Triage Mode Fatigue

A simple explanation

Triage is the act of sorting — what is urgent, what can wait, what gets routed, what gets a fast reply. A little triage is the connective tissue of any working day. A day made of nothing but triage is a different category of experience: you have made hundreds of small decisions, you have moved nothing through to completion, and the felt-exhaustion is heavier than the day's output can explain.

The cost of triage is not the time spent on each item. It is the decision tax paid on every item that crosses the field. By evening, the tax has compounded into something the body reads as deep tiredness — without the satisfaction that depth-work normally leaves behind.

An everyday example

You open the laptop at 8:45. You scan email — 38 messages. You flag four as urgent, three as later, the rest you read and decide not now. The scan takes nineteen minutes. By 9:30 a Slack channel has thirty new messages; you skim, react to two, ignore the rest. A calendar invite arrives — you read it, accept, move on.

By 5pm you have answered fast, sorted fast, deferred fast. The inbox has the same number of items in it as when you started. You feel emptied out. The day was full and the day produced almost nothing you can name — and the gap is the entire problem.

Why a day in triage doesn't feel like work

It does feel like work, in the moment. Each decision lands as a small completion. The reply gets sent, the message gets archived, the invite gets accepted — and the brain reads each of these as a win.

What it does not feel like, by evening, is progress. Progress is the integration of effort into something that lasts beyond the session — a finished draft, a solved problem, a closed loop. Triage produces dispositions, not integrations. The disposition moves the item from unsorted to sorted; it does not move the item from open to done.

The hollow at the end of the day is the gap between the felt-busy and the felt-progress. Triage delivers a full quota of the first and almost none of the second. The body reads the gap as failure, and the loop-runner often metabolises it as a need to triage faster tomorrow.

The behavioral loop

The shape that runs through a triage-heavy day:

1. Channels open — email, Slack, calendar, tickets, messages.
2. Scan — eyes move across the surface of forty inputs.
3. Decide — urgent, later, defer, ignore; each decision costs.
4. Dispose — reply, flag, route, archive; each disposition lands as a small win.
5. Return to scan — the queue has refilled while you were disposing.
6. Defer the deep work — the integration task that needed an unbroken block gets pushed to after triage; triage does not end.
7. End of day — felt-busy is high; felt-progress is low; the deep work is untouched.
8. Self-distrust — another day where I didn't do the real thing; the loop tightens.

The defining feature is that the day's deep work never gets a window. The triage has consumed the windows.

Emotional drivers

Three feelings, usually layered:

• A small relief at every disposed item — the brain registering closure even though the closure is partial.
• A diffuse anxiety about the unattended channels — the messages not yet read, the queues not yet sorted — which keeps the scanning tempo high.
• An end-of-day hollow that the loop-runner often reads as personal failure rather than as a structural problem of how the day was permitted to be shaped.

What your nervous system does

Each decision produces a small surge — the orienting response and a small dopaminergic blip at the disposition. Forty an hour, sustained, is not a tempo the body was designed for. The prefrontal cortex carries the decision load directly; by mid-afternoon, glucose costs have mounted and decision quality starts to slip. Cortisol drifts up. The body somatically tightens — jaw, shoulders, shallow breath — and the loop-runner reads the tightness as evidence that the work is important rather than as a signal that the structure is wrong.

Over months, the triage tempo becomes the baseline and the body stops registering it as effortful. It registers it as the job.

The DojoWell interpretation

Triage mode fatigue is a clean instance of residue_accumulation — the density signature in which each item leaves a small unfinished trace, and the traces compound across the day until working memory is layered with dispositions that never quite closed.

The Meaning System is asking for a block long enough to deposit something that lasts. The Threat System, scanning for unattended channels and unrouted urgency, keeps the triage going. The Threat System wins because its requests are fast and concrete; the Meaning System gets paid in tomorrow.

The substitute is perpetual sorting. Sorting is real cognitive work — the felt-effort is genuine. The deposit per disposition is near-zero, because the item moves from one queue to another rather than from open to done.

The equation is sharp. Effort runs all day. Residue compounds. Deposit per cycle is small. The numerator collapses. Density: low. The fix is not faster triage — it is reclaiming the window the deep work needs before the triage opens.

How do I get out of constant triage?

Three moves, in order of leverage.

First, invert the order. The deep work goes first, before any channel is opened. Most knowledge workers who flip this find that ninety minutes of pre-triage depth produces more progress than eight hours of post-triage work.

Second, batch the triage windows. Triage runs twice a day, in defined windows, not continuously. The cost of triage is the residue across the rest of the day, not the time inside the window.

Third, separate disposition from completion. Triage moves items between queues. Completion moves items out of queues. Track them separately, and notice on which days you did the second at all.

Practical steps

1. Open the deep work before the inbox. First action of the day is the contiguous task, not the scan. The order matters more than the duration.
2. Set triage windows. Two windows of forty-five minutes — late morning, late afternoon. Outside the windows, channels stay closed.
3. Track dispositions vs. completions. At the end of the day, write two numbers: items disposed, items completed. The ratio reveals the shape of the day.
4. Refuse the triage-as-warmup story. The story says: I'll triage first to clear the deck, then do the deep work. The deep work never arrives; the deck refills faster than triage clears it.
5. Name the felt-busy. When the day feels productive in real time, ask: what would I name as finished? If the answer is nothing, the day is in triage mode regardless of how it feels.

Reflection questions

• At the end of your last busy-but-hollow day, what did you actually complete versus what did you dispose?
• Which channel issues the most triage decisions at you, and what would change if it stayed closed until noon?
• When did you last begin a day with the deep work, before opening any inbox?
• What does your body do during the first hour of triage — and what does it do during the first hour of contiguous work?

Frequently Asked Questions