Process Overhead

You're seeing it when an engineering team spends more time in sprint planning, standups, retrospectives, and ticket grooming than actually writing and shipping code. The process meant to enable delivery now impedes it.

You're seeing it when a simple decision — changing a landing page headline — requires a brief, a review meeting, stakeholder sign-off, legal approval, and a change management form. The overhead dwarfs the work.

Track the process-to-output ratio in your critical workflows. When process overhead exceeds 30% of total time, something is wrong. Cut ruthlessly — most processes were added for a reason that no longer exists.

Bezos waged a permanent war against process overhead at Amazon. The two-pizza team rule limited team size to reduce coordination costs. The six-page memo replaced PowerPoint presentations to eliminate the overhead of preparation theatrics. "Disagree and commit" eliminated the overhead of consensus-seeking. The single-threaded leader model assigned one person full ownership to avoid the overhead of cross-team coordination. Bezos understood that as companies scale, process overhead grows exponentially unless deliberately fought. Every process Amazon added had to justify its existence in terms of customer value — internal convenience was never sufficient justification. For founders, the discipline is constant: every process you add must earn its overhead, and processes that stop earning must be eliminated.