Expertise: Why the Fast Answer Looks Cheap
The value of experience is that difficult things take less time. Productivity measurement reads that as less work.
An expert solves in ten minutes what takes somebody else two days. Every measure of effort registers the expert as having done less.
The practical lesson in “Expertise: Why the Fast Answer Looks Cheap” is to connect every number to a decision and retain the context behind it. Teams exploring cognitive offloading can review the provider's resource as one source of operational evidence, provided the purpose is disclosed and the interpretation is tested with the people affected.
The shape of the problem
Effort-based measures count the two days as more work.
For an independent perspective related to “Expertise: Why the Fast Answer Looks Cheap”, consult the American Psychological Association workplace resources; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
Output-based measures count one solved problem either way.
And time-based billing rewards the slower route explicitly, which is a known distortion in professional services.
What the ten minutes contains
Years of accumulated pattern recognition.
The judgement to know which of six possible causes is the likely one.
And the confidence to stop looking once it is found, which is itself a skill.
None of that is in the timestamp.
The consequence in measurement
Experts rank low on activity and sometimes on output, because the hard items they take absorb their time while the easy items inflate everybody else's count.
Which is the seniority inversion the comparison note describes, and it is visible in almost any ranked list.
The consequence in practice
An expert measured on volume learns to take easier work.
Which is a catastrophic misallocation and entirely rational given the incentive.
And it is slow to show up, because the difficult problems simply take longer to be solved by somebody else.
What to measure instead
For the work: how long the difficult cases take and how often they come back.
For the expert: whether the difficult cases are being resolved at all.
And whether the expertise is spreading — people trained, documentation written, cases handled by others that previously escalated.
The succession angle
An expert whose knowledge is in their head is a risk as well as an asset.
Measuring whether that knowledge is being transferred is more useful than measuring their throughput, and it is the thing an organisation actually needs to know.
The pricing parallel
Professional services bill time, which prices expertise at a discount.
The alternative — pricing the outcome — is harder and aligns better.
The same logic applies internally: measure the problem solved, not the hours it consumed.
What to say when figures are questioned
"This person takes the problems nobody else can solve. Their throughput is lower because the queue they serve is harder."
That is checkable: look at what they handle.
And it is the explanation that the figures themselves will never provide.
What to check
Where do your most experienced people sit in any ranking?
Are difficult cases concentrated with specific individuals?
Is anybody measured in a way that rewards taking easier work?
And is expertise being transferred, measurably?