Playbook
Four gates, then a foundation lift.
We validate from the bottom of the stack up. The first gate that fails tells us where the ambiguity enters. Fixing it there, rather than where it shows, is what makes the improvement last.
- Gate 1L4 · Experience-First
Can we articulate the experience?
Fails when
- Nobody can describe the end-to-end journey
- Success is measured in features shipped
- Recovery paths are an afterthought
Passes when
The moments, journeys and recovery paths are written down and agreed before anything is built.
- Gate 2L3 · Systems-First
Can we articulate the system?
Fails when
- Every team has its own plumbing
- Changes feel risky and slow
- AI-generated code multiplies inconsistency
Passes when
Boundaries, contracts and standards are explicit, and a human owns every validation gate.
- Gate 3L2 · Team
Can the team commit?
Fails when
- Meetings end in agreement, not action
- Tension is discussed in corridors
- Work lives in people's heads
Passes when
Decisions turn into commitments with owners and next actions, and the team holds itself to them.
- Gate 4L1 · Organization
Does the organization own it?
Fails when
- Decisions get reopened
- Mandate and responsibility sit in different places
- Ambiguity is absorbed by individuals
Passes when
Ownership and mandate are explicit, decisions leave a trace, and open ambiguity has somewhere to go.
Foundation lift
Once we know which gate failed first, we work one layer above it. If the experience cannot be articulated because the system is unclear, we fix the system. If the system is unclear because the team cannot commit, we work with the team. The goal is not to pass every gate at once, but to stop ambiguity entering at its source.
Start
Tell us where ambiguity is costing you.
A short note is enough: what you are trying to ship, and where it keeps getting stuck. We will reply with which layer we think the cause sits in.