Efficiency Should Not Depend on Which Team You Are In
- New Way To
- Jan 20
- 4 min read
Updated: Feb 15
Why efficiency gaps exist, why leadership misses them, and what to do first
Leaders rarely wake up thinking “We have an efficiency problem.”They wake up thinking “We are busy, but progress is uneven.”
One team ships quickly and cleanly. Another team struggles with the same type of work. A few people seem to carry an entire department. Meetings multiply. Escalations become normal. Everyone has a story, but no one has a shared picture.
This is not a motivation problem. It is not a talent problem. In most organisations, it is an alignment problem in how work gets done.
The uncomfortable truth: efficiency gaps are usually designed into the system
Efficiency differences between teams almost never come from effort. They come from the invisible details of daily work:
What “good” looks like is clear in one team and ambiguous in another
Approvals are lightweight in one area and heavy in another
Some teams have templates, checklists, and reuse, others start from scratch
One group has stable flow, another is interrupted all day
Handovers are smooth in one chain and broken in another
These are not dramatic failures. They are small choices that compound.
Over time, teams build local fixes. People create workarounds. Strong performers develop their own shortcuts and personal systems. Managers compensate with extra coordination. Everyone adapts.
And that adaptation is exactly why leadership misses the gap.
Why leadership often cannot see the real problem
Leadership usually views the organization through three channels:
Reporting: metrics, dashboards, project status
Escalations: what breaks badly enough to surface
Anecdotes: what people mention in meetings
None of these reveals how work truly happens. They show outcomes, not friction.
Friction lives in places that are easy to ignore because they look small:
Searching for the latest version of a document
Copying data between systems
Waiting on a decision that no one owns
Rework caused by unclear inputs
A handover that bounces back twice
From a distance, this looks like normal work. Up close, it is the real cost.
The pattern behind the pattern: local optimisation creates organisational imbalance
Most teams improve locally. They fix what they can control. They build their own ways of working. That is natural, and often necessary.
But local optimisation creates two side effects:
Fragmentation: the same task is done differently across teams
Unfairness: some people work in a smoother system than others
This is why two departments can have the same tools and still experience different productivity. Tools do not create efficiency. Systems of work do.
The result is a widening gap:
The fast teams get faster
The stuck teams stay stuck
The organisation becomes dependent on a few people who “know how to get things done”
That dependency feels like excellence, until those people leave or burn out.
A practical way to think about team efficiency
If you want to manage this without blame, you need a simple frame that points to work conditions, not personal performance.
A useful lens is to look at friction across five dimensions:
Effort Waste
Where time leaks through manual work, rework, duplication, and searching.
Flow and Predictability
Whether work moves smoothly or gets disrupted by interruptions, waiting, and priority churn.
Clarity and Decisions
How clear priorities, ownership, and decision rights really are.
Coordination and Handover
Where work breaks between teams and comes back for fixes.
Learning and Improvement
Whether better ways of working spread or stay local.
This is not a maturity model. It is a way to see patterns that are normally invisible.
Why common fixes disappoint
When leaders sense uneven productivity, they often reach for familiar levers:
More tools: new platforms, new dashboards, new systems
More training: workshops that make people smarter but not faster
More process: more steps, more forms, more approvals
More pressure: targets, urgency, more meetings
These can help, but they often fail because they treat symptoms, not the underlying pattern.
If the same task is executed in five different ways, training will not standardise it.If decisions are unclear, process will add more waiting.If handovers are broken, pressure increases blame, not flow.
The fix is not more activity. It is better visibility and smarter focus.
What to do first: make the hidden frictions visible without blame
Before you launch another initiative, build a shared picture of how work feels and where it slows down.
You are not trying to map everything. You are trying to find:
Which frictions dominate
Which handovers are most painful
Which recurring tasks are best candidates for deeper comparison
Where small changes would unlock big relief
This first step should be lightweight. If it feels like a big project, you will never get honest participation.
A reflective question
If you compared two teams doing similar work, what would you expect to be different: the people, or the system around them?
Do you want a low-effort way to surface these friction patterns across teams, so you can decide what is worth tackling next? Then take the Friction Pulse.
