Frame
Clarify the problem
Make the problem, constraints, and decision space visible so teams can move through ambiguity without waiting for a brief that never arrives.
Approach
How I work as a senior product designer.
I move across problem, strategy, UX, prototype, working product, and validation. Builder capability means turning product decisions into working software — not collecting AI tools.
- Frame
- Design
- Build
- Validate
How I work
Frame → Design → Build → Validate
An operating model for consequential product problems — not a generic design-process diagram.
Design
Shape the system
Architecture, interaction, and experience language that product, engineering, and operations can share — before pixels become politics.
Build
Make it real
Functional prototypes, MVPs, and production interfaces. AI-assisted development raises fidelity so decisions get tested as software, not slide decks.
Validate
Learn under constraint
Evidence from users, operations, and shipping. Adjust the bet. Protect quality. Stay accountable to what actually works.
AI-native product practice
Designing for an AI-native world
AI is changing more than the speed of design. It is changing what we design, how products behave, and where design responsibility ends.
From specialist to orchestrator
The work is no longer only screens. It is framing the problem, sequencing judgement, and helping product, engineering, and operations act as one system.
From AI as a tool to AI as a material
Models change product behaviour: what is offered, what is withheld, how trust is earned, and what happens when the system is wrong. That is design material, not a plugin.
From deterministic flows to probabilistic experiences
Intelligent products must be designed for expected, uncertain, and failed states. Recovery, explanation, and human override are part of the product, not afterthoughts.
Product principles
Principles for intelligent products
- 01
Design for intent, not only navigation.
- 02
Use AI where it creates meaningful value.
- 03
Design expected, uncertain, and failed states.
- 04
Match system autonomy to consequence.
- 05
Build calibrated trust.
- 06
Evaluate behaviour continuously after launch.
Leadership
Direction without distance.
My role changes with the organisation’s needs. I can set direction, create alignment, and remain close enough to the work to protect the quality of execution.
Make decisions legible
Situation, options, evidence, trade-off, and choice — so teams can critique the thinking, not only the UI.
Build critique into the system
Quality should not depend on one leader reviewing every screen.
Stay close to the work
Leadership is not distance from execution. It is responsibility for the conditions in which execution succeeds.