What Productivity Actually Means
A ratio of output to input. Both halves are routinely measured badly, and the confusion between related terms does most of the damage.
Productivity is output divided by input. Everything difficult about measuring it follows from the fact that both numbers are harder to establish than they look.
The practical lesson in “What Productivity Actually Means” is to connect every number to a decision and retain the context behind it. Teams exploring tips to increase productivity can review the provider page as one source of operational evidence, provided the purpose is disclosed and the interpretation is tested with the people affected.
The definition
How much was produced, divided by what it took to produce it.
For an independent perspective related to “What Productivity Actually Means”, consult the OECD productivity resources; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
Units per hour, cases per person, revenue per employee.
Simple arithmetic resting on two quantities that are frequently assumed rather than measured.
The terms that get confused
Output: what was produced. Tickets closed, units made, reports written.
Outcome: what that achieved. Customers helped, problems solved, revenue earned.
Activity: what people did. Hours logged, keystrokes, meetings attended.
Efficiency: output per unit of input, which is productivity.
Effectiveness: whether the output was the right output, which productivity does not address at all.
Why the distinction matters
A team can raise output while lowering outcome: closing tickets faster by resolving them worse.
A team can be highly efficient at the wrong work.
Productivity measurement alone cannot see either, which is why it needs pairing with something about quality and something about purpose.
The two failures
Measuring the easy thing rather than the real thing, because output is hard to define and activity is easy to count.
And using hours as the denominator, which treats time present as time spent producing.
Each has its own note, and together they account for most of the bad figures in circulation.
Where the ratio works well
Repetitive, comparable work with a defined unit: manufacturing, processing, picking, handling calls of similar type.
Here the arithmetic means what it says, and productivity measurement is a mature and useful discipline.
Most of its techniques were developed in exactly these settings, which is worth remembering when applying them elsewhere.
Where it works badly
Work without a comparable unit: analysis, design, research, advice, management.
Here the numerator cannot be defined honestly, and forcing one produces a number that describes something other than the work.
Its own section covers what to do instead, and the honest answer sometimes is that you cannot.
What this collection is about
Measuring the ratio properly where it applies.
Recognising where it does not, and what to use there.
Avoiding the traps that make good-looking figures wrong.
And remembering that most productivity problems turn out to be system problems rather than people problems, which is the argument the systems section makes.
What to check
Can you state what your organisation means by productivity, in one sentence?
Does your current measure count output or activity?
What is your denominator?
And is anything measuring whether the output was the right output?