Performative Productivity

A simple explanation

Performative productivity is the visible performance of being productive when the visibility itself has become the point. It is not exactly lying — the Slack status really is green, the calendar really is full, the meetings really did happen — but the visibility has separated from the work it was supposed to signal. The display became its own job, with its own effort cost and its own private rationale.

This separates performative productivity from ordinary productivity, where visibility is a side-effect of doing the work. Here the visibility is calibrated, often hourly, for a watching eye — a manager, a peer, an algorithm — and the actual work makes room for the performance rather than the other way around. The appearance of progress substitutes for the deposit of it, and the body, somewhere underneath, knows.

An everyday example

It is Tuesday afternoon. You opened a deep-work document at 2pm and immediately bounced out of it, because forty-six minutes of silence on Slack feels longer than it used to. You toggle to chat, post a small update in a project channel, react to two messages, and watch the green dot reassure itself. By 3pm you have answered fourteen messages, attended a check-in that could have been a paragraph, and updated your status to focusing — back at 4.

You log off at 6:30 feeling oddly tired and oddly hollow. The deep-work document is still at the same paragraph. You did not, in any meaningful sense, do the work today. You did the second job — the performance of having done the work — and it has its own exhaustion, recognisable now from years of repetition.

Why do I feel I have to look busy at work?

Because the watching eye is real, and the Belonging System reads it accurately. Hybrid and remote work removed the casual proof-of-presence that an office building used to provide. The System, asked to keep you connected to your team and your standing, supplies a substitute proof: visible motion. The green dot, the calendar density, the responsiveness window, the just shipped update.

The Threat System adds its own weight. Layoff news in the feed, performance reviews quarterly, unallocated capacity phrases in skip-levels — the System reads these as concrete threats and prescribes visibility as armour. Looking productive becomes the System's idea of safety. The trade looks rational until you measure what the visibility cost you in actual output.

The behavioral loop

A loop where the performance becomes the product:

1. Watching-eye signal — a manager pings, a calendar opens, a teammate reacts. The System registers that visibility is being measured.
2. Threat ping — a faint am I visible enough? arrives, often below conscious notice.
3. Performance behaviour — a status toggle, a Slack post, a calendar entry, a meeting accepted, a reply sent inside two minutes.
4. Brief belonging hit — a green check, a reaction emoji, a thanks for the quick turnaround. The System logs success.
5. Real-work interruption — the deep-work document, the long thinking, the difficult email, the actual deliverable — pushed by twenty minutes, then an hour, then a day.
6. Compensatory belief — I am still being productive — look at all the messages, look at the meetings. The substitute begins to feel like the real thing.
7. Residue — the real work is now late, the long thinking did not happen, the body holds a low-grade tension at the desk that it did not have at 9am.
8. Re-entry — the next ping arrives and the performance is now faster, more grooved, harder to interrupt.

Emotional drivers

Four feelings, layered:

• A diffuse fear of being judged unproductive, which never quite gets specific enough to be tested against actual evidence.
• A belonging hunger — to be seen, recognised, included in the channel — that the performance partially feeds.
• A faint self-distrust that the loop-runner often misreads as needing to be more disciplined.
• A subtle resentment toward the watching eye, which is rarely named because the loop-runner has internalised it as their own standard.

What your nervous system does

The watching-eye signal triggers a low-level sympathetic alert — a small upshift in arousal, narrowed attention, a forward lean toward the screen. The body becomes response-shaped: leaning toward interrupt rather than depth. Heart rate stays modestly elevated. Breath rides high in the chest. The eyes flick to the dock, the inbox tab, the notification corner, with a fluency the loop-runner stopped noticing months ago.

Over weeks and months, the response-shape becomes the resting shape. The body cannot easily downshift into the parasympathetic state that deep work requires, because it is held at a low alert all day. The work that needs forty minutes of quiet does not get them, not because the calendar refuses, but because the nervous system has forgotten how to drop in.

The DojoWell interpretation

Performative productivity is one of the clearest false_progress signatures in the modern-life realm. The substitute — visibility-without-output — is genuinely felt as productivity by the loop-runner, because the Systems are scoring visibility as the win condition. The system logs many small wins each day: messages answered, meetings attended, status updated. The deposit register, which tracks actual output, runs quietly empty.

Two Systems co-author the loop. The Belonging System fears social invisibility and reads the watching eye as kin. The Threat System fears institutional invisibility — being deprioritised, deranked, let go — and reads the same watching eye as judge. Their substitutes converge on the same behaviour, which is why the loop is hard to interrupt by appealing to either System alone.

The closure pattern is substituted rather than stalled because the system genuinely thinks it has closed the loop each time the green dot reasserts itself. False progress, by definition, feels like progress. The cost shows up downstream — missed deliverables, thin output reviews, the slow drift of being known as responsive but not creative — and the Systems are not equipped to read the downstream as related to their own behaviour upstream.

The work is not to be less visible. It is to stop confusing visibility with deposit, and to let the body learn the difference between a meeting attended and an hour of work done.

How do I stop performing busy at work?

You do not stop the watching eye. You stop letting the Systems outsource your sense of having worked to it.

Three moves, in order of difficulty:

1. Pick the deposit and write it down at 9am. One sentence: by end of day, the work that will have actually moved is X. The Systems cannot easily substitute around a sentence you wrote to yourself.
2. Schedule one ninety-minute opaque block. Status amber, notifications muted, calendar marked focus. The discomfort of the first twenty minutes is the data — the body re-learning to downshift.
3. At 5pm, score the day on deposit, not motion. What moved that would not have moved otherwise? Some days the honest answer is nothing. Naming it is the practice.

Practical steps

1. Cap the number of green-dot hours. Not the workday, the visible-presence hours. Four good hours of visibility plus four hours of opaque focus deposits more than ten hours of low-grade availability.
2. Decouple your status from your work. Focusing is a status. Available 4pm is a status. The Systems fear that opacity equals invisibility; the data says it usually equals respect.
3. Track output, not effort, for two weeks. A list of what shipped, not a list of what you did. The gap between the two lists is the loop's footprint.
4. Notice the watching eye specifically. Whose green-dot are you performing for? Sometimes it is a manager. Sometimes it is a peer. Sometimes it is a memory of a previous boss who is no longer in your life. Naming the eye shrinks it.
5. Hold one slow conversation with your manager about deposit. Not about availability. About what you are actually meant to deliver this quarter and how it will be measured. The fog the Systems work inside often dissolves in five minutes of direct talk.

Reflection questions

• At the end of today, what would deposit mean — and what would visible motion mean — and how big is the gap?
• Whose watching eye are you most calibrated to, and what would change if it stopped watching?
• How do I know if I'm performing productivity rather than doing it — what would the body feel like in each case?
• What real work has been postponed this week because the second job of looking productive consumed the hours?

Frequently Asked Questions