Selected work
Four products built for people who work inside them all day: an enterprise operations platform, a support desk, a music system for venues, and a website that has to sell a factory. Each entry opens a full case study: the constraint, the model underneath, and the decisions I would defend in a review.
How to read these. All four decks run the same shape: overview, the problem stated in the words the teams used, how I reasoned about it, the surfaces themselves, then impact and reflection. Each one has a table of contents, so skip to the section you care about.
Syahzani
Syahzani
The short version
I am a product designer working on operational software: enterprise platforms, support desks, and the tablet mounted behind a bar. The kind of product people sit inside for eight hours, until they know where every button lives.
I usually get called in once a product has grown one feature at a time and nobody can describe it in a sentence any more. My job is to give it back a shape someone can defend in a review.
How I work
What I go deep on
The part that rarely shows up in a portfolio shot: how an object is modelled, who is allowed to change what, and whether a decision still makes sense six months later when nobody remembers the reasoning. Permission models, state machines and information architecture are where I do my most useful work.
I stay through build. I sit in the sprint, answer the edge cases, and cut scope with the engineers when the date is real. Design that ships is the only kind that counts.
Before this
Earlier work was consumer apps and marketing sites, and that experience still earns its keep: writing interfaces that make sense to someone opening them for the very first time.
Outside work
Coffee brewed with more equipment than any morning deserves, and a font collection I keep adding to and rarely use.
Let’s talk
Got a product that has become hard to explain?
Tell me the situation as it actually is. If I am not the right person for it, I will say so plainly.
Whichever you pick, it reaches the same person. Email suits briefs and attachments; WhatsApp suits a quick question.