Frame
Find the decision behind the brief
I ask what needs to become clearer, who is affected and what evidence would change our direction. A good frame prevents a team polishing the wrong solution.
How I work
I help teams turn ambiguity into a decision they can test, build and learn from.
The process changes with the problem. The constant is staying close to the people using the product and the people responsible for shipping it.
How I move the work
Five behaviours I return to as the work changes.
Learn
Bring the team into the evidence
Research matters when it changes shared understanding. I make findings tangible early so Product, Engineering and Design can challenge assumptions together.
Explore
Prototype the risky question first
I use sketches, Figma, coded prototypes and AI-assisted exploration to compare directions. The fidelity follows the question—not the other way around.
Include
Treat accessibility as a design input
I look for visual, cognitive, language and interaction barriers while the product is still flexible. Strong fixes usually improve the pattern for everyone.
Ship
Stay close through implementation
I work with engineers through build, review edge cases and refine the interaction in the product. Delivery is part of design, not a handoff at the end.
The work gets better when everyone making the decision can see the same problem clearly.
What teams get from me
- Clear framing when the brief is still ambiguous.
- Enough craft to make an idea tangible and testable.
- Honest challenge without losing momentum.
- Design ownership that continues into the shipped product.
Proof in practice
Where the way of working changed the outcome.