What is org friction in software teams?

Org friction's the hidden overhead—dependencies, processes, meetings—that turns a 1-day task into weeks. Unmeasured, it eats capacity.

How do you measure org friction?

Run a Friction Log: track every wait, switch, block in a shared doc for a sprint. Tally hours lost. Shock execs with totals.

Does fixing org friction really boost velocity?

Yes—often 30-50% gains. But it takes leadership guts, not just dev tweaks.

🏗️ DevOps & Infrastructure

That 5-Point Story Taking Three Weeks? Blame Org Friction, Not Your Estimates

Imagine estimating a simple feature at 5 points, only for it to drag on for weeks. It's not poor guessing—it's your company's hidden drag called org friction, devouring productivity.

theAIcatchup Apr 09, 2026 3 min read

Frustrated software engineer tangled in red tape and meeting icons while code waits

⚡ Key Takeaways

Estimates are accurate; org friction (30-40% capacity drain) is the real delay culprit. 𝕏
Use a Friction Log to make invisible drags visible and force org changes. 𝕏
Blame-shifting to estimates breeds cynicism—fix incentives, processes, and silos instead. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#agile delivery #agile estimation #dev velocity #org friction #software delivery #software estimation #software velocity #team productivity #team velocity

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

GitLab's AI Prompts Promise Faster Shipping — But Who's Really Winning?

Docker Saved Our Python Team From Five Months of Silent Chaos

One Dev's Year-Long Rewrite Nightmare: Why Estimates Always Lie

Kubernetes Just Killed Ingress NGINX: Half Your Clusters Are Suddenly Vulnerable

Stay in the loop