7 Signs Your Team Has Coordination Friction
Kinetiq Team
Coordination friction is the tax a team pays for not having agreed how it works. It rarely announces itself. There is no incident report, no line in the budget, and no meeting where somebody says the problem is that nobody knows who decides. It shows up instead as a general sense that everything takes longer than it should, which is a feeling rather than a finding, and feelings do not get fixed.
So here are seven things you can actually observe. Each one is cheap to check, and each points at a specific missing agreement rather than at a person having a bad quarter.
The Seven Signs
1. Work Gets Redone, and Nobody Calls It Rework
Somebody rebuilds a deck because the brief changed. An engineer reworks an integration because the spec was read two ways. Each instance arrives looking like a fresh problem, gets absorbed, and is never counted.
Asana’s Anatomy of Work Index found knowledge workers losing an average of 58 minutes a day to duplicated work alone. Across a team of twenty that is close to 100 hours a week. The test: ask your team, out loud, what they redid this week. If the answers come easily and the number surprises you, you have found your first agreement worth writing down.
2. The Same Decision Keeps Coming Back
You settled it in March. It returned in May, wearing slightly different clothes, and you settled it again. Now it is back.
A decision that will not stay decided was never really made. It was expressed in a room, by whoever spoke last, and never written anywhere someone outside that room could find it. The test: pick a decision from the last quarter and ask three people what was decided and why. Compare the answers.
3. Meetings Exist Mainly to Find Out What Is Happening
SHRM’s workplace research, which we covered in our piece on meeting overload and collaboration debt, found 71 percent of managers describing their meetings as unproductive while the average employee attends eight to twelve a week. The two facts are not in tension. They are the same fact.
A status meeting is a workaround for information that should have been legible without one. The test: cancel one recurring status meeting for two weeks and see what breaks. Usually nothing does, which is its own answer. Occasionally something important surfaces late, and now you know precisely which piece of information the meeting was actually carrying.
4. People Check With You Before Starting
This one flatters managers, which is why it survives. Being consulted feels like being trusted. It is more often a sign that the boundaries of someone’s authority were never drawn, so the safest move is always to ask.
We worked through the distinction in creating clarity without micromanaging. The test: count the messages this week that were requests for permission rather than requests for information. Each one is a decision right that has never been assigned.
5. “Done” Means Different Things to Different People
Design thinks done means approved. Engineering thinks it means merged. Marketing thinks it means live. Everyone is right inside their own function, and the work stalls in the gaps between them.
This is where handoff protocols earn their keep, and the fix is unglamorous: write down what has to be true for a piece of work to move to the next stage. The test: take one item in flight and ask the sender and the receiver, separately, what finished looks like.
6. One Person’s Absence Stops the Work
Somebody takes a week off and three things queue up behind them. Not because they are irreplaceable in principle, but because the context lives in their head and was never externalised.
This is the failure mode we described in why good managers build systems, not dependency. It reads as excellence right up until the moment it reads as risk. The test: look at your last two holidays. What waited?
7. Priorities Move Midweek and Nothing Gets Declined
A new request lands on Wednesday. It goes on the list. Nothing comes off. The list is now longer than the week, and everyone quietly decides for themselves what to drop, which means the organisation’s actual priorities are being set by whoever is least comfortable saying no.
We covered the mechanics of holding the line in setting expectations when priorities shift midweek. The test: name the last thing your team explicitly declined. If nothing comes to mind, you do not have priorities. You have a wish list.
A decision that will not stay decided was never really made. It was expressed in a room, by whoever spoke last, and never written anywhere someone outside that room could find it.
Why These Compound
Individually each sign is survivable, and that is exactly the danger. A team can carry all seven and still ship, because competent people route around broken process by working harder and checking more often. The cost is paid in a currency nobody reports: attention.
Research from the American Psychological Association, which we cited in our piece on context switching, found that interruptions as brief as five seconds can triple error rates on complex cognitive tasks, and that task switching can cut productive capacity by up to 40 percent. Every one of the seven signs above generates interruptions. The checking, the clarifying, the second meeting to confirm the first one.
So the friction does not just slow the work. It degrades the quality of the thinking that goes into it, and it does so invisibly, because nobody attributes a mediocre decision to the fourteen interruptions that preceded it.
Where to Start
Do not try to fix seven things. Pick the one where your test produced the most uncomfortable answer, and write down a single agreement that addresses it. One sentence, somewhere the team can see it. Then leave it alone for a month and see whether it held.
Most teams find that two or three of these signs share a root, and that resolving the root quietly removes several symptoms at once. If you want the fuller picture of how the pieces fit together, our Modern Team Operating System Guide covers the five components these agreements belong to, and the companion piece on the hidden cost of coordination friction works through what these symptoms cost as a team grows.
Related Reading
Written by
Kinetiq Team
The KinetIQ editorial team. We write about the systems behind how work actually gets done: communication, decision-making, accountability, handoffs, and the execution habits that hold up when teams are under pressure.
