Set clear expectations
Name what ownership looks like, where support is available, and how a decision will be made.
Page record 03Leadership philosophy
People → Process → Practice → Impact
I stay close enough to the product to improve the decision, then create enough clarity for the team to own what follows. The sequence makes that practice repeatable.
- 01People
- 02Process
- 03Practice
- 04Impact
01 / People
Make it safe to think out loud.
Teams cannot do their best work when every question feels risky or every decision waits for the most senior person in the room.
Coach the next rep
Turn broad feedback into one behavior someone can practice, observe, and build on.
Distribute ownership
Create room for designers to lead the work, the conversation, and eventually the system around it.
02 / Process
Use structure to reduce friction.
A useful process makes the work easier to understand. It should expose decisions and handoffs without becoming another layer the team has to serve.
Make the path visible
Clarify how work enters the team, what evidence is needed, who decides, and what “ready” means.
Bring design in early
Frame the problem with product and engineering before the solution has hardened around an assumption.
Document what must last
Capture decisions and operating agreements so progress does not depend on who happened to be in the room.
03 / Practice
Make quality repeatable.
Strong craft should not require heroics. It grows through shared standards, regular critique, research, accessibility, and time to improve the work before it ships.
Critique the decision
Ask what the work is trying to solve, what changed, and what evidence would change the team’s mind.
Build a shared language
Give design, product, engineering, research, and content a common way to discuss quality and tradeoffs.
Put standards in the workflow
Treat accessibility, interaction quality, and definition of done as part of delivery—not a final inspection.
04 / Impact
Measure what became better.
Shipping is an event. Impact is the change that follows: a clearer decision, a more reliable workflow, stronger adoption, less rework, or a team able to operate with more confidence.
Agree on the signal early
Define the behavior or operating condition the work is expected to change before choosing the output.
Keep evidence close
Pair claims with the artifact, observation, or measure that makes the change inspectable.
Carry the learning forward
Use the result to improve the next decision, the next release, and the way the team works together.
In practice