A library, not a method.
These are the thinking patterns I lean on when I work with product leadership, and the people I learned them from. None of them are my ideas. Each one has shaped how I see the organisations I consult with, and how I explain what I see. I add a pattern here when I have used it enough to know what it does well, and where it does not.
Seven models. One argument.
Building shared understanding when the situation is genuinely uncertain. Before a team can act well, it needs to agree on what kind of territory it is in — and what kind of action that territory requires.
Explore
The structures that determine who decides what — and whether those decisions stick. Most organisations have a formal structure and an informal decision architecture, and it is the informal one that governs.
Explore
The discipline of staying in contact with the problem before committing to the solution. How teams find, frame and validate the right work — before building the wrong thing with great precision.
Explore
The social and neurological forces that shape whether individuals contribute, challenge or withdraw. Designing conditions for good work starts with understanding how people actually behave in groups, not how they are supposed to.
Explore
How transformation actually spreads through organisations — and why the project-plan reflex almost always slows it down. The difference between mandating change and building a movement for it.
Explore
What leaders actually do that determines whether an organisation can hold complexity. The distinction between directing outcomes and designing conditions, and why that distinction separates leaders who land transformations from those who stall at the management layer.
Explore