Nothing has happened yet.
You slept fine. You’ve done no work on this. You sat down four minutes ago.
And there’s a fatigue present that would be appropriate two hours in — a heaviness, a sense of the day already having been spent, a genuine physical reluctance that has nothing obvious behind it.
Then the thought arrives: maybe I’m burnt out.
Maybe. But there’s a test that separates the two possibilities, it takes five minutes, and getting it wrong in either direction is expensive.
What’s Producing It
Fatigue experienced before beginning a task can arise from two distinct sources requiring opposite responses. The first is load: an unspecified task has been repeatedly held in attention over an extended period, each instance carrying the cost of the whole undefined object, and the accumulated cost presents as tiredness at the moment of approach. This form is anticipatory rather than actual, and it characteristically lifts within a few minutes of beginning concrete work. The second is depletion: genuine exhaustion of physical or cognitive resource, which is not task-specific, does not lift on starting, and is worsened by continuing. The two are indistinguishable by sensation and are separated by response to a brief trial of work. Misidentifying depletion as load results in pushing through genuine exhaustion; misidentifying load as depletion results in resting a problem that rest cannot address.
Three mechanisms produce the first kind. Then the test.
One: You’ve Already Paid, Repeatedly
The largest contributor, and it’s cumulative.
An unspecified goal has no components, so it can’t be held in pieces. Every time it crosses your mind — in the shower, at a traffic light, at 11pm — you load the whole undefined object, and the whole object is priced high because its size is unknown.
That’s covered in why a big goal is physically uncomfortable to look at. What matters here is the accumulation.
Do that thirty or forty times over four months and there’s a real total. And the total doesn’t present as a memory of having thought about it a lot. It presents as fatigue, arriving at the moment you approach the thing, because approaching it is what triggers the retrieval of everything attached to it.
So the tiredness you feel sitting down isn’t a forecast of the work ahead. It’s a bill for work you never did.
Two: Sitting Down Runs the Whole Project
Second mechanism, and it’s specific to the moment of starting.
When you sit down to a defined task, you load the task. When you sit down to an undefined one, you load the project — because there’s no boundary between the session and everything downstream of it.
So the act of opening the file triggers a rehearsal: the chapter, then the other chapters, then the editing, then the fact that you don’t know how it ends, then whether it’s any good, then what happens if it isn’t.
None of that is deliberate. It runs in a second or two and it’s expensive.
And it explains something otherwise strange: the fatigue is often worse at the moment of starting than at any other point in the day. Thinking about the project casually is cheaper than sitting down to it, because sitting down to it recruits the full simulation.
Three: Open Loops Cost Something in the Background
Third, and it’s the quietest.
Unfinished things occupy some ongoing resource. An intention you’ve formed and not completed maintains a low-level presence — it surfaces unprompted, it produces small intrusions, it makes a claim on attention that you didn’t authorise.
One of those is negligible. Eleven is not, and most people carrying an unstarted project are carrying several.
This is why the fatigue often isn’t proportionate to the specific task in front of you. You’re not tired because of this project. You’re tired because this project is the fourth open loop and approaching it briefly surfaces the other three.
The practical implication is unglamorous: closing or explicitly abandoning small open loops reduces the background cost, and it does so faster than working on the big one. Deciding not to do something, properly and deliberately, closes the loop as effectively as doing it.
The Five-Minute Test
Here’s the instrument, and it’s the whole point of this article.
Do five minutes of the smallest concrete piece of the work. Then check.
The piece must be genuinely concrete — not planning, not reviewing, not “getting oriented.” An actual action with an output. One paragraph, one line of code, one item on the form.
Then:
If the fatigue lifts, it was load. This is the common result, and it’s often dramatic — people report the heaviness draining within two or three minutes of real work. What happened is that you replaced an undefined object with a defined one, and defined objects have knowable costs. There’s nothing left to be heavy about.
If the fatigue is unchanged or worse, it’s depletion. You’re actually out of resource. Continuing is not brave, and it’s the response that does damage. That’s type four in procrastination isn’t laziness, and the fix is rest rather than any technique on this page.
The test works because the two states respond oppositely to the same intervention, which is the only reliable way to separate things that feel identical.
Run it before deciding which problem you have. Most people decide by feel, and feel is precisely the instrument that can’t tell them apart.
Why Misdiagnosis Costs So Much
Worth spelling out, because both errors are common and both are expensive.
Treating depletion as load means pushing through genuine exhaustion, repeatedly, on the theory that starting will fix it. It doesn’t, the resource keeps draining, and the pattern that produces is not one anyone recovers from quickly.
Treating load as depletion means resting a problem that rest cannot touch. You take a week off, feel fine, sit down at the end of it, and the fatigue is exactly where you left it — because it wasn’t tiredness, it was an unspecified object still sitting unspecified. Then you conclude that the rest didn’t work and that something is more seriously wrong.
That second error is the more common one, and it’s the more discouraging, because a failed rest reads as evidence of a deeper problem.
And a note worth including plainly: if the tiredness is broad rather than task-specific, persistent over weeks, and doesn’t respond to sleep, that’s worth raising with a doctor. There are medical explanations for that pattern and none of them are addressed by anything in this article.
What This Is Not
It is not a claim that pre-task tiredness is imaginary. The fatigue is real and it’s measurable in its effects. What’s misidentified is its source, not its existence.
It is not “just start and you’ll feel better.” That advice is right about a third of the time and actively harmful the rest. The proposal here is a five-minute diagnostic with two possible outcomes, one of which is to stop.
It is not a substitute for looking at your circumstances. Someone with a newborn, a demanding job, and a sick parent is tired for reasons no test will reframe. Some fatigue is a straightforward consequence of load-bearing circumstances and doesn’t need diagnosing.
The Cost
The price here is specific and slightly circular, which is what makes it difficult.
You have to start in order to find out whether you should start.
That’s the trap. The test requires five minutes of real work, and the fatigue’s entire function is to prevent five minutes of real work. So the diagnostic sits on the wrong side of the thing it’s meant to diagnose.
There’s no clever way around it. The five minutes has to happen while you feel too tired to do it, on the possibility that the tiredness is a bill rather than a reading.
Second cost: sometimes the answer is depletion, and depletion has no interesting fix. There’s no technique, no reframe, no productivity insight. There’s just stopping, which is unsatisfying and, for most people reading this, considerably harder than working.
That’s frequently the real reason people don’t run the test. They can guess the answer and they’d rather have the option of pushing.
Common Questions
Why do I feel exhausted before I’ve begun?
Usually because you’ve repeatedly held an unspecified task in attention over months, each time paying the cost of the whole undefined thing. The accumulated total presents as fatigue at the moment you approach it. It’s a bill for work you never did rather than a forecast of the work ahead.
Is pre-task tiredness real or am I making excuses?
Real, and measurable in its effects. What’s usually wrong is the attribution, not the sensation. Load and depletion feel identical, which is why the source can’t be determined by how it feels.
How do I tell tiredness from avoidance?
Do five minutes of genuinely concrete work and check. If the heaviness lifts, it was load. If it’s unchanged or worse, it’s depletion and the correct response is to stop.
Why does resting sometimes not help?
Because rest treats depletion, and if the problem is an unspecified task, a week off leaves it exactly as unspecified as it was. You return rested and the fatigue is unchanged, which is easy to misread as evidence of something more serious.
Why is the tiredness worst at the moment I sit down?
Because sitting down to an undefined project triggers a rehearsal of the whole thing rather than of the session. Thinking about it casually is cheaper than approaching it, because approaching it recruits the full simulation.
When should I see a doctor about this?
If the tiredness is broad rather than specific to one task, persists over weeks, and doesn’t respond to sleep. That pattern has medical explanations and none of them are productivity problems.
Where to Start
Tomorrow. The task you’ve been avoiding. One instruction.
Set a timer for five minutes and do the smallest real piece.
Not planning. Not reading back over what’s there. Not organising the folder. An action with an output — one paragraph, one entry, one call.
When the timer goes, stop and ask one question: is it lighter?
That’s the whole thing. You’re not trying to work. You’re running a measurement, and the measurement takes five minutes and resolves a question you’ve had for months.
If it’s lighter, you now know the problem was specification, and the fix is decomposition rather than rest or resolve.
If it isn’t, you now know you’re genuinely depleted, and you can stop with a clear conscience instead of spending another four weeks alternating between forcing and feeling guilty.
Either answer is worth five minutes. Not knowing has been costing you considerably more than that, every time the thing crosses your mind.
I’ve spent twenty-five years working on how ordinary people develop capabilities that look impossible from the outside, and a surprising amount of what looks like extraordinary stamina is nothing of the kind.
It’s someone who isn’t carrying eleven undefined objects around, paying for all of them, every time one crosses their mind.