The five Frustration Architectures, explained

The five Frustration Architectures are the recurring structural patterns that produce the Frustration Condition: Decision Bottlenecks, Approval Loops, Priority Churn, Role Ambiguity, and Unspoken Constraints. They are the published vocabulary the Cross-Functional Listen clusters open-text into, and the unit of analysis the Three Doors decision discipline acts on.

The set is small enough to memorise and broad enough to absorb almost every structural friction a knowledge-work team will raise. That combination — small and exhaustive — is what makes the framework usable as shared vocabulary inside an organisation rather than a consultant's deliverable.

1. Decision Bottlenecks

A Decision Bottleneck is a structural pattern in which a category of decisions cannot be made without a specific person or forum, and that person or forum has insufficient capacity to clear the queue. The team learns that initiative routed through the bottleneck stalls; over time, fewer initiatives are started.

Typical signatures in open-text: 'Waiting on a decision from X,' 'We can't move until the steerco meets,' 'No one will say yes or no to this.' Typical Three Doors response: Remove the bottleneck (delegate the decision), Defer With Clarity (publish the queue and the date), or Accept (name the constraint and adjust the team's plans).

2. Approval Loops

An Approval Loop is a structural pattern in which a piece of work circulates through multiple approvers in a sequence that does not converge — each approver introduces feedback that requires re-approval from earlier approvers, and the loop closes only when one approver gives up. The team learns that finished work is reversible.

Typical signatures: 'We've been through five rounds of legal,' 'Marketing approved it but then product wanted changes,' 'Every time we update it, someone else weighs in.' Typical response: Remove (collapse approvers to a single accountable owner), Defer With Clarity (lock scope and ship a version), or Accept (declare the work permanently in revision and stop pretending).

3. Priority Churn

Priority Churn is a structural pattern in which the top-priority list changes faster than the team can deliver against it. The team learns that effort is reversible — work in progress is regularly abandoned — and stops investing in execution depth.

Typical signatures: 'This was top of the list last quarter,' 'Why are we still doing this?,' 'I'm not sure what we're optimising for any more.' Typical response: Remove (publish a frozen quarter), Defer With Clarity (acknowledge the new priority and explicitly retire the old), or Accept (declare the function reactive and resource it accordingly).

4. Role Ambiguity

Role Ambiguity is a structural pattern in which more than one person reasonably believes they own a decision or output, and the disagreement is never resolved. Work is duplicated; gaps appear; accountability blurs. The team learns that ownership is contestable and stops investing in either side of the contested boundary.

Typical signatures: 'I thought you owned this,' 'Two teams sent us the same brief,' 'No one is the DRI on this.' Typical response: Remove (assign a single DRI on the record), Defer With Clarity (publish a temporary owner with a date for resolution), or Accept (declare the boundary permanently shared and define the coordination cadence).

5. Unspoken Constraints

An Unspoken Constraint is a structural pattern in which a real binding constraint — budget, headcount, regulatory, customer-commitment — is known by leadership but not surfaced to the team, who continue to plan around the absent constraint and discover it at the moment of execution.

Typical signatures: 'No one told us we couldn't,' 'We built that and then heard about the freeze,' 'Why is this only coming up now?' Typical response: Remove (lift the constraint where possible), Defer With Clarity (name the constraint and the date it lifts), or Accept (publish the constraint as a working assumption).

Why five Architectures and not more

The set was derived empirically from the doctoral study underlying this framework — a phenomenological analysis of 23 manager interviews followed by a 331-participant quantitative validation. Across the qualitative corpus, every reported friction routed to one of these five with high inter-coder agreement. Adding a sixth category produced near-empty clusters; collapsing to four produced clusters that lost diagnostic specificity.

Five is also the practical maximum for shared vocabulary inside a line organisation. Above five, line managers stop using the framework in conversation; below five, the categories absorb too much heterogeneous content to be actionable.

Outside references