A piece of work leaves one team and arrives at another. On paper the handoff is clean: the ticket is reassigned, the file is attached, the box is checked. But the team receiving it doesn't have what it actually needs. They re-open questions the last team already answered. They call the customer back to re-explain something that was explained two days ago. The work moves forward — but the context didn't move with it.
If you run a service organization, you have watched this happen. Information gets lost between teams. Handoffs between departments fail in ways nobody can quite point to. And the explanation usually offered — someone dropped the ball — almost never fits, because it keeps happening to different people on different days. When a problem recurs across people, the cause is rarely the people.
Why context doesn't survive a team transfer
There is research that explains this better than the dropped-ball theory does. In 1996, Gabriel Szulanski studied 122 transfers of best practice inside eight large companies — the kind of internal handoff that should be easy, because everyone works for the same firm. He expected the main barrier to be motivation: people not wanting to share. That is not what he found.
The largest barriers to moving knowledge from one part of an organization to another were not motivational. They were structural. The receiving side's capacity to absorb what was handed over. The ambiguity around why the work is done the way it is. The difficulty of the relationship between the team handing off and the team receiving. Szulanski named the pattern internal stickiness — the friction that makes knowledge resist moving, even when everyone involved is willing to move it.
Here is the practical version. The part of a handoff that's easy to transfer is the part that's already written down. The part that doesn't transfer is the context: the reason this client gets handled differently, the workaround everyone uses because the system errors out, the half-step that never made it into the SOP. That knowledge lives inside the team that did the work. The checklist crosses the boundary. The context stays behind.
What it looks like as an operational signal
Most organizations only see the consequence — a customer escalation, a missed deadline, a redo — and treat each one as an isolated incident. The incident gets resolved. The condition that produced it doesn't, because the condition isn't visible on any report. It lives in the gap between two teams, which is exactly the place no single manager owns.
This is the gap Organizational Intelligence is built to read. Sigma G looks at four things in any recurring friction event — the Challenge that surfaced, who took Ownership of it, the Drive that went into resolving it, and the Learning Strength that came out the other side. A handoff that keeps losing context produces a recognizable shape: real effort goes in, the same problem comes back, and ownership of the gap sits with no team in particular. High Drive, low Learning Strength, diffuse Ownership. That shape is a leading indicator — it shows up while the work is still moving, well before it surfaces as turnover, a lost account, or a quarter that came in soft.
The cost is real even though it never gets a line item. Every re-explained handoff is duplicated labor. Every redo is rework. For a mid-sized service operation, rework and the quiet drain of work crossing boundaries twice is one of the larger costs hiding inside "normal" operations — our friction calculator puts a conservative, BLS-sourced number on it for an organization your size. The point isn't the precise figure. The point is that structural friction has a price, and a recurring handoff failure is structural friction you can actually locate.
The reason this matters now: the gap is fixable, but only if you can see it before it compounds. A handoff that loses context this quarter trains people to stop expecting context next quarter. They build private workarounds. The operation keeps running — slightly slower, slightly more dependent on a few people who remember how things really work — and the drift never trips an alarm.
If this pattern feels familiar and you're wondering why your existing instruments never flagged it, that's the right question to ask next. Here's why engagement surveys won't tell you where your team stopped improving — and what reads the signal instead.