What is org friction in software teams?

Org friction's the hidden overhead—cross-team waits, process gates, silos—that turns a quick task into weeks of drag, unmeasured by estimates.

How do you reduce org friction?

Log it ruthlessly for a sprint, categorize, escalate patterns. Slash meetings, align incentives, sunset old processes. Velocity soars.

Nope—estimates nail the work, ignore the org. Fix the environment, not the prediction.

🧠 Engineering Culture

Your team nails the estimate. Ships weeks late. Blame game starts. But it's not you—it's the org's hidden drag eating 40% of your time.

theAIcatchup Apr 09, 2026 3 min read

Estimates are accurate; org friction (30-40% capacity loss) is the real delay culprit. 𝕏
Use a Friction Log to make invisible drag visible and slash it. 𝕏
Leadership must own reduction—blaming estimation just breeds pessimism. 𝕏

Published by

Ship faster. Build smarter.

#agile pitfalls #estimation errors #org friction #team velocity

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to