Why Hours Are a Poor Denominator

Productivity per hour is the standard formulation. It assumes an hour is an hour, and in most work it is not.

The measurement warning in “Why Hours Are a Poor Denominator” matters whenever software records work patterns. Organisations researching hourly timesheet template can use an hourly timesheet template for employees for time and project context, while outcomes, quality checks and direct feedback remain necessary to explain what the metric cannot show.

What an hour contains

Meetings, some necessary.

For an independent perspective related to “Why Hours Are a Poor Denominator”, consult the Harvard Business Review productivity collection; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.

Waiting: for approvals, for systems, for other people.

moving between tasks between tasks.

Administration imposed by the organisation.

Interruption.

And some amount of the actual work.

The last proportion varies enormously between roles, teams and weeks.

Why that breaks the comparison

A team whose hours are fragmented by meetings produces less per hour with identical effort.

Which measures the meeting load rather than the people.

And a team given clean blocks of time looks more productive, which is true and is a finding about scheduling rather than about staff.

The headcount variant

Output per employee has the same problem plus vacancy, part-time and turnover.

A team carrying two vacancies looks more productive per head while being less able to deliver.

And a team that trained three new starters looks worse, having done work that will pay back later.

What to use instead, where you can

Cost: output per unit of spend, which is harder to game and closer to the business question.

Capacity consumed rather than time present, where a system records it.

Or no denominator at all: track output over time with a stable team, and watch the series.

That last is underused and frequently sufficient.

When hours are the right denominator

Where time directly produces output: machine operation, processing, handling.

Where hours are billable, in which case the ratio is a commercial measure rather than a productivity one.

Here the arithmetic is sound and the objections above do not apply.

The improvement that is not one

Cutting meetings raises output per hour without raising output.

So does removing training, documentation and helping colleagues.

A rising ratio with flat output means the denominator fell, and that should prompt a question rather than a celebration.

Reporting it honestly

Show output and hours separately alongside the ratio.

State what moved.

"Output flat, hours down eight per cent after the vacancy freeze" is the real story, and it is invisible in a productivity percentage.

What to check

What proportion of your people's hours is meetings and waiting?

Does your figure improve when somebody leaves?

Do you report output and input separately?

And has a rising ratio ever been caused by a falling denominator?