Start with the person trying to understand
Before designing the system, understand what the person is trying to make sense of, decide, avoid, explain, or defend.
This keeps the work grounded in real situations instead of abstract platform logic.
A practice for making unclear work discussable.
Less a manifesto than a working method: find the decision, expose the model, prototype the argument, and keep human judgement visible.
Make complexity readable
Complex products do not need to feel simplistic. They need to feel legible, structured, and navigable.
The aim is not to hide the system, but to make the right parts understandable at the right moment.
Use prototypes to think together
A prototype is not only a preview of an interface. It is a shared object for discussion, alignment, critique, and better questions.
I use prototypes to turn uncertainty into something teams can react to and improve.
Design for trust and agency
People trust products when they can see what is happening, understand why, and retain enough control to act with confidence.
This matters in AI workflows, governance tools, and any product where people need to stand behind their actions.
Keep craft close to strategy
Strategy becomes real through details: hierarchy, interaction, language, rhythm, and the small decisions that shape how a product feels.
Visual craft is not separate from product thinking. It is how product thinking becomes usable.