Process
How I work
Complex products fail in the seams between roles, between systems, between what a team intended and what a person does at 4:55pm. These four principles are how I keep the seams visible and the work shippable.
01
Behavior before interface.
I start with what a person is actually doing when they reach the screen - who is standing in front of them, what they are afraid of getting wrong, how many seconds they have. The interface is the last decision, not the first.
On the Agent Chat, one day of shadowing gave us more insight into the users' needs than any brainstorming session.
02
Decide with evidence, argue with trade-offs.
Strong opinions are cheap in a design review. I bring the observation that produced the opinion, and I name what the alternative buys and what it costs, so the room can decide instead of defer.
On Campaigns, the dashboard-versus-wizard question was settled by shadowed A/B testing rather than by whoever spoke last.
03
Systems are how design scales.
One good screen helps one team. A shared foundation of tokens, components, accessibility baked in, and governance people can live with raises the floor for everyone and makes the next release faster than the last.
The Odeza design system brought order and guidelines that served as the foundation for all Odeza products.
04
Ship inside real constraints.
Timelines, legacy data models, compliance, and one engineer's remaining sprint are the material I design in, not obstacles to design around. The best version of the work is the one that reaches users.
Three months, with minimal engineering resources and Practice Edition still shipped a V1 that won its category.
Contact
Let’s build something that works.
Currently advising teams at Frameworks Partners and open to my next full-time senior role.