Organisational Drag: The Weight Slowing Your Team Down, One Decision at a Time

In short: organisational drag is what a business feels when no single thing is broken, but everything takes slightly longer than it should. It isn't one blocker you can point at and fix — it's dozens of small, avoidable pieces of resistance spread across every decision, handoff and sign-off, each too small to notice alone. This is the same pattern behind why capable teams get bogged down, seen from a different angle: not the signs, but the accumulated weight itself, and what actually reduces it.

What Organisational Drag Actually Is

Borrow the term from physics, because it's the right word, not just a catchy one. Drag isn't a single obstacle in the way — it's resistance distributed across every surface moving through the system. A bottleneck has an address: find it, widen it, done. Drag doesn't. It's smeared thinly across hundreds of ordinary moments — a sign-off that takes a day instead of an hour, a handoff nobody follows up on straight away, a decision that's technically someone's to make but gets run past another desk anyway. Clear every bottleneck in a business and it can still feel like wading through wet sand, because the resistance was never concentrated where anyone was looking.

Where It Comes From — and Why It Hides

Drag is decision friction — the resistance a system puts in the way of any single decision — showing up on repeat, across the whole business, all day. No single piece of it was designed to slow anything down: a sign-off added to catch one rare mistake, a second check layered on after last year's error, a metric tracking effort because effort was easier to count than outcome. Each made sense on its own. None were built to work together, and nobody owns the total. That's misalignment, not malfunction — several individually sensible parts of the system quietly pointed in slightly different directions. Drag is what misalignment feels like from the inside, before it's severe enough to have an obvious single cause.

That's also why it's so easy to miss. Each person only ever sees their own step, and from inside any one step the delay looks reasonable — of course this needs a second look, of course that needs sign-off. Only tracing the whole path end to end makes the resistance visible. Which is why drag gets reported as a mood, not a fact: "we're just really busy," "everything takes longer than it used to." Those aren't vague complaints — they're accurate descriptions of something real that genuinely has no single cause, which is exactly why "let's fix the process" keeps going looking for a bottleneck and, correctly, not finding one.

The Compounding Cost

This doesn't need to be dramatic to matter. Say a business makes a hundred routine decisions a day, and each picks up one avoidable extra minute — a moment's hesitation about whether it's really theirs to call, a message sent to check rather than just deciding. That's not a minute. It's well over ninety minutes of the day spent on resistance before anyone's produced anything, with everything still queued behind it. The exact number will differ everywhere and is beside the point — what matters is that drag compounds, quietly, on ordinary decisions, not dramatic ones.

Bain & Company puts a figure on the total: the average company loses more than a fifth of its productive power to exactly this kind of drag — not a one-off cost, a continuous one.

How to Reduce It, Without Adding Headcount or Process

The instinct once drag is named is to add a new process to manage it — which just adds more resistance on top. The better move is closer to what an engineer does with real drag: reduce the surface area exposed to resistance, not push harder through it.

Cut what doesn't earn its place. For every sign-off or "just loop me in," ask what it's actually protecting against, and whether that risk is still real. Plenty won't be — a leftover reaction to one bad outcome years ago, still taxing every ordinary decision since.

Give every handoff a named owner. Drag concentrates hardest at the seams between teams, where work goes quiet because it's genuinely nobody's job to notice it's arrived. A named owner and a clear expectation of when it moves again closes off one of the most reliable sources of resistance in the system.

Check what each step actually rewards. A step that mainly protects the person taking it — by spreading a name across the decision — will survive forever, whether or not it protects anyone else. Worth being honest about which one it's doing.

Frequently asked questions

Is organisational drag the same as a bottleneck? No — a bottleneck is one visible choke point with an obvious fix. Drag has no single address; it's resistance spread across many ordinary steps, which is why clearing a bottleneck often doesn't make the business feel any faster.

How is this different from decision friction? Friction is the mechanism, in any one decision. Drag is what that mechanism produces at scale, across hundreds of decisions a day — the cause and its accumulated, felt effect.

Do we need to hire more people to fix this? Usually not. It's a resistance problem, not a capacity problem — the same team typically moves faster once unnecessary resistance is removed.

Does reducing drag mean cutting corners? No. It means being honest about which checks protect something real and which mainly protect whoever signs off. Genuinely consequential calls still deserve real scrutiny.

Where do we start? Pick one routine decision type and trace exactly how many steps it passes through before it's settled — most teams are surprised by the count. For a broader first read, the Friction Factor survey scores your team on this exact scale, from a healthy core through frequent drag to systemic misalignment, in a few minutes.

---

Conan Magill, Founder, Unleashed Operations — former Fonterra programme manager and Manta5 COO, whose MBA research surveyed roughly 200 project managers on what actually drives decision quality.

Last updated: 25 July 2026