A person can understand the principle and still struggle in work that gets stuck between teams because social pressure, time pressure or uncertainty changes what is easy to retrieve. The purpose here is making ownership visible without creating a blame culture. Accountability improves when ownership, finish conditions, timing and escalation are visible before problems occur.
Plan A: the normal version
Before work that gets stuck between teams, use review missed commitments without blame. During it, watch for meetings with actions but no follow-up. If the situation stays within normal range, continue with name a single owner for each commitment and review on-time handoff rate afterward.
Plan B: when pressure changes the conditions
Switch plans when tasks owned by everyone makes the original approach less useful. Plan B is attach a date or trigger. It is intentionally simpler so it can survive higher cognitive load.
The stop rule
Stop adding explanation or effort when you notice using accountability as punishment. At that point, either ask for the missing information, renegotiate a constraint, take a short pause or escalate according to the situation.
A sample switch
You might begin with “What will count as done?” and later move to “If this is blocked by Thursday, what is the escalation path?” if the first approach no longer fits. The switch is a sign of adaptation, not failure.
What to compare after the attempt
| Attempt | Trigger | Plan used | Result | Keep/change |
|---|---|---|---|---|
| 1 | meetings with actions but no follow-up | review missed commitments without blame | on-time handoff rate | Change one variable |
| 2 | tasks owned by everyone | name a single owner for each commitment | age of blocked work | Keep what helped |
| 3 | What became predictable? | Repeat the reliable move | number of reopened tasks | Increase difficulty only if stable |
Use a trade-off map
Work that gets stuck between teams usually contains at least two competing values: speed versus quality, harmony versus candor, autonomy versus control, or short-term relief versus long-term learning. Write the two most important trade-offs before acting. Then use name a single owner for each commitment to protect the priority you have chosen and define an acceptance condition when the trade-off changes.
When to change course
Switch approaches when the evidence changes, not simply because discomfort rises. If tasks owned by everyone is present and commitments with one named owner is deteriorating, change one part of the response. If discomfort rises but the evidence remains sound, you may be experiencing normal pressure rather than a signal that the plan is wrong.
Review one trade-off explicitly
Most professional situations contain a trade-off: speed versus accuracy, candor versus harmony, autonomy versus control, short-term relief versus long-term learning, or detail versus clarity. Name the trade-off before acting. Afterward, ask whether the balance you chose still makes sense. This creates a more useful review than asking only whether the situation felt comfortable or whether everybody was pleased. Applied to work that gets stuck between teams, keep the review tied to team accountability rather than turning it into a broad judgment about ability. Write one observation from the attempt, one decision you would repeat, and one change for the next comparable situation. If you cannot name those three items, the review is probably still too general. The purpose is to leave the situation with a usable next experiment, not a longer explanation of why it was difficult.
Questions people ask
What if another person makes the situation harder?
Keep the boundary between influence and control clear. You can use name a single owner for each commitment, state the relevant constraint, and decide whether to continue, pause, renegotiate or escalate.
How long should I practice before changing the plan?
Run several comparable attempts unless the approach creates a clear problem. Look for a trend in number of reopened tasks, not a perfect first performance.
What is the earliest sign I should watch for in work that gets stuck between teams?
Use an observable signal rather than a mood label. For this article, start with meetings with actions but no follow-up. It appears early enough to support a different choice.