"Why Can't I Just Be Consistent?"

Tuesday, and then Thursday

On Tuesday you answered every email within the hour, ran a meeting that actually stayed on time, cooked dinner, and still had the energy to reply to a friend's message with something more than a thumbs-up. On Thursday, two days later, the same inbox felt like a wall. The same meeting agenda swam in front of you. You forgot to eat lunch and noticed at 4pm that you'd been staring at one paragraph of a document for twenty minutes without reading a word of it.

Nothing obvious changed between those two days. You didn't sleep dramatically worse, drink more the night before, or face a harder workload on paper. And yet the gap in what you produced was enormous — enormous enough that if a stranger watched only Tuesday, they'd assume you were highly capable, and if they watched only Thursday, they'd assume the opposite. Both would be watching the same person.

The question underneath the question

"Why can't I just be consistent" is rarely really a question about time management. It's a question about identity: which version of me is the real one — the Tuesday version or the Thursday version? And if I can do it sometimes, doesn't that prove I could always do it, if I just tried harder, cared more, or built better habits?

That logic feels airtight, and it's also the exact place where the moral reading of inconsistency takes hold. If capability is proof of choice, then incapability must be proof of a lesser choice — not trying, not caring, not disciplined enough. It's a tidy story. It's also built on a false premise: that a single high-performing day is evidence of a stable, on-demand baseline, rather than evidence that the right conditions happened to line up.

What actually varies day to day

For a brain that manages attention and executive function differently, output on any given task is the product of several variables stacking on top of each other, not a single dial called "effort." Interest is one of them — tasks that are novel, urgent, or personally meaningful can recruit sustained focus almost automatically, while tasks that are none of those things require the brain to manufacture engagement from nothing, which is expensive and unreliable work. This is sometimes described through the idea of an interest-based nervous system: not that interest is the only thing that matters, but that it does more of the heavy lifting than it does for many other people.

Then there's accumulated load. Executive function draws from a limited daily supply, and it gets spent on things that never show up on a to-do list: masking distraction in a meeting, managing a mildly annoying interaction, resisting an urge to check your phone forty separate times. By Thursday afternoon, if Tuesday and Wednesday both quietly drained that supply, there may simply be less left to spend — even though nothing about Thursday's actual to-do list looks harder.

Context matters more than people expect, too. A slightly noisier room, a task with a vaguer starting point, a night of lighter sleep, a stretch without exercise, a lingering low-grade worry about something unrelated — none of these would derail most people's day much, but for a system already working harder to sustain attention, they can be the difference between a task starting in ninety seconds and a task not starting at all.

And then there's the sheer executive demand of the task itself. Two tasks that look equivalent on paper — reply to this email, write that report — can require very different amounts of initiation, sequencing, and working-memory holding. The email might have a clear single action. The report might require holding four sub-steps in mind at once while also filtering out distraction, which is a fundamentally heavier lift regardless of how much time either one takes.

Where personal responsibility still lives

None of this means inconsistency has no cost, or that it's entirely out of your hands. A missed deadline still affects a colleague's week. A forgotten plan still lands on a friend who was looking forward to it. Understanding the mechanism behind inconsistency is not a reason to stop building structure around it, and it's not a reason to skip the apology or the fix when it affects someone else.

The useful shift isn't from "I'm responsible" to "I'm not responsible." It's from "I should be able to will myself into an even baseline through more effort" to "my baseline is genuinely more variable, so my systems need to account for variability rather than assume it away." That's a more honest engineering problem than a moral one, and it's a far more solvable one. Buffer time, externalised reminders, choosing which few things truly need Tuesday-level performance and protecting those — these are responses to a real pattern, not excuses for one.