Your CFO can probably tell you exactly what labor costs.
But can they tell you how much organizational friction costs?
That's harder.
Friction doesn't arrive as an invoice.
It hides inside ordinary work.
Employees attend meetings they don't need to attend.
Managers approve decisions that don't require managerial approval.
Teams enter the same information into multiple systems.
People wait for responses.
Reports are created and never used.
Work gets corrected because instructions weren't clear.
Employees navigate outdated processes everyone knows are inefficient.
Each incident looks small.
Collectively, they may represent one of the largest untapped productivity opportunities in the organization.
Productivity Isn't Just an Employee Problem
When productivity falls, the conversation often turns toward workers.
Are employees working hard enough?
Are remote employees productive?
Do we need better performance management?
Can AI increase individual output?
Those questions may have value.
But they can also begin in the wrong place.
Sometimes employees aren't the productivity problem.
The organization is.
A highly productive employee placed inside a poorly designed system eventually becomes less productive.
The best driver in the world cannot overcome a highway filled with unnecessary tollbooths.
The Meeting Tax
Consider meetings.
One hour doesn't sound expensive.
But put twelve employees in the room and you've consumed twelve hours of organizational capacity.
Make it weekly and you've consumed more than 600 hours annually.
Now multiply that across the organization.
Some meetings create substantial value.
Others exist because they have always existed.
If a recurring meeting doesn't support a decision, coordination, problem-solving, or meaningful communication, leaders should ask what return the organization receives for the capacity invested.
Calendar time is workforce capacity.
Treat it accordingly.
The Approval Tax
Approvals create another hidden cost.
Organizations accumulate them gradually.
Something goes wrong, so an approval is added.
Risk increases, so another layer appears.
A new executive wants visibility, so another checkpoint develops.
Eventually employees spend significant time requesting permission rather than producing value.
Approvals can absolutely protect organizations.
But each one should earn its existence.
If a $500 decision requires three executives, the approval process may cost more than the risk it was designed to control.
The Rework Tax
Few things consume capacity as quietly as rework.
An unclear assignment creates the wrong deliverable.
A broken handoff produces errors.
Poor data requires reconciliation.
A rushed implementation creates cleanup.
Employees redo work because different departments use different assumptions.
The payroll expense looks exactly the same.
But productive capacity has vanished.
That's why leaders should measure not only how much work gets completed, but how much work must be completed more than once.
The Work Nobody Questions
Every organization accumulates legacy work.
Reports.
Processes.
Meetings.
Positions.
Approvals.
Policies.
Spreadsheets.
Nobody remembers exactly why some of them started.
But people keep doing them.
This creates an unusual organizational phenomenon:
New work gets scrutinized before approval.
Old work can continue indefinitely without proving its value.
Over time, organizations become cluttered.
Then leaders add technology hoping to make employees more productive.
Sometimes the better first step is simply to stop doing unnecessary work.
AI Won't Fix Bad Work
This matters enormously in the AI era.
Automating an unnecessary process doesn't make it necessary.
Using AI to produce an irrelevant report faster doesn't create value.
Adding sophisticated technology to a dysfunctional workflow can simply accelerate dysfunction.
Before automating work, ask whether the work should exist.
Then ask whether it should be simplified.
Then determine what technology can improve.
That sequence matters.
Capacity Returned May Be the Better Metric
Organizations frequently justify productivity initiatives through cost reduction.
What if leaders also measured capacity returned?
Suppose process redesign saves a team 20 hours per week.
That capacity could support customers.
Develop new products.
Reduce overtime.
Improve quality.
Accelerate a strategic initiative.
Train employees.
Or simply make an unsustainable workload sustainable.
The value isn't necessarily a headcount reduction.
It is organizational capacity available for something more important.
That's a far more strategic definition of productivity.
Make Friction Visible
Executives should begin asking employees:
What work consumes time without creating proportional value?
Where do you wait?
What gets duplicated?
What requires unnecessary approval?
Which meetings could disappear?
What process routinely creates rework?
What information do you produce that nobody appears to use?
Where does technology make work harder rather than easier?
Employees often know exactly where the friction lives.
They experience it every day.
Productivity Is an Organizational Design Question
There will always be legitimate conversations about individual performance.
But organizations should resist treating productivity primarily as a question of employee effort.
Before demanding more from people, examine what the organization is demanding of them.
How much capacity disappears into friction?
Your financial statements probably won't tell you.
Your employees can.
And the productivity opportunity hiding there may be larger than the next cost-cutting initiative.
