1. The results you can see aren't the same as ability
What you see at work isn't decided by a person's ability alone.
Observed results
= ability
× difficulty of the assignment
× workload
× support received
× frequency of interruptions
× hidden cleanup work
× how well it's presented
Someone who carries a lot of hard cases and fixes other people's mistakes will have more visible errors and delays. Someone who handles a narrow, protected area looks steady and reliable.
2. The more capable you are, the messier your work looks
When urgent cases, undefined tasks, inquiries, and requests for help from other departments all land on the person who finishes fast, their scope of work keeps spreading.
Capable
→ extra tasks
→ more interruptions
→ more projects in parallel
→ looks chaotic on the surface
Slow at processing
→ fewer tasks added
→ fixed scope of work
→ looks stable on the surface
If the organization doesn't adjust for task difficulty and total workload, the "stable" person ends up looking like the high performer.
3. Looking exhausted becomes a stand-in for effort
When evaluators can't see how the work actually gets done, they treat visible behaviors as proof of effort:
- Staying late for long hours
- Always seeming to be in a rush
- Talking a lot in meetings
- Replying quickly
- Saying "I'm so busy" all the time
But long hours may just be the result of low efficiency, too many meetings, rework, or poor delegation. The person who quietly finishes early looks like they're doing nothing.
4. Hiding your ability is rational, and that causes "adverse selection"
When showing your ability puts you at a disadvantage, capable people leave in one of two ways.
Hide their ability
or
Leave the organization
Meanwhile, people who have adapted to performing busyness and dodging responsibility are more likely to stay. As a result, the organization slips into this loop:
Can't see who is capable
→ piles extra load on the capable
→ they hide their ability or quit
→ even harder to see who is capable
That loop is adverse selection: the organization ends up keeping the wrong people.
5. Break down what "few mistakes" really means
Even when you compare only error rates, you need a denominator.
0 mistakes out of 10 routine tasks
2 mistakes out of 500 complex tasks
The first person isn't necessarily the better one. What you should look at is:
- Number of tasks handled
- Difficulty
- Financial impact
- First-time accuracy rate
- Rework rate
- How much cleanup other people had to do
- Future work hours eliminated through improvements
6. How to get ability assessment back on track
- Record workload and difficulty
- Measure quality and rework, not just completion time
- Track newly added urgent work as a separate category
- Count fixing, training, and standardizing for others as results
- Remove "time spent at the office" from the performance metrics
- Compare total work hours before and after an improvement
- Look at process data, not just what people report about themselves
Evaluation needs to go back to asking not "who looks tired?" but who created how much value, under what conditions, and in a way that can be repeated.
7. Conclusion of Article 3
In an organization where performing busyness has become the norm, the very data needed to tell capable from incapable disappears.
Punish productivity
→ people hide their ability
→ judged by appearances
→ work is misallocated
→ the capable burn out or leave
If the reward for being capable is more work, and the protection for low ability is an unchanged workload, the organization is creating a situation in which it can't measure anything at all.
