Turning complexity
into clarity.
I've spent about ten years designing software for complicated industries: AI, government, healthcare, supply chain, defense, enterprise, digital transformation. Most of that work had less to do with screens than with working out what the product actually needed to do.
Most people know me as Abu Alseed. Or just Sed, because people are usually too lazy to pronounce long names.
For more than ten years I've been designing digital products in AI, government, healthcare, supply chain, agriculture AI, defense, enterprise and digital transformation. Very different industries, same job: take something complicated and make it usable.
Somewhere along the way I stopped thinking of this job as screens and wireframes. Most of it is learning a domain quickly, keeping a room full of stakeholders roughly aligned, and making decisions before you have all the information. This site is where I write some of that down.
Three projects, start to finish.
Each one covers what the problem was, how I worked through it, and what shipped. They are all client work, so they sit behind a password.
How the work usually goes.
Understand
Framing the problem, talking to the people who'll use it, and finding out what the stakeholders quietly disagree about.
Map
Stories, journeys and flows, so the logic of the thing is visible before anyone designs a screen.
Design
High-fidelity UI built on a real system, so the hundredth screen still matches the first.
Ship
Handoff, QA, then fixing whatever real users manage to break.