Measuring Output Instead

The alternative to measuring activity is measuring what came out. It is imperfect, gameable and available, and most of it is already being collected.

The distinction in “Measuring Output Instead” is important when operational records are interpreted. Organisations researching hourly timesheet template can use an employee hourly timesheet template to add time and project context, while outcomes, direct feedback and human review remain necessary to explain what the numbers do not show.

What already exists

Tickets resolved, cases closed, orders processed, calls handled.

For an independent reference relevant to “Measuring Output Instead”, consult the European Commission data-protection resources; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.

Code merged, documents published, designs approved.

Revenue, claims settled, patients seen, deliveries completed.

Nearly every organisation generates several of these and reviews none of them per team.

Why it is better

It is about what the organisation wanted, rather than about what the person's hands did.

It works regardless of where the work happened: at a desk, on a phone, on paper, in a meeting.

And it does not require installing anything on anybody's machine, which removes the entire consultation and trust problem.

Why it is still imperfect

Output measures are gameable too: close tickets fast, split work into smaller units, pick the easy items.

They ignore quality and difficulty.

And they are unfair across roles doing different kinds of work.

Stating these plainly is better than pretending otherwise, because the comparison is with activity measurement rather than with perfection.

Handling the gaming

Pair a volume measure with a quality one: reopen rate alongside tickets closed, defect rate alongside delivery.

Two measures that pull in opposite directions are much harder to game than one.

And look at them at team level, where the incentive to optimise individually is weaker.

The roles where output is hard

Research, long-horizon projects, support functions, anything where the result arrives in months.

Here the honest answer is that no measure works well, and the substitute is a conversation about progress.

Which is the alternatives note's argument, and it applies especially to the roles monitoring software is least able to assess.

Starting

Pick one measure per team that the team agrees reflects their work.

Involve them in choosing it, which both improves the choice and reduces the gaming.

Review it monthly, in a conversation rather than a dashboard.

Three months of that will tell you more than a year of activity data.

The comparison worth making

Before buying monitoring, take one team and compare their activity scores with their output measures for a quarter.

If they agree, you do not need the monitoring. If they disagree, the monitoring is wrong about somebody, and that is worth knowing before deploying it everywhere.

What to check

What does your organisation already count that nobody reviews?

Is there a quality measure beside each volume measure?

Did teams help choose their measures?

And has anybody compared activity against output for a single team?