How I lead
The operating model I have refined since 2008
Small groups explore. One owner executes. Peers review. People develop faster when their roles build on their strengths. Decisions get made on evidence.
-
The operating model
Since 2008, small groups explore at project kickoff, one design owner carries execution, and structured peer review is the quality gate.
It started with a fourteen person team at eMedia, and it is still how I run work today.
-
Develop by strength
I inherited designers who were exceptional conceptual thinkers but struggled with visual execution. I positioned them around their conceptual strengths and paired them with designers who had exceptional visual craft. Both became stronger designers.
Develop people, do not manage them out.
-
Evidence over persuasion
I showed them the call volume and the decision made itself.
-
The translator
I am fluent across the C suite, product, engineering, QA, research, and policy.
I help teams reach decisions everyone understands, supports, and can execute.
-
Partners and vendors
I apply the same quality standards across internal teams and partner organizations: early mockups, clear specifications, structured reviews, and unbiased research practices.
When a persistent practice problem requires executive backing, I escalate the underlying structure rather than repeatedly treating individual symptoms.
-
Design for the limits
Every system has a point where it stops being able to help. That moment is a design surface, not an exception to handle later.
I would rather ship a system that says it does not know than one that performs certainty. Designing the failure path is not defensive work. It is where trust is built or lost.