Ahmed.Idris

Designing paths through complexity.

Intro · 1:24

Creating cohesive product experiences across fragmented enterprise and government workflows.

Featured Work

All projects

No client is named here, and each screen is a recreation built for this portfolio. The structure and the density are the real thing. The content is made up.

01

Vehicle Operations Platform

Forty car dealerships, each with its own forms, spreadsheets and process. One record per car, and a module for each part of the work.

Lead product designer5 workflows · 7 rolesIn testing
02

Reseller Licensing Ops

A company that resells Google Workspace. What a client had bought sat in Zoho, what was running sat in Google’s reseller console. One record holds both counts.

Lead product designer3 systems → 1 consoleLive
03

Government Developer Portals

National API portals built from scratch for regulators and a health-sector data company. Arabic-first, identity-gated, strict standards.

Government & health3 written upLive
04

Struct, a shared design system

The shared set of components, rules and colour tokens behind the dealership and licensing products, so the two look and behave like one thing.

Design systems2 products, 1 libraryOngoing

Where work
usually starts

The information usually exists already. It sits in tools that do not share data, and people fill the gaps with calls and messages. A disagreement between two of them only surfaces when something goes wrong.

01

Map the work as it is done

Interviews and working sessions with the people doing the job, and the forms, spreadsheets and messages they keep themselves. The aim is to see the whole job, not just the part the brief mentions.

Across five dealerships and one cleanup centre, the brief was to replace the spreadsheets, but the spreadsheets were not what was going wrong.

02

Settle the model before the screens

Which object the work is about, which states it moves through, and who is allowed to change them. Those questions are cheaper to answer once, early, than on every screen afterwards.

Three modules kept the same vehicle record and needed different states from it. That was settled before any of them were drawn.

03

One list, with a different view for each role

Everybody writes to one record, and each role gets the screen it needs. Each view can be narrow, as long as it reads from the same record as all the others.

Operators at a desk get dense tables and keyboard shortcuts. Drivers moving cars between stores get a phone and nothing else.

Working on a system that needs to feel like one product?

I’m open to senior and lead product design roles. Pick a time for a short intro call, or write to me directly.

a.idris.prof@gmail.com
Intro call · 30 minCairo time (GMT+3)
Book Wed 23 at 13:30