Some problems are not solved by better decisions. They are structured so that every available response makes the underlying issue worse.
This is not a failure of judgment. It is not a management problem or a culture problem or a communication problem. It is an architectural problem — a structural condition that produces bad outcomes regardless of how capable or well-intentioned the people inside it are.
The name for it is the Double Bind.
What a Double Bind is
A Double Bind is a situation in which two responses are available, both responses are reasonable, and both responses reinforce the problem they are trying to address.
The trap is not visible from inside it. From inside it, the situation looks like a decision — two options, each with costs and benefits. The person chooses the one that seems less costly. The problem continues. They adjust, try again, apply more effort to the same response or switch to the other one. The problem continues. Eventually the conclusion is that the people involved are not capable enough, not committed enough, or not working hard enough. The structural condition that made the problem inevitable is never examined.
This is the mechanism that makes Double Binds expensive. Not that they are hard to see once identified. That they are almost never identified. The organisation spends months or years cycling through the available responses, each one producing the same outcome, without ever stepping back far enough to recognise the shape of the trap.
What it looks like in practice
The clearest version of the Double Bind in a founder-led company is the escalation pattern.
The founder notices that decisions are not being made at the right level. The team escalates too much. Work stalls when the founder is unavailable. The response is to push back — to tell the team to make the decisions themselves, to delegate, to step away from operational detail.
The team tries. But the information they need to make good decisions independently — the strategic context, the priorities, the founder’s reasoning on past decisions — is not documented anywhere. It exists in the founder’s head. Without it, the team makes decisions that turn out to be wrong, or that contradict each other, or that have to be undone. The founder steps back in to correct the damage. The team learns that making independent decisions leads to problems. They escalate more.
Now try the other response. The founder accepts the escalation. They stay available, they answer the questions, they make the calls. The decisions get made correctly — the founder’s judgment is, in fact, usually right. The team becomes more dependent. The founder becomes more central. The organisation’s capacity to operate independently decreases. The founder is more load-bearing than before.
Both responses are reasonable. Work harder on delegation, or accept the escalation and keep things running. Both make the underlying problem worse. That is the Double Bind.
Why the conventional diagnosis fails
The standard reading of this pattern is that the founder needs to let go. That the problem is one of control — the founder is holding on too tightly, not trusting the team, micromanaging. The solution is to change behaviour: delegate more, resist the urge to step in, give the team space to learn from their mistakes.
This diagnosis is not wrong exactly. But it is incomplete in a way that makes it useless.
The reason the founder keeps stepping in is not primarily psychological. It is structural. The team does not have what they need to make good decisions independently. They do not have it because nobody built the infrastructure to give it to them — the documented strategy, the clear decision rights, the shared context that would allow them to know what the founder would decide without having to ask. That infrastructure does not exist because the founder has been too busy being the infrastructure to build it.
Telling the founder to let go without building the structural alternative is like removing a load-bearing wall and hoping the ceiling does not fall. The instruction is technically correct. The precondition for it being safe has not been met.
What breaking it requires
The exit from a Double Bind is not a better choice between the two available responses. It is the construction of a third option that did not previously exist.
In the escalation pattern, the third option is building the structural alternative before withdrawing. Documenting the strategy so it is accessible to everyone who needs to make decisions from it. Defining decision rights so that ownership is clear and escalation is the exception rather than the default. Creating the shared context that allows the team to reason from the same starting point as the founder, without the founder present.
This is slower than choosing between the two available responses. It requires work that feels strategic rather than operational, and it produces no immediate visible results. The founder who does this work is still answering escalations while building the alternative. Nothing improves in the short term.
But the structure of the trap requires it. There is no shortcut between a Double Bind and its resolution — only the work of building what is missing.
The same trap, experienced from below
The Double Bind is not only a founder problem. The same structure operates at every level of the organisation where ownership is unclear and escalation is the default.
Consider someone in a sales role — call them Sam. Sam is trying to move a deal forward and needs to make a call on pricing. The decision is not clearly theirs to make. Two responses are available.
Sam makes the call independently. If it goes well, nothing is said. If it goes badly — if the pricing was off, if it contradicted something agreed elsewhere, if the founder would have decided differently — Sam is corrected. Sometimes publicly. The lesson is clear: independent decisions carry personal risk.
Sam escalates instead. The decision travels upward. It waits. The client waits. When it comes back down, it comes with the right answer — and sometimes with a signal, spoken or unspoken, that Sam should have been able to handle this. The lesson is equally clear: escalating signals a lack of capability.
Act and risk being wrong. Wait and risk being seen as incapable. Both responses carry a cost. Neither resolves the underlying condition, which is that Sam does not have what they need to make the decision well — the context, the boundaries, the clarity about what is theirs to decide.
This is the Double Bind as it is felt inside the organisation. Not as a structural observation but as a daily experience of working in a system that punishes both initiative and caution, depending on the outcome. Over time the rational response is disengagement — not because Sam stopped caring, but because the cost of caring actively has become higher than the cost of doing the minimum and waiting for instructions.
The founder sees a team that cannot operate independently. The team is living inside a structure that was never built to allow them to.
The first step is recognising the shape of the problem. Not as a management failure. Not as a people problem. As a structural condition that will continue producing the same outcomes until the architecture changes.
That recognition is the exit from the trap. Everything else is construction.