Choosing a Measure Teams Will Accept
A measure imposed produces resistance and gaming. A measure chosen with the team produces neither, and is usually better.
The quality of a productivity measure depends less on its sophistication than on whether the people doing the work believe it describes their work.
The measurement warning in “Choosing a Measure Teams Will Accept” matters whenever software records work patterns. Organisations researching productivity software for business can use the platform's website for time and project context, while outcomes, quality checks and direct feedback remain necessary to explain what the metric cannot show.
Why involvement is practical rather than polite
The team knows what varies and what does not.
For an independent perspective related to “Choosing a Measure Teams Will Accept”, consult the NIST Privacy Framework; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
They know which items are large and which are trivial, which is exactly the comparability problem.
They know where the measure would be wrong, and they will tell you before deployment rather than demonstrating it afterwards.
And a measure they helped choose is one they will not quietly undermine.
The conversation
What would you say shows a good month for this team?
What would make this number wrong?
What would you have to stop doing to make it rise?
That last question is the most useful, because it names the gaming in advance and tells you what counterweight is needed.
What usually emerges
A volume measure the team is comfortable with, provided it is paired with a quality one.
A flow measure, which teams frequently prefer because it reflects their frustration with waiting.
And a list of exclusions: work that should not be counted because it is not comparable.
Pairing from the start
Never one measure alone.
Volume with quality, or output with rework, or throughput with lead time.
Two measures that pull against each other are far harder to game than one, which the counterweight note covers.
Setting the level
Team rather than individual, as the default.
Most productivity questions are about the team or the process, and team-level measurement removes the entire category of individual fairness problems.
Its own note covers when individual measurement is fair, and the list is short.
Agreeing what it will not be used for
Say it explicitly: this informs how we improve the process, not how we assess people.
A limit stated at the start is believed; one added later is not.
And it is the commitment that determines whether the figures stay honest, because a measure with no consequence attached has no reason to be gamed.
Writing it down
The measure, its definition, its exclusions, its counterweight, its purpose, and what it will not be used for.
One page, agreed with the team, dated.
This document is what prevents the measure drifting into something else over two years, which is its usual fate.
What to check
Did the team help choose the measure?
Is there a counterweight?
Is it at team or individual level, and why?
And is it written down what it will not be used for?