Small unmade decisions create disproportionate stalls
Sequences stall for many reasons — missing resources, unclear ownership, competing priorities. But one of the most common and least visible causes is a small unmade decision that is holding multiple downstream tasks in suspension without anyone having identified it as the source of the problem.
These decisions tend to be small enough that they feel like they should not need formal attention — a format choice, a naming decision, a preference between two approaches that seem roughly equivalent. Because they feel minor, they get deferred. Because they get deferred, the tasks that depend on them cannot start. The stall appears to be about the larger work when it is actually about the smaller unresolved choice underneath it.
Pairwise comparison identifies these unlock decisions by comparing what is currently waiting against what is currently undecided — surfacing the connection between the stall and its cause.
What type of small decision is most likely causing the stall
Unlock decisions tend to cluster around a small number of types — identifying the type makes the specific decision easier to find
Different types of small decisions create different patterns of downstream stall.
Format and approach decisions are among the most common unlock decisions. When it has not been decided whether something will be a document or a presentation, a meeting or an async process, a built solution or a bought one, every subsequent task that touches the output is in limbo — unable to start without knowing what it is building toward.
Ownership decisions are another common type. When it is unclear who has authority to make a particular call, everyone waits for someone else to make it. The decision is not difficult — it simply has not been assigned. Assigning it resolves the stall immediately.
Framing and naming decisions are a third. When a project, a product, or a piece of work does not yet have a settled name or framing, communications about it remain vague, alignment is harder to achieve, and the downstream work that requires a clear description cannot proceed cleanly. The name feels like a minor thing until it is absent.
Identifying which small decision would release the most downstream work
The unlock decision is the one whose resolution immediately makes the next step obvious
That is the test — not how significant the decision feels, but how much it releases when made.
The signal that something is an unlock decision rather than just an unresolved minor item is the effect of its resolution. When a small decision is made and several other things immediately become possible or clearer, it was the unlock. When a small decision is made and nothing changes downstream, it was not.
Unlock decisions often have a characteristic quality: they have been deferred precisely because they feel like they should not need to be made formally. Someone should have just decided. The fact that nobody did is not a sign that the decision is unimportant — it is often a sign that nobody realised how much was waiting on it.
Comparing the candidates for unlock decision directly — which of these, if resolved, would release the most immediate downstream work — is what this comparison is for.
When several small decisions are competing for the unlock position
When more than one small decision appears to be holding things up, the unlock is the one whose resolution releases the others
It is possible for a sequence to have more than one small unmade decision causing stalls simultaneously. When that happens, the priority comparison is between them — which of these, if resolved first, would make the others easier or unnecessary?
In most cases there is a hierarchy. One decision, once made, reduces the ambiguity around the others or makes them straightforward to resolve. That is the unlock — not because the other decisions are unimportant but because they are downstream of this one in the decision structure, even if that structure has not been explicitly mapped.
The cost criterion also applies here. The decision whose continued ambiguity is creating the most cost — in delayed work, in ongoing uncertainty, in the effort of working around it — is the one whose resolution is most urgent regardless of how small it appears.
The three ways to resolve a small decision that has been left unmade too long
The right resolution depends on whether the decision needs to be made, owned, or forced
Making the decision now and treating it as the unlock it actually is means someone with sufficient information and authority simply decides — and communicates that decision clearly enough that everything waiting on it can begin. This is usually faster than it appears. The decision has often already been made informally by whoever has been working closest to it. Formalising it takes minutes. Not formalising it costs days.
Assigning clear ownership means the decision has not been made because nobody has been explicitly responsible for making it. Assigning it to a specific person with a specific deadline converts an ambient ambiguity into a tracked item with a resolution date. The decision itself may take no longer than five minutes once it has an owner — the delay was never about difficulty, only about unclear responsibility.
Time-boxing it means setting a point at which a default applies if no decision has been made by then. This works when the decision genuinely requires input that is not yet available, but the indefinite wait for that input is more costly than proceeding with a reasonable default. The time-box forces a resolution rather than allowing the stall to continue indefinitely under the cover of waiting for the right moment.