Companies draw boxes. Inside them are departments, roles and systems. Between them, a few arrows.
The boxes get budgets, owners and projects. The arrows are treated as fact. On paper, each is only a claim.
The boxes can all be right
This is what makes some businesses so hard to read: no single part appears weak. The strategy is sound, the people know their craft, the tools are in place. And the whole still barely moves.
Then the question shifts to the arrows. And something stands out: every box has an owner. The arrows between them usually don’t.
Forwarded does not mean received
An observation does not become a decision just because it was forwarded. A decision does not become action just because it appears in the minutes. An inquiry has not been handed over just because its status changed.
Yet that is exactly what gets measured: sent, acknowledged, marked done. The system shows green. But a status update does not prove that the other side can carry on, that responsibility has been taken, that anything has actually changed. The business measures delivery and calls it change.
The missing half is the proof
What the arrow is missing is not a return arrow. It is proof that something changed on the other side: responsibility taken, a decision made, a next step you can see. Or an exception that raises its hand when nothing happens.
In air traffic control, a critical instruction is read back. Not because repetition improves the instruction, but because the controller can hear whether it was understood as intended. That still does not prove execution. It proves that the instruction was understood. And it shows the principle: a critical handover needs more than an acknowledgement.
A handover is not complete when something leaves. It is complete when the other side can continue, and the business can tell.
People close the loop by hand
Where the outcome of the handover is not visible to the business, people close the loop by hand, every day. Someone follows up. Someone checks whether anyone has taken it on. Someone notices the customer has already moved on. Your best people do more than carry the work. They detect what the system misses, restore context and correct the course.
It works. Which is exactly why nobody notices. A gap bridged by hand every day eventually looks like a working process. When the load rises, the people don’t suddenly fail. What becomes visible is what was never in the system.
The people are not the gap. They are the reason it stayed invisible for so long.
A business that can correct itself
No workshop is needed. Take one critical arrow and ask four questions: What actually goes across? What should be different on the other side as a result? How does the business know it happened? And what happens when that signal never comes?
If you cannot answer the third question, you cannot tell whether the handover worked. If you cannot answer the fourth, there is no correction built in. Then the handover runs on hope and personal attention.
The prize is not a cleaner handover. When this logic is built into the critical handovers, the business can correct itself: it sees earlier where things stop moving and knows what to change next. That is the part of a company’s mechanics no org chart can show.
An arrow shows intent. What happens next shows whether the connection worked.
Patrick Thole, Disruption Dynamics, Zürich
disruption-dynamics.ch