Discover
I listen widely: users, clients, stakeholders, data, constraints, and the developer who knows where the edge cases live.
How I work · Double Diamond, evolved
I use a Double Diamond process, but I do not worship the diagram. The goal is to turn messy signals into useful action.
Discover → Define → Design → Deliver or DevelopThe principle behind the process
I listen widely: users, clients, stakeholders, data, constraints, and the developer who knows where the edge cases live.
I turn research signals into a focused problem, shared priorities, and clear design or developer actions.
I explore flows, interfaces, and prototypes while keeping user value and business value in the same conversation.
I communicate clearly with engineers and increasingly build working prototypes myself using Codex and Claude Code.
The part diagrams miss
I make clients feel heard, explain decisions clearly, and build confidence around the direction.
My computer science background helps me turn design intent into language developers can act on.
I connect insights, design choices, and business value so decisions feel grounded rather than subjective.
I work comfortably with users, designers, developers, business teams, and whoever else the problem needs.