Think about yesterday and answer two questions.
When were you actually sharp? There’ll be a window — probably two or three hours, possibly less. The period where the difficult thing would have been possible, where your judgement was good, where you could hold several things at once without dropping any.
What did you spend it on?
For most people the honest answer is: email, a meeting somebody else scheduled, and about forty minutes of small urgent things that arrived early and felt like they needed handling.
Then at four in the afternoon, spent, you sat down to do the work that actually required judgement.
That’s not a time management problem. You have enough hours. It’s an allocation problem, and it has a specific structure.
Why the Best Hours Go First
Working hours are not interchangeable. Cognitive capability varies substantially across a day, with most people having a limited window — commonly two to four hours — in which demanding work is possible at full quality, and a longer remainder suitable for routine work. Because this variation is not usually made explicit, hours are treated as fungible and allocated by urgency rather than by the capability each task requires. This produces a systematic misallocation: the highest-capability hours occur early, incoming requests also arrive early, and requests present as urgent, so the best hours are reliably consumed by work that could have been done at low capability. The demanding work is then attempted in the remaining hours, when capability is lowest, which produces both worse output and the impression of insufficient ability. The constraint is allocation rather than quantity, and additional hours do not resolve it because the additional hours are low-capability ones.
Three mechanisms consume them. All three are avoidable and none of them are your fault.
Thief One: Reactive Intake
The largest, and it operates in the first thirty minutes.
You open email, or messages, or whatever the equivalent is in your work. And within about ten minutes you have four things that other people need, each of which is small, each of which is genuinely quick, and each of which is now sitting in your head.
Two costs, and the second is bigger than the first.
The direct cost is the time you spend handling them. Forty minutes, say.
The indirect cost is that you’ve now loaded four open items into a working memory that was about to be used for something difficult. Even after you’ve dealt with them, the residue occupies capacity for a while. You’ve spent forty minutes and degraded the following ninety.
That’s why “I’ll just clear my inbox first and then start properly” doesn’t work, and why people who do it report that they never seem to get to the real work. They get to it. They get to it with a container that’s already partly full.
Thief Two: Other People’s Calendars
Second, and it’s structural rather than personal.
Meetings get scheduled by whoever needs them, and they get scheduled into whatever’s open. Nobody scheduling a meeting is thinking about your cognitive profile — they’re thinking about a gap.
So over time your calendar fills according to other people’s requirements, and the morning fills first because mornings are when people schedule things.
The result is that your best window is systematically the most fragmented part of your day, and fragmentation is worse than loss. Two clear hours are worth considerably more than four hours broken into three pieces, because demanding work has a load-in cost that has to be paid every time you return to it.
The tell: if your best thinking happens on the rare day a meeting gets cancelled, your calendar is the constraint.
Thief Three: High-Capability Time Spent on Low-Capability Decisions
Third, and it’s the most avoidable.
A great deal of what fills a morning is decisions that don’t require your best judgement. Approvals. Routine choices. Small preferences. Things where any reasonable answer is fine and speed matters more than quality.
Those can be made at four in the afternoon, at reduced capability, with no loss whatsoever.
Instead they’re made at nine, at full capability, because they arrived at nine.
You’re spending your scarcest resource on the tasks with the lowest requirement, purely because of arrival order. Urgency is determining allocation, and urgency is uncorrelated with the capability a task needs.
The Audit
Don’t track your whole week. Whole-week time tracking is tedious, produces a wall of data, and almost nobody sustains it past day three.
Track one thing:
For five days, write down what you did in your best two hours.
Two lines a day. That’s the entire instrument.
You need to know when your best two hours are, and most people know within about twenty minutes without any measurement — it’s the window where you don’t have to force it. If you genuinely can’t tell, note when the difficult thing felt possible.
At the end of the week you’ll have ten lines. Read them together.
The finding is nearly always the same, and it’s uncomfortable in a specific way: most of your best hours went to work that a less capable version of you could have done perfectly well.
Not wasted, exactly. Everything on that list was real work that needed doing. It just didn’t need those hours.
The Fix Is Reallocation, Not More Time
Here’s why this connects to the rest of this material rather than being a productivity tip.
The instinct on discovering this is to find more hours. Get up earlier, work later, protect the weekend.
That doesn’t work, and the reason is in the model: the extra hours you find are low-capability hours. Adding volume at the bottom of the quality curve doesn’t produce more of the thing you’re short of. You’re short of sharp hours, and there are only so many, and no amount of discipline generates additional ones.
The only available move is reallocation. Which means, concretely:
Protecting the window. Blocking it before other people’s requests arrive, which usually means the night before rather than the morning of.
Delaying intake. Not opening the reactive channels until the window has been used. This is the single highest-return change available and almost nobody makes it, because the first hour is exactly when everything arrives.
Moving low-requirement decisions to low-capability hours. Batching them deliberately into the afternoon, where they belong.
And here’s the part that makes it hard: all three require declining things. Protecting a window means being unavailable during it. Delaying intake means someone waits. Batching decisions means somebody doesn’t get an answer immediately.
Which is why this is fundamentally the same problem as not being able to say no, wearing different clothes. The person who can’t protect their morning usually can’t protect anything, and the calendar is just where it’s most visible.
What This Is Not
It is not a claim that everyone is sharpest in the morning. Some people genuinely aren’t. The claim is that there’s a window and that it’s being misallocated, not that it’s at a particular time. If yours is at nine in the evening, the same argument applies to the same effect.
It is not about doing more. The output of this audit is usually that you do less in your best hours — one substantial thing rather than eleven small ones — and the total production goes up.
It is not a substitute for capacity work. If the underlying constraint is capacity rather than effort, reallocating hours produces a modest improvement and then stalls. This is a real lever and it isn’t the deepest one.
The Cost
The price is straightforward and it’s paid by other people, which is why it’s difficult.
Protecting your best hours makes you less available, and availability is currently part of your reputation.
You’re the person who responds quickly. That’s been valuable, it’s been noticed, and some part of your standing rests on it.
Blocking two hours a day means messages sit for two hours. Nothing catastrophic happens — nothing ever does — but somebody will notice, and one person will comment on it, and you’ll feel it.
That’s the actual reason almost nobody does this despite everybody understanding it. Not that they can’t identify their best hours. That the fix requires a small, visible, ongoing reduction in how helpful they appear.
Second cost: you’ll find out what you’ve been doing with them, and the five-day audit is genuinely deflating. Ten lines is a small artefact for a large discovery.
Common Questions
Are all working hours equally valuable?
No, and treating them as interchangeable is the source of the problem. Most people have a limited window of high capability — often two to four hours — with the remainder suitable for routine work. Allocating by urgency rather than by capability requirement systematically wastes the window.
Why do I end up doing my hardest work when I’m tired?
Because the demanding work has no external deadline pressing at nine in the morning, while incoming requests do. Urgency wins the allocation, the window gets consumed, and the difficult thing falls through to whatever’s left.
Why doesn’t clearing my inbox first work?
Because handling four small items loads them into working memory and leaves a residue. You spend the direct time and degrade the following period, so the window is diminished before the real work begins.
Should I just work more hours?
It doesn’t help, because the additional hours are low-capability ones. You’re short of sharp hours specifically, and volume at the bottom of the quality curve doesn’t produce more of them.
What if my best hours aren’t in the morning?
The argument is unchanged. The window is being consumed by whatever arrives during it, and the fix is the same: protect it, delay reactive intake until after it, and batch low-requirement decisions elsewhere.
Why is this so hard if it’s obvious?
Because every part of the fix requires declining something — being unavailable, letting someone wait, not answering immediately. It’s a refusal problem wearing a scheduling costume.
Where to Start
Five days. Two lines a day. Nothing else.
Write down what you did in your best two hours.
Don’t change anything while you’re measuring. Don’t optimise, don’t protect the time, don’t feel bad about the entries. You’re taking a reading, and readings taken while you’re trying to improve the number are useless.
At the end of the week, read the ten lines together and mark each one with a single letter:
H if it genuinely required your best capability.
L if a tired version of you could have done it just as well.
Count the Ls.
That number is what you’re actually working with, and it’s usually somewhere around seven out of ten. It’s also the most actionable figure you’ll produce about your own working life, because every L is an hour you already have and are giving to something that didn’t need it.
Then next week, move one L. Just one — one recurring low-requirement thing shifted out of the window into the afternoon.
One is enough to find out whether the world objects. It mostly doesn’t, which is the finding that makes the rest possible.
I’ve spent twenty-five years working on how ordinary people develop capabilities that look impossible from the outside, and the ones who produce a startling amount are rarely working longer than everyone else.
They’ve just worked out that they get about two good hours, and they spend them like it.