Being Busy Is Not the Same as Being Productive
A company can be fully occupied while customer outcomes remain slow. Separate activity from useful output by examining waiting, rework, bottlenecks and priorities.
O02 · FOUNDATION ARTICLE · FIEASE BUSINESS OPERATIONS
A company can have everyone working continuously and still perform badly.
Emails are flying.
Phones are ringing.
Managers move from meeting to meeting.
Employees stay late.
Orders are being “followed up.”
Teams are solving urgent problems.
People say they are overloaded.
More employees are hired.
Yet customers still wait, deadlines slip, errors recur and managers continue to complain that there is not enough capacity.
How can that happen?
Because activity is not the same thing as productive output.
The distinction is more important than it first appears.
The U.S. Bureau of Labor Statistics defines labour productivity as the relationship between output and the labour used to produce it. OECD similarly defines labour productivity using output per hour worked—and importantly notes that productivity is not simply a reflection of personal effort. Capital, technology, intermediate inputs, organisational changes, efficiency and scale also influence how much output each hour can produce. (oecd.org)
Translated into business language:
Busyness tells you that resources are being consumed. Productivity tells you what useful output those resources are producing.
A person can therefore work extremely hard inside an extremely inefficient system.
That is not an employee contradiction.
It is an operations problem.
What is the simplest difference between activity and productivity?
Consider two teams.
Team A
Works 400 hours in one week.
Completes 500 accurate orders.
Team B
Works 500 hours.
Completes 350 accurate orders.
Which team was busier?
Team B consumed more labour time.
Which team produced more useful output?
Team A.
Obviously real businesses are more complicated than this.
Output may differ in complexity and quality.
But the principle holds:
hours worked and work completed are not the same measure.
What exactly is productivity?
At the simplest level:
Productivity = Output ÷ Input
For labour productivity:
Useful output ÷ labour input
The unit of output depends on the business.
Examples:
Manufacturer:
good units per labour hour.
Warehouse:
correct orders picked per labour hour.
Professional-services business:
completed client deliverables per delivery hour, adjusted for quality and complexity.
Accounts payable:
valid invoices processed per FTE or labour hour.
Customer support:
successfully resolved cases relative to resource consumed.
But there is an important warning.
A productivity measure becomes dangerous when “output” is poorly defined.
What do you mean by “useful output”?
Imagine a factory produces 1,000 components.
Two hundred are defective.
If management measures only pieces produced, productivity appears high.
If it measures conforming pieces produced, the picture changes.
Now imagine a call centre measures:
calls handled per employee
Agents shorten calls.
But customers repeatedly call back because issues remain unresolved.
The activity measure improved.
Customer output did not.
The same happens in Sales.
A salesperson makes 100 calls.
Another makes 40.
Which is more productive?
You cannot tell until you know:
who they contacted;
whether conversations were relevant;
what opportunities resulted;
what ultimately converted.
Productivity requires a meaningful definition of output.
Isn't “work harder” still a valid way of increasing output?
Sometimes.
If a temporary surge occurs and the process is already reasonably effective, additional effort can increase output.
But “work harder” is a weak permanent operating strategy.
Suppose an employee spends eight hours doing this:
3 hours performing useful work;
1 hour correcting errors;
1 hour searching for information;
1 hour waiting/chasing approvals;
1 hour entering duplicate information;
1 hour in low-value coordination.
Asking that person to work an additional hour may produce slightly more output.
A better question is:
Why are five hours being consumed around three hours of useful work?
Improving the system may create more capacity than adding effort.
Does that mean every minute not directly producing something is waste?
No.
This is where simplistic efficiency programmes become dangerous.
Some work does not directly create the customer deliverable but is necessary.
Examples:
quality control;
financial controls;
maintenance;
safety;
regulatory work;
planning;
training.
The proper distinction is not:
customer-facing = good
and:
everything else = bad.
Lean thinking provides a more useful lens.
Lean Enterprise Institute distinguishes value-creating work, incidental/necessary work and waste. Its classic seven wastes include overproduction, waiting, unnecessary conveyance, unnecessary processing, excess inventory, unnecessary motion and correction/rework. (lean.org)
These ideas began in manufacturing, but the logic translates surprisingly well to office and service work.
What does waste look like outside a factory?
Consider the seven classic categories.
| Lean concept | Manufacturing example | Office/service equivalent |
|---|---|---|
| Overproduction | Producing before demand | Reports nobody uses |
| Waiting | Machine/operator waiting | Waiting for approval |
| Conveyance | Unnecessary material movement | Moving files/information repeatedly |
| Overprocessing | More processing than required | Duplicate data entry |
| Inventory | Excess physical stock | Large backlog/WIP |
| Motion | Searching/reaching/walking | Searching systems/files |
| Correction | Scrap/rework | Correcting invoice/proposal/data errors |
Lean Enterprise Institute explicitly includes searching for tools or documents as examples of unnecessary motion and describes correction as inspection, rework and scrap. (lean.org)
The language may come from manufacturing.
The economic logic is universal:
resource is being consumed without equivalent progress towards the required outcome.
But if employees are doing these things, aren't they still working?
Absolutely.
That is exactly why waste is difficult to see.
Suppose Accounts Payable receives an invoice without a purchase-order number.
An employee:
checks ERP;
searches emails;
contacts Procurement;
Procurement contacts the requester;
requester searches old communication;
Finance follows up;
supplier calls Finance;
Finance responds.
People may spend an hour dealing with the issue.
Every minute is genuine human effort.
But most of the effort was created because the correct input did not exist at the right point in the process.
The employee is not the waste.
The system created unnecessary work.
That distinction changes management behaviour.
A poor manager asks:
“Why is this employee taking so long?”
A better manager asks:
“Why does the process require all of this effort?”
Why do organisations mistake busyness for productivity?
Because busyness is visible.
Managers can see:
emails;
calls;
meetings;
long hours;
employees moving;
overflowing inboxes;
open tasks.
The actual flow of customer value is often less visible.
A company may know how many emails were sent.
But not:
how many orders were completed right the first time;
how long work waited;
what percentage needed correction;
where backlog accumulated;
which constraint controlled overall output.
Activity gives management the comfort of motion.
Output requires better measurement.
Isn't measuring employee utilisation enough?
No.
Utilisation answers:
How much of the available resource time is occupied?
That is different from:
How much useful output does the system produce?
A person can be 100% occupied by:
useful work;
rework;
waiting-related follow-up;
unnecessary reporting;
duplicate entry.
From the calendar's perspective, all four look like utilisation.
From the business's perspective, they are economically different.
Can high utilisation actually make a process worse?
Yes, especially where work arrives with variability.
Imagine every member of a service team is permanently occupied.
A new urgent case arrives.
Nobody has capacity.
The case waits.
Another arrives.
It waits too.
Soon:
backlog grows;
priorities are changed;
people interrupt existing work;
work-in-progress rises.
Operations research formally studies this through queueing systems. MIT's materials on queueing and Little's Law show the mathematical relationship between the number of items in a system, throughput/arrival rate and the time they spend in the system. (ocw.mit.edu)
You do not need advanced mathematics to understand the management implication:
A completely loaded system has little ability to absorb variability without creating queues.
Maximum individual utilisation and best customer flow are therefore not always the same objective.
What is waiting, and why is it so important?
Waiting occurs whenever work is ready to move but cannot.
Examples:
purchase request waiting for approval;
customer order waiting for credit clearance;
proposal waiting for pricing;
component waiting for inspection;
invoice waiting for documentation;
candidate waiting for interviewer feedback;
project waiting for customer information.
Employees may remain busy by moving to another task.
That creates an illusion that no capacity is being lost.
But the outcome has stopped progressing.
That is why a business should distinguish:
Touch time
How long people actually work on an item.
Lead/flow time
How long the complete item takes from beginning to end.
A process may contain two hours of actual effort spread over five days.
Reducing the two hours by ten minutes may have much less value than removing two days of waiting.
Can we put a mathematical relationship behind that?
Yes.
One of operations research's most useful relationships is Little's Law.
For a stable system:
Work in Process = Throughput × Flow Time
or commonly:
L = λW
where:
L is the average number of items in the system;
λ is average throughput/arrival rate;
W is average time an item spends in the system.
MIT identifies Little's Law as one of the foundational relationships used in operations and queueing analysis. (betterworld.mit.edu)
What does Little's Law mean in plain English?
Suppose a business completes:
20 jobs per day
and an average job spends:
5 days
inside the process.
Average work in process is approximately:
20 × 5 = 100 jobs
Now suppose the company can reduce average flow time to:
3 days
while keeping throughput at 20.
Average WIP becomes:
20 × 3 = 60 jobs
Forty fewer jobs are circulating inside the process.
That can mean:
less tracking;
fewer status questions;
less scheduling complexity;
less money tied in unfinished work, depending on the process;
faster customer completion.
It helps explain why “starting more work” can make an organisation feel busy without making it finish more work.
Can too much work-in-progress reduce productivity?
Yes.
Imagine a consulting company has 15 employees.
Management starts 30 projects simultaneously so nobody is ever idle.
Employees constantly move between:
Project A;
Project B;
urgent customer feedback;
internal reviews;
Project C.
Many projects are active.
Few are finished.
The organisation looks extremely busy.
Customers experience delay.
A healthier system may deliberately limit simultaneous work and focus on completion.
This is a fundamental operations principle:
Starting work and finishing work are not the same thing.
What is rework?
Rework is work that must be performed again because an earlier output was incorrect, incomplete or unsuitable.
Examples:
correcting an invoice;
rewriting a proposal;
remanufacturing a defective component;
re-entering wrong customer information;
fixing a shipment;
repeating a customer-support interaction.
Rework is especially damaging because the business pays twice:
once for the original work,
then again for correction.
ASQ's cost-of-quality framework classifies rework, scrap, reinspection and downtime as internal failure costs, while returns, warranty, complaints and similar consequences occur when failure reaches the customer. (careers.asq.org)
Can rework make a team look as though it needs more employees?
Very easily.
Consider a team processing 2,000 transactions each month.
Suppose 15% require 20 minutes of correction.
Transactions requiring correction:
2,000 × 15% = 300
Correction time:
300 × 20 minutes = 6,000 minutes
That is:
100 hours per month
If the defect is avoidable, 100 hours of apparent workload is actually failure demand created by the existing process.
Management may say:
“We need more staff.”
Possibly.
But first ask:
“Why did we create 100 hours of avoidable work?”
What is failure demand?
It is work created because something did not work correctly the first time.
For example:
Customer:
“Where is my order?”
Why did the call occur?
Because delivery/status visibility failed.
Customer:
“My invoice is wrong.”
Why did the contact occur?
Because billing failed.
Customer:
“You closed my complaint, but the problem is still there.”
The second interaction is caused by failure in the first.
A team can therefore become overloaded partly by work the organisation created for itself.
What about searching for information?
Searching feels minor.
But repeated friction compounds.
HYPOTHETICAL EXAMPLE
Suppose 50 employees each spend an average of 15 minutes daily looking for:
latest files;
approval status;
customer history;
current pricing;
product information.
Daily time:
50 × 15 minutes = 750 minutes
= 12.5 hours per day
Across 22 working days:
275 hours per month
That is more than one full-time person's monthly working capacity.
There may be no accounting line named:
“Cost of finding things.”
The capacity is still consumed.
What about duplicate data entry?
The same principle applies.
Imagine customer information is entered into:
CRM.
Excel.
ERP.
A logistics portal.
Why?
Sometimes systems genuinely require it.
Sometimes it is simply the historical result of disconnected processes.
Duplicate entry creates three problems:
additional labour;
increased error probability;
conflicting versions of truth.
Busy employees may therefore be performing work that better process and information architecture could remove entirely.
Are meetings a productivity problem?
Some are.
But meetings are not inherently waste.
A good meeting can create enormous value by enabling:
decisions;
problem-solving;
coordination;
risk management.
The useful question is:
What outcome does this meeting enable, and is a meeting the lowest-cost effective mechanism?
Remember that meeting cost is collective.
A one-hour meeting with ten people consumes ten labour hours.
That can be excellent value.
Or almost none.
What about approvals?
Approvals often begin as sensible controls.
A mistake occurs.
Management adds an approval.
Another issue occurs.
Management adds another.
Years later:
routine transactions require several managerial signatures.
Nobody remembers which risk each approval was designed to control.
The process becomes slow while senior managers become busy processing low-value decisions.
Approval design should ask:
What risk exists?
How material is it?
What authority level is appropriate?
Can rules handle normal cases?
Can only exceptions escalate?
Controls should reduce meaningful risk.
Otherwise they may become delay disguised as governance.
Why is unnecessary “follow-up” such a strong warning sign?
Follow-up is often evidence that normal workflow is not visible or reliable.
Employees repeatedly ask:
“Did you receive it?”
“What is the status?”
“When will it be done?”
“Has this been approved?”
Individual messages seem small.
Across hundreds of transactions, they become a shadow process.
A process that requires constant chasing is often not fully controlled by its official workflow.
What is overprocessing?
Lean defines overprocessing as doing more work than necessary for the customer or purpose. (lean.org)
Office examples include:
reports nobody uses;
excessive formatting;
duplicated reviews;
unnecessary levels of precision;
entering information already available elsewhere;
preparing analysis that does not change a decision.
The key question is:
Who uses this output, and what decision or outcome does it improve?
If nobody can answer, investigate.
Can too much output actually reduce productivity?
Yes.
This sounds paradoxical.
Lean's concept of overproduction shows why.
Suppose customer demand is 100 units.
A production line produces 130 to improve output-per-hour and machine-utilisation metrics.
The dashboard looks good.
But the additional 30 units now require:
material;
storage;
handling;
working capital;
tracking.
Lean Enterprise Institute gives precisely this kind of example: output and apparent efficiency can look strong while the business is simply creating inventory ahead of actual need. (lean.org)
So even “more output” is not necessarily productive if the output is not required.
Productivity has to be connected to useful demand.
What is the difference between productivity, efficiency, effectiveness and utilisation?
These terms are often mixed together.
| Concept | Question |
|---|---|
| Activity | What are people doing? |
| Output | What was completed? |
| Productivity | How much useful output was created relative to input? |
| Efficiency | How much resource was needed to produce that output? |
| Effectiveness | Did we achieve the intended outcome? |
| Utilisation | How much available capacity was occupied? |
A business can be:
highly utilised,
apparently productive,
but ineffective.
For example:
A factory produces very large volumes nobody currently needs.
Employees are busy.
Machines are utilised.
Output is high.
Customer value is not.
Why is productivity not purely an employee-performance issue?
This is one of the most important lessons from the OECD definition.
Output per hour depends partly on factors such as:
capital/equipment;
technology;
process design;
organisation;
intermediate inputs;
scale.
OECD explicitly cautions that labour productivity only partially reflects workers' personal capabilities or intensity of effort. (oecd.org)
So when productivity is weak, management should not jump immediately to:
“People aren't working hard enough.”
Investigate the operating environment.
What should management measure instead of busyness?
A balanced productivity view should include several dimensions.
APQC recommends balanced measurement across areas such as cost effectiveness, cycle time, process efficiency and staff productivity rather than optimising one measure in isolation. (apqc.org)
A practical dashboard might contain:
Useful output
How much acceptable work is completed?
Lead time
How long does an item take from start to finish?
First-time-right
What percentage is correct without rework?
Backlog
How much work is waiting?
WIP
How much unfinished work is circulating?
On-time completion
How often is the promise met?
Constraint capacity
What is limiting the system?
Cost per output
Where economically meaningful.
These metrics describe the system much better than:
“Everyone seems busy.”
What should productivity mean in different departments?
There is no universal measure.
Manufacturing
Possible measures:
good units per labour hour;
first-pass yield;
cycle time;
scrap/rework;
on-time output.
Warehouse
accurate orders picked;
lead time;
picking productivity;
errors;
backlog.
Finance
transactions completed;
close cycle;
error/rework rate;
exceptions;
cost per transaction.
Customer service
issues resolved;
first-contact resolution;
customer wait;
repeat contacts;
quality.
Professional services
completed milestones;
project lead time;
utilisation;
rework;
on-time delivery;
project economics.
The metric should reflect the actual desired outcome.
Why can a department's productivity improvement hurt the business?
Because the organisation is a system.
Suppose Customer Service is told:
reduce average call time.
Agents end calls quickly.
Call-duration metric improves.
But unresolved issues create repeat calls.
Workload may actually increase.
Or Procurement buys larger lots to reduce purchase price.
Purchasing metric improves.
Inventory rises.
Or Production maximises output.
Inventory rises.
The general principle is:
Do not optimise an activity in a way that worsens the end-to-end outcome.
How do bottlenecks affect productivity?
Suppose a process has four stages.
| Stage | Capacity/day |
|---|---|
| A | 150 |
| B | 130 |
| C | 70 |
| D | 120 |
Stage C constrains throughput.
Improving Stage A from 150 to 180 may create no additional completed output.
It may merely create more WIP before C.
This means employee-level productivity measures can encourage the wrong behaviour.
If A is rewarded for “units produced,” A keeps producing even though C cannot absorb the work.
Local productivity rises.
System productivity does not.
Does reducing idle time always improve productivity?
No.
A resource can appear idle because the system does not currently need its capacity.
Creating unnecessary work just to keep that resource busy may make performance worse.
This is especially relevant for:
specialist resources;
maintenance capacity;
customer support;
quality inspection;
variable-demand services.
The objective is not:
everybody occupied every second.
The objective is:
the system reliably produces the required outcome.
When should a company hire more people?
Sometimes hiring is absolutely correct.
Demand may have genuinely exceeded sustainable capacity.
But before automatically hiring, diagnose the workload.
Ask:
Is demand real?
Is the additional work customer-generated and sustained?
Is the process stable?
Or is workload inflated by exceptions?
Is rework high?
Are employees repeatedly doing work twice?
Where is the bottleneck?
Will the new employee increase end-to-end throughput?
Is role design clear?
What capacity exactly are we purchasing?
What are the five biggest drains on useful capacity?
A practical Fiease diagnostic can begin with five.
1. Waiting
Where does work stop?
2. Rework
What gets done again?
3. Search
What information is difficult to find?
4. Handoffs
Where does responsibility move unnecessarily or unclearly?
5. Approvals
Which decisions wait for authority?
A sixth is often equally important:
6. Overprocessing
What work exists without enough corresponding customer or business value?
Fiease Useful Capacity Diagnostic
Instead of beginning with headcount, map capacity consumption.
For each team, estimate:
A. Value-producing work
Work directly creating the intended output.
B. Necessary enabling/control work
Work required for governance, quality, compliance or support.
C. Failure/rework
Work created because previous output failed.
D. Coordination/search
Work spent locating information and chasing status.
E. Waiting-related disruption
Interruptions and switching created by blocked work.
F. Unused capability
Time available but not productively deployed.
The objective is not to eliminate B–F blindly.
It is to understand them.
Only then can management decide whether the true constraint is:
insufficient headcount;
poor process;
poor information;
technology;
skills;
demand variability.
HYPOTHETICAL EXAMPLE: A 30-person service operation
Assume a B2B services company has 30 delivery employees.
Each has approximately 160 paid hours per month.
Gross monthly labour capacity:
30 × 160 = 4,800 hours
Management believes the team is overloaded.
A capacity study estimates:
| Capacity use | Monthly hours |
|---|---|
| Customer-value delivery | 3,100 |
| Necessary administration/control | 500 |
| Correcting avoidable rework | 350 |
| Searching/reconciling information | 250 |
| Status/follow-up meetings | 300 |
| Duplicate data/reporting | 300 |
| Total | 4,800 |
Everybody really is busy.
The question is:
Busy doing what?
Direct customer delivery represents:
3,100 ÷ 4,800 = 64.6%
That does not mean every other hour should be eliminated.
The 500 hours of control/admin may be necessary.
But suppose the business can remove:
150 hours of rework;
100 hours of search;
100 hours of unnecessary reporting.
Released capacity:
350 hours per month
At 160 hours per employee, that is roughly:
2.2 employee-months of capacity
Management now has options.
It can:
absorb growth;
improve service;
reduce overtime;
postpone hiring;
reallocate capability.
The productivity improvement came from removing work, not asking people to work faster.
Can operational improvement increase employee wellbeing as well as productivity?
Often, yes.
Many waste categories are unpleasant for employees too.
People generally dislike:
correcting recurring mistakes;
searching for missing data;
waiting for approvals;
dealing with customer anger caused by preventable failure;
duplicating work;
constantly changing priorities.
Removing those frictions can simultaneously:
increase productive capacity;
reduce frustration;
improve customer experience.
Operations improvement is therefore not necessarily about pushing people harder.
Often it means designing work so people do less unnecessary work.
What should leaders stop saying?
Instead of:
“Everyone needs to work faster.”
Ask:
“What is preventing work from flowing?”
Instead of:
“We need more people.”
Ask:
“What is consuming the capacity we already have?”
Instead of:
“Why is this employee slow?”
Ask:
“What conditions does this employee work inside?”
Instead of:
“How many activities did we complete?”
Ask:
“What useful outcome did those activities create?”
What questions should a business ask tomorrow morning?
Start here.
What are the main outputs this team exists to produce?
How many are actually completed each week/month?
How much work is currently open?
How long does work take end to end?
How much actual touch time is involved?
Where does the rest of the time go?
What percentage needs correction?
What creates the largest backlog?
What approvals cause the most delay?
What information do people repeatedly search for?
What work is entered more than once?
What customer enquiries exist because something failed?
What is the system's bottleneck?
Would adding one employee increase finished output?
Which activity would we stop doing if we redesigned the process today?
Those questions reveal productivity much better than watching how intensely people appear to work.
Frequently asked questions
Is being busy always bad?
No. Strong demand can legitimately require intensive work. The mistake is using busyness itself as evidence of productivity.
Is overtime proof that we need more employees?
Not necessarily. Overtime may indicate insufficient capacity, but it can also result from rework, poor scheduling, late inputs or bottlenecks.
Should every employee have a productivity target?
Not necessarily. Individual targets can be useful where output is measurable and controllable, but they can create unintended behaviour if employees optimise their target at the expense of the overall process.
Is utilisation the same as productivity?
No. Utilisation shows how much capacity is occupied. Productivity compares output with inputs.
Is efficiency the same as productivity?
Closely related, but not identical. Productivity focuses on output relative to input; efficiency focuses on resource conversion and waste; effectiveness asks whether the correct outcome was achieved.
Does reducing meetings automatically improve productivity?
No. Remove meetings that do not create sufficient value. Keep meetings that enable essential coordination and decisions.
Does automation always improve productivity?
No. Automating unnecessary work can preserve waste in digital form.
How do we know if we have a genuine headcount problem?
Measure demand, useful output, backlog, lead time, rework and the constraint. If legitimate demand sustainably exceeds effective process capacity after major avoidable waste is addressed, more capacity may be justified.
The central idea
Activity measures effort.
Productivity measures useful output relative to resources.
Efficiency asks how economically those resources were converted.
Effectiveness asks whether the required outcome was achieved.
A company can have:
high activity + poor productivity.
It can have:
high utilisation + slow customer flow.
It can have:
high departmental output + poor business performance.
That is why the most useful management question is not:
“How do we make everybody busier?”
It is:
“How do we convert more of the effort we already consume into useful, correct, completed outcomes?”
Sometimes the answer is better technology.
Sometimes it is more people.
Sometimes better skills.
Sometimes more capacity at a bottleneck.
But very often the first opportunity is simpler:
remove the waiting, rework, searching, duplication, unnecessary approvals and incomplete work that are already consuming the organisation.
A business should not celebrate how hard its people have to fight the system.
It should build a system that allows their effort to produce results.
That is the difference between being busy and being productive.
FIEASE · BUSINESS OPERATIONS FOUNDATION SERIES