An individual puts visible effort on show, late-night emails, packed calendars, constant urgency, to look indispensable to the people who evaluate them, whatever they deliver.
An example
Two analysts prepared the liquidity reporting for the head of corporate treasury at a regional bank. One sent emails at one in the morning, kept a calendar with no open slots, and opened every status meeting with a list of fires he was fighting. The other left by six and said little. When year-end ratings came due, the head nearly gave the late-night analyst the higher score. Then she pulled the reporting log for the year. The quiet analyst had produced eleven of the fourteen regulatory submissions, all on time; the busy one had produced three, two of them after extensions. Every deadline on his projects had slipped by about a week, though his emails grew more urgent each time. She rated the quiet analyst higher and wrote down why.
Why it works
The theater creates evidence of value without adding any, so promoting the performer looks like the right call. Checking deliverables seems redundant amid the flood of activity, and it carries a social price: questioning someone who is visibly exhausting themselves for the company reads as ungrateful. It works where output is hard to measure or slow to show, evaluators are busy enough to rely on proxies, the culture treats visible effort as a virtue, and peers are performing too. It collapses when a hard measure becomes available.
The thinking behind it
Erving Goffman The Presentation of Self in Everyday Life (1956) treats behavior as performance managed for an audience, with preparation and contradicting facts kept out of view. Late-night emails and urgent status updates are a performance of indispensability staged for evaluators. Asking what you would conclude from a person's outputs alone is a way of looking past the front region to what the performance leaves out.
A. Michael Spence Job Market Signaling (1973) shows that a costly action can separate more productive people from less productive ones only if it costs the less productive more. Visible effort costs a middling performer no more than a strong one, so it does not separate them, yet busy evaluators read it as if it did. A hard measure of output, where one exists, replaces the weak signal with direct evidence.
Warning signs
Email timestamps cluster after ten at night while deliverable dates never move forward. Calendars have no open time, but finished work is hard to point to. Status updates describe fires and effort more than completions. Questioning the person's output is treated as ungrateful or bad for morale, and a less visible peer has a longer list of delivered work.
How to defend yourself
Ask what you would conclude about this person if you could see their outputs and none of their hours. Then:
- Pull the record: deliverables, dates, and who produced them.
- Bring in a hard measure wherever one exists, such as tickets closed, submissions filed, or revenue per head.
- Set the performer next to a quieter peer with more delivered work and compare them on output alone.
- Write the rating rationale in terms of results, so any appeal has to argue with the record.
If you are the quiet peer being outshone, keep your own list of what you finished and when, and put it in front of your evaluator before ratings.
How a leader shuts it down
Reduce how opaque output is: define deliverables for staff and knowledge roles, track them, and use them in ratings. Stop praising hours in public, and ask evaluators to cite completed work for every high rating. Where a whole team is performing effort, the theater becomes the norm, so reset the standard for everyone at once.