my name is

JAMAL

Makes it clear 50+ intranets UI/UX Designer Chennai, IN

Open to full-time roles

I turn complex enterprise tools into things people actually use

Four years inside the software nobody puts on a portfolio: the intranets, the dashboards, the forms people open every single morning.

about me!
Mohammed Jamal leaning on a railing in front of a yellow wall
that's me

what's up

Most enterprise software isn't badly designed. It's undesigned.

It gets built feature by feature until nobody remembers what it was for.

I've spent four years at SharePoint Designs fixing exactly that, across fifty-plus intranet portals. The fix is rarely a new feature. It's a clearer sentence, a shorter path, and a screen that admits what it's actually for.

Mohammed Jamal in profile on a train, listening to music
off the clock
4+
years designing enterprise products
50+
intranet portals shipped to real teams
03
case studies written end to end
  • UI Design
  • UX Research
  • Prototyping
  • Design Systems
  • SharePoint
  • Accessibility
explore my work!

Featured
Works

Three problems, told properly: the research, the wrong turns, and the decisions I'd defend.

+ Project 01
Mobile app · Case study

NutriDash

People order food they can't see the contents of. NutriDash puts the ingredients back in front of the person eating them, without turning dinner into a spreadsheet.

View case study ↗
UI/UXHealthFood delivery
NutriDash app screens
+ Project 02
Mobile app · Case study

Fuel Buddy

Fuel prices change daily and nobody knows where the cheap pump is until they've driven past it. A small app for a decision people make weekly and think about for ten seconds.

View case study ↗
UI/UXMobilityMaps
Fuel Buddy app screens
+ Project 03
Web app · Case study

DocVault AI

The closest to my day job: thousands of documents, no shared vocabulary for finding them. An AI layer is only useful here if it earns trust faster than the search bar it replaces.

View case study ↗
UI/UXSharePointAI
DocVault AI dashboard
how I work

Four moves

Not a methodology I read about. Just the order that stops me designing the wrong thing beautifully.

  1. 01

    Listen

    Talk to the people who have to live in the thing. Stakeholders describe the system they wanted; users describe the one they got.

  2. 02

    Frame

    Write the problem in one sentence everyone can agree on. If it takes a paragraph, we don't understand it yet.

  3. 03

    Design

    Flows before screens, systems before pixels. Components a developer can reuse without asking me what the spacing was.

  4. 04

    Ship

    Stay through the build. The handoff isn't a file. It's the fifty small answers that come after it.

where the reps came from

The Practice

Nov 2022 → Present

SharePoint Designs

UI/UX Designer

Designed and delivered over 50 intranet portals with a focus on usability, accessibility and engagement, working alongside developers, product managers and stakeholders to keep the design intact from the first workshop to the last build.

UI DesignUX ResearchPrototypingDesign SystemsSharePointAccessibility

tools on my desk

  • Figma
  • Framer
  • Webflow
  • Photoshop
  • Illustrator
  • Adobe XD
  • Miro
  • Notion
  • Lightroom
through my lens

Field Notes

I shoot street photography wherever I travel. Same instinct as the day job: watch what people actually do.

Street photograph 1
Street photograph 2
Street photograph 3
Street photograph 4
Street photograph 5
Street photograph 6

more at @jamal_bikon ↗

Let's talk

Hiring for something complex? Tell me what your team is trying to fix. I read every message.

Mohammed Jamal

Looking for a full-time product or enterprise design role, especially one with the messy, unglamorous problems in it.

let's make something clear together