Estimated reading time: 19–22 minutes
Growth is usually celebrated as the ultimate indicator of organizational success.
More customers.
More employees.
More products.
More markets.
More revenue.
Yet many organizations discover an unexpected consequence of growth.
Everything becomes slower.
Projects require more approvals.
Simple questions become multi-day discussions.
Hiring takes longer.
Product launches slip.
Customer requests wait in queues.
Innovation loses momentum.
The surprising part is that employees are often working harder than ever.
Productivity at the individual level may remain high while the organization as a whole becomes progressively less responsive.
Organizations rarely become slower because people become less productive.
They become slower because the system requires more work to accomplish the same outcome.
This distinction is one of the most important insights in systems thinking.
Organizational speed is not simply the sum of individual productivity.
It is an emergent property of the entire system.
Decision paths.
Information flow.
Ownership.
Dependencies.
Feedback loops.
Incentives.
Every interaction shapes how quickly work moves through the organization.
This is one of the central ideas behind System Shaping™.
Rather than asking people to work faster, leaders should redesign the conditions that allow work to flow with less friction.
What Makes Organizations Slow?
Most organizations slow down because friction gradually accumulates inside the system.
- Too many approvals.
- Unclear decision ownership.
- Cross-functional dependencies.
- Information bottlenecks.
- Workflow bottlenecks.
- Meeting overload.
- Administrative complexity.
- Long decision queues.
- Poor operating model design.
- Execution bottlenecks.
Each source of friction appears manageable on its own.
Together they create an organization that becomes increasingly difficult to coordinate, increasingly difficult to adapt, and increasingly difficult to lead.
Organizational speed is determined less by how fast people work than by how little friction exists between decisions and execution.
Why Organizations Become Slower (Quick Answer)
Organizations become slower because growth increases coordination, communication paths, and dependencies faster than their operating systems evolve.
| Creates Organizational Speed | Creates Organizational Friction |
|---|---|
| Clear ownership | Shared responsibility |
| Fast decisions | Decision queues |
| Simple workflows | Workflow bottlenecks |
| Direct communication | Information bottlenecks |
| Operational agility | Administrative complexity |
| Enterprise agility | Cross-functional dependencies |
| Adaptive operating model | Execution bottlenecks |
Growth itself is not the problem.
The problem is allowing organizational friction to grow faster than organizational capability.
Growth creates opportunity.
Poor system design turns opportunity into organizational drag.
The Speed Paradox
Leaders often assume that larger organizations should naturally move faster because they possess more talent, more resources, and more expertise.
Reality often produces the opposite outcome.
More employees create more communication.
More expertise creates more handoffs.
More managers create more approvals.
More reporting creates more administrative work.
Every improvement appears reasonable in isolation.
Together they quietly reduce execution speed.
The greatest threat to organizational agility is not lack of effort.
It is the invisible accumulation of friction.
The Organizational Friction Spiral™
Organizations rarely become slow because of one major decision.
They become slower through a predictable chain of interactions.
Growth creates more people.
More people require more coordination.
Coordination creates more dependencies.
Dependencies require additional communication.
Communication generates more meetings.
Meetings increase waiting.
Waiting slows execution.
Slower execution reduces organizational agility.
This is the Organizational Friction Spiral™.
Growth does not automatically create bureaucracy.
It creates more interactions. Those interactions create friction unless the system evolves.
Why Coordination Costs Grow Faster Than Organizations
Many leaders assume organizational growth is linear.
Ten people become twenty.
Twenty become fifty.
Fifty become two hundred.
Headcount grows predictably.
Coordination does not.
Every additional team introduces new communication paths.
Every specialist introduces additional dependencies.
Every department creates another organizational interface.
Every approval increases waiting.
Eventually coordination itself becomes a significant percentage of organizational work.
The fastest-growing cost inside large organizations is often invisible.
It is the cost of coordination.
Waiting Is Hidden Work
Most organizations measure productivity.
Very few measure waiting.
Projects wait.
Approvals wait.
Budgets wait.
Hiring waits.
Customer requests wait.
Products wait.
Ideas wait.
Every hour spent waiting interrupts momentum.
People switch context.
Priorities change.
Knowledge fades.
New meetings become necessary.
Execution slows again.
Waiting is one of the largest forms of organizational waste because almost nobody measures it.
Why Hiring More People Can Reduce Organizational Speed
Adding employees increases capacity.
It also increases organizational complexity.
New employees require onboarding.
Teams become larger.
Communication expands.
Managers coordinate more relationships.
Dependencies multiply.
If workflows remain unchanged, organizational responsiveness often declines despite having more talented people.
The organization becomes busier.
It does not necessarily become faster.
Scaling people without redesigning the operating model usually scales friction as well.
The Organizational Speed Equation™
Organizational speed is determined by more than effort.
It emerges from several interacting system properties.
Organizational Speed = Decision Quality × Information Flow × Clear Ownership ÷ Organizational Friction
This equation is intentionally simple.
Improving only one element rarely transforms organizational speed.
Fast decisions without clear ownership create confusion.
Clear ownership without information flow creates bottlenecks.
Excellent leadership cannot compensate indefinitely for excessive friction inside the system.
The fastest organizations reduce friction before asking people to increase effort.
Executive Examples
Technology
Engineering teams double in size, but software delivery slows because every feature now depends on multiple teams coordinating releases.
Healthcare
Documentation requirements improve compliance but reduce the time clinicians spend with patients, creating operational bottlenecks.
Manufacturing
Reporting expands as organizations grow, yet managers increasingly spend time producing reports instead of solving operational problems.
Financial Services
Risk management becomes stronger while customer responsiveness declines because approval chains continue expanding.
Execution Speed vs Organizational Activity
| Improves Execution Speed | Creates Organizational Activity |
|---|---|
| Fast decisions | More meetings |
| Clear ownership | Shared accountability |
| Rapid information flow | Long reporting chains |
| Operational agility | Administrative work |
| Customer responsiveness | Internal coordination |
| Simple workflows | Workflow bottlenecks |
| Enterprise agility | Organizational busyness |
Busy organizations often mistake movement for momentum.
Fast organizations remove friction so momentum can emerge naturally.
System Shaping™: Designing Organizations That Stay Fast
Most organizations respond to slowing execution by increasing pressure.
More deadlines.
More meetings.
More reporting.
More oversight.
More urgency.
These actions often create even more organizational friction.
They treat slow execution as a people problem instead of a systems problem.
System Shaping™ begins from a different assumption.
Organizations move quickly when work flows naturally through the system.
The objective is not maximum employee effort.
The objective is minimum unnecessary friction.
Fast organizations are not built by demanding more effort.
They are built by removing everything that prevents meaningful work from moving forward.
Characteristics of Organizations That Stay Fast
Organizations that maintain execution speed while scaling tend to share remarkably similar characteristics.
- Decision ownership is obvious.
- Approvals exist only for meaningful risk.
- Information reaches the right people quickly.
- Cross-functional collaboration is intentionally designed.
- Dependencies are continuously reduced.
- Workflow bottlenecks are identified early.
- Processes become simpler over time rather than more complicated.
- Operating models evolve as organizations grow.
- Leaders remove outdated controls instead of continually adding new ones.
- Execution speed is considered a strategic capability rather than an operational metric.
Notice what these organizations are optimizing.
Not individual productivity.
Not employee busyness.
Not administrative control.
They optimize how work moves through the system.
The fastest organizations continuously simplify how value flows from decision to execution.
The Executive Speed Diagnostic™
Before introducing another approval, process, meeting, or reporting requirement, executives should ask:
- Does this reduce or increase organizational friction?
- Where will work spend more time waiting?
- Which workflow bottleneck does this eliminate?
- Could clearer ownership replace another approval?
- Will customers experience faster outcomes?
- Does this improve organizational responsiveness?
- Which existing process can be removed if this one is added?
- Will this strengthen execution speed—or simply create more activity?
- How will this affect enterprise agility one year from now?
- Are we improving the system or asking people to compensate for it?
These questions shift leadership attention from managing people to designing better systems.
Frequently Asked Questions
Why do organizations become slower over time?
Organizations become slower because coordination, communication paths, approvals, and dependencies grow faster than their operating systems evolve. The resulting friction gradually reduces execution speed and organizational agility.
What causes organizational friction?
Organizational friction is commonly caused by unnecessary approvals, workflow bottlenecks, excessive meetings, unclear ownership, poor information flow, administrative complexity, and cross-functional dependencies.
Why doesn’t hiring more people always improve performance?
Additional employees increase communication, coordination, and management requirements. Without redesigning the operating model, organizational complexity often grows faster than productive capacity.
How can organizations improve execution speed?
Execution speed improves when organizations simplify decision paths, reduce dependencies, improve information flow, eliminate unnecessary work, and continuously redesign systems to reduce friction.
Is organizational speed the same as productivity?
No. Productivity measures individual output. Organizational speed measures how efficiently an entire system converts decisions into meaningful outcomes.
Conclusion: Speed Is an Emergent Property of System Design
Organizations rarely lose speed because people stop caring.
They lose speed because friction quietly accumulates.
Another approval.
Another dependency.
Another meeting.
Another workflow.
Another reporting requirement.
Each addition appears insignificant.
Together they fundamentally reshape how the organization operates.
Growth creates coordination.
Coordination creates friction.
System design determines whether friction becomes permanent.
The organizations that sustain execution speed over decades are not necessarily those with the largest budgets or the smartest people.
They are the organizations that continually redesign their operating systems to remove friction before it becomes structural.
That is the purpose of System Shaping™.
Not making people work faster.
Designing systems where speed, adaptability, execution, and collaboration emerge naturally.
The future belongs to organizations that scale clarity faster than they scale complexity.
Continue Exploring Organizational Systems
- Why Organizations Create Complexity Instead of Clarity
- Why Organizations Optimize the Wrong Problems
- Why Organizations Create Too Many KPIs
- Why Decision Making Slows Down as Organizations Grow
- Why Organizations Become Bureaucratic
- The Incentive Trap
- What Are Feedback Loops?
- What Are Leverage Points?
- What Is Adaptive Leadership?
- What Is Systems Leadership?
- What Is System Shaping?
- Organizational Change Assessment
Recommended external references: