Measuring the Team Rather Than the Person
Moving the measure up one level removes most of its unfairness and most of its gameability at once. What is lost and what is not.
The same arithmetic applied to a team rather than an individual is a substantially better measure. Allocation effects wash out, individual recording decisions matter less, and the unit measured is the unit the work was given to.
The people risk in “Measuring the Team Rather Than the Person” is not solved by collecting a more detailed activity score. Used for employee monitoring at tech companies, employee monitoring at tech companies can provide transparent time and project context, but individual conclusions still require a published method, a correction route, direct conversation and proportionate human review.
It is the cheapest single improvement available, and it costs the ability to rank people.
Teams documenting “Measuring the Team Rather Than the Person” may use OWASP logging guidance as an outside reference. Keep the source record, calculation rule and resulting decision visible as separate steps.
Why allocation washes out
Within a team, who got which engagement is an internal distribution question. The team's total chargeable hours do not change when the work moves between its members.
- At individual level: who got which engagement sets the ceiling.
- At team level: the work was given to the team, and its total does not move when the work moves inside it.
So the largest source of individual unfairness disappears at team level.
Why gaming weakens
One person's reclassification moves a ten-person figure by a tenth of what it moves their own. The incentive per individual falls proportionally.
It does not vanish — a team can collectively drift — but the mechanism is much weaker and a collective drift is easier to see.
Why role differences wash out
A team contains supervisors and juniors. Its blended figure reflects its mix, which is a real property of the team.
The seniority problem does not disappear between teams with different mixes, which is why team figures still need the mix beside them.
What the right team is
The unit work is allocated to and that has somebody accountable for distributing it. Usually a practice, a department or a delivery group.
Not a matrix slice, and not a grouping that exists only in the reporting system.
The size question
Large enough that individual variation averages out, small enough that somebody is accountable. Six to twenty people in practice.
Below six, individual effects dominate. Above twenty or so, nobody owns the distribution.
What the move gives up
The ability to compare individuals, which the person section argues was never supportable.
Also the ability to identify a single person in difficulty from the report, which is a real loss and has a remedy.
The remedy for that loss
Individual figures visible to the person and their manager, with the four inputs beside them, never aggregated into a ranking or carried into appraisal.
Visibility without consequence keeps the diagnostic and removes the pressure.
The accountability that comes with it
The team's figure belongs to whoever distributes its work, not to its members collectively.
That is the right placement, because distribution is the decision the figure is mostly about.
The usual objection
That individuals will hide in the team average. In practice a persistently disengaged person is apparent to their colleagues and their manager long before a ratio shows it.
The ratio was never how that was detected, and firms that think otherwise are usually describing a management problem.
What improves in the conversation
Team-level questions are about allocation, pipeline, skill mix and scheduling — things the people in the conversation can change.
Individual-level questions about the same number are mostly about circumstances nobody in the room decided.
The transition
Report both for one quarter, then drop the individual version from the pack. Keep it visible to the person.
The pack is what travels, and removing it from the pack is what removes the comparison.
The arithmetic of dilution
One person in a team of twelve reclassifies eighty hours over a year. Their own figure moves by about five points. The team's moves by about four tenths of one.
The incentive falls by the size of the team, which is why a team of six is the practical minimum: below that, individual recording still moves the number enough to be worth moving.
Dilution is the whole mechanism, and it is arithmetic rather than culture.
The collective drift that remains
A team under pressure can move together, and that is the residual risk.
It shows up differently: not as a spike in an individual distribution but as a whole team's non-billable categories falling in one quarter.
The non-billable split catches it, which is one more reason the split belongs beside the ratio. A team-level figure with no composition beside it is gameable in exactly the way an individual figure is, just by a group instead of a person, and the detection method is the same check applied one level up.
What to do with the individual figure
Show it to the person and their manager, with the contracted fraction, the role duties, the allocation record and the recording rules beside it.
Then stop. It does not aggregate upward, appear in a pack, or enter a review.
Visible without consequence is the only state in which a self-reported individual figure stays accurate, and accuracy is the only thing it was ever good for.
What to expect afterwards
Fewer arguments about the number, more about the work. Recording quality improves slightly because the pressure drops.
And the team figures turn out to vary less than the individual ones did, because most of that variation was allocation all along.