Coordination friction: When strong teams produce weak handoffs
There is a performance problem that puzzles leadership teams more than any other, because every individual piece of evidence says things are fine. Operations hits its numbers. The credit team is disciplined. IT delivers its projects. Customer-facing units know their clients. And yet the work that crosses between these capable teams – the product launch, the client onboarding, the regulatory submission – grinds, stalls, and arrives late or reworked. Strong teams, weak handoffs.
The friction is easy to feel and hard to see. It lives in the spaces the org chart does not draw: the assumptions one team makes about what another needs, the information that was sent but not understood, the priorities that are perfectly rational inside each unit and mutually incompatible between them. Because it belongs to no one, it is managed by no one – and what is managed by no one is paid for by everyone, in cycle time, rework, and the slow-burning frustration of people who are doing their jobs well and still watching the joint outcome fall short.
What coordination friction actually signals
The tempting reading is interpersonal: these teams do not get along, those two department heads have history. Occasionally true, rarely the cause. When friction appears at multiple seams of the same organization, it signals conditions: goals and incentives defined per unit with no shared measure for the work between them; communication practices that move information without moving understanding; workload levels that leave no slack for the coordination work itself, so every handoff is done in a hurry by people who have no time to do it twice – and then do; and the absence of routines where the teams involved see the whole flow rather than their segment of it. This, again, is the Intention vs Experience Gap in operation: leadership intends one organization pulling together; people experience a relay race run in the dark.
Why the usual responses fall short
The standard remedies are the offsite and the process map. The offsite builds goodwill that lasts until the first Monday deadline; the process map documents a flow that reality left behind two quarters ago. Both treat coordination as either a relationship problem or a documentation problem. It is neither. It is a capability that lives in daily practice – in how teams plan across their boundary, surface problems early, and hold a shared picture of the work – and daily practice does not change because a document or a pleasant memory says it should.
What changes it
Reducing coordination friction starts with locating it precisely: which seams, which handoffs, what the people on both sides actually experience there – the kind of picture a whole-organization diagnostic produces and anecdote never does. The development that follows works on the seam itself: teams building shared routines across the boundary, leaders aligning goals and priorities so that cooperation stops costing the cooperating side, and communication practices that carry context, not just content. Built this way – in the live work, on the real handoffs – coordination stops being a virtue the organization hopes for and becomes a capability it maintains, and measures, year after year.
mHub helps organizations close the gap between what leadership intends and what their people experience – through the structured implementation of our Workplace Performance System.