Frustration Architecture
Role Ambiguity
Nobody is certain who owns this. It gets done late, it gets done twice, or it doesn't get done at all — and nobody is blameable.
Dr. Tim Hough · ISBN 979-8-9965397-1-0 · Buy the book →
From the book
Role Ambiguity is what happens when the org chart is silent about who actually owns a piece of work, so the work falls into one of three quiet failures: it is done late by the most conscientious person on the team, it is done twice by two different people who don't know about each other, or it isn't done at all and shows up as a customer complaint a month later.
Ambiguity protects no one. The team learns to do informal hand-offs in hallways, in DMs, in the margins of unrelated meetings. Those informal workarounds are not laziness — they are the team building the missing scaffolding by hand, every week, because the scaffolding was never put up.
The architecture is the ambiguity, not the absent owner. Naming the owner is half the fix. The other half is naming what the owner is on the hook for, and what they are explicitly not on the hook for.
The diagnostic
If your team's most common explanation for missed work is "I thought X was doing it" or "I didn't realise that was on me," and the same boundary keeps getting re-litigated, you are looking at Role Ambiguity. The work isn't getting dropped because people are careless. It's getting dropped because the catcher's mitt isn't on anyone.
The fix recipe
- 1
Name the outcome, not the activity — what is the team on the hook for delivering, and to whom.
- 2
Assign one owner per outcome, and write down what they are explicitly NOT on the hook for so the boundary is visible.
- 3
Build parallel infrastructure where two functions genuinely share the work — a small standing forum, not another approval — so escalation is no longer the only path.
- 4
Tell the room what changed in Three Doors voice and remove the informal hand-offs that were holding the gap together.
All five architectures
Most teams are living inside more than one at a time.
The diagnostic runs inside a workspace.
Public content ends here. The live tagging, clustering, and Three Doors decisions against each architecture happen once you stand up a workspace.
Source: Why Your Best People Stop Trying. Dr. Tim Hough.