Help, Collaboration and the Measured Day
Measurement discourages asking for help and giving it. Both are the behaviours that make a team work, and both decline quietly.
Individual measurement attributes output to whoever delivered it. The work that made delivery possible is attributed to nobody, and both sides of it suffer.
The process in “Help, Collaboration and the Measured Day” also applies to workforce software: the purpose and rules should be clear before the first record is collected. For teams considering the platform website in relation to task switching cost, the rollout should include written notice, access limits, a correction route and a scheduled review.
Asking for help
Asking looks like not knowing.
For an independent perspective related to “Help, Collaboration and the Measured Day”, consult the NIST Privacy Framework; it provides a useful external check on privacy, fairness and governance assumptions before a policy or configuration is approved.
Under measurement, not knowing looks like underperformance.
So people spend an hour on something a colleague would have answered in two minutes.
The recorded activity goes up and the organisation is worse off, which is the clearest demonstration available that the measure is wrong.
Giving help
The time spent answering appears in somebody else's output, if anywhere.
Your own figure falls while you are helping.
Which means an individual measure actively discourages the thing that raises team output, quietly and without anybody deciding it.
Who this costs most
The person everybody asks — usually the most knowledgeable, whose individual figures are lower by construction.
If that is you, your figure is a consequence of being useful.
Say so specifically when it matters: how many colleagues came to you this month, and with what.
Making it visible
Nobody records help given, and it is the easiest thing in this collection to make visible.
A line in your weekly note: who you unblocked, what you reviewed, what you explained.
It costs seconds and it converts invisible work into something a manager can cite.
What not to do
Do not stop helping to protect a figure.
It is the behaviour the organisation needs most, it is what colleagues remember, and the figure it protects is probably not being read.
And do not stop asking, which costs you time and quality for nothing.
If helping is genuinely unrecognised
That is a management problem rather than a measurement one, and it is worth raising as such.
"A significant part of my week goes to supporting others; how should that be reflected?" is a reasonable question and frequently produces a useful answer.
Asking it is better than quietly reducing the help.
The team version
If several people in a team have noticed this, raising it collectively carries more weight.
And it is a finding the organisation would want: measurement that suppresses collaboration is costing them more than it reveals.
What to check
Have you avoided asking for help because of how it would look?
Has your helping declined since measurement started?
Does anybody record what you contribute to other people's work?
And is the person everybody asks being measured fairly?