01
Sit inside the ambiguity.
Before a single screen, I map the real shape of the problem — the constraints, the data, the people who'll live inside the system.
02
Give shape to complexity.
Systems thinking turns tangled requirements into a structure teams can actually build on.
03
Make it feel weightless.
Interfaces that carry complexity quietly — clear, considered, never heavy-handed.
04
Test what matters.
Research and iteration close the loop, so the solution holds up long after it leaves the deck.
