Flow Is Not Proof of Priority

I have just had eight consecutive days of genuinely good creative output. In the same eight days I did not touch a single item on my financial admin list — a statutory filing that is now overdue, and a material receivable that hasn't moved.

The creative work was real. It wasn't procrastination dressed up as productivity. It produced a finished campaign, a positioning I can defend, and a reusable system for making more of it. That's precisely what makes this worth writing down: the output is the alibi.

The flawed inference

The reasoning I was running, mostly unconsciously, went: this work is flowing, flow means I'm doing the thing I'm best suited to right now, therefore this is the right use of today.

Every step of that is wrong except the first.

Flow is a property of the fit between a task's difficulty and your skill at it. It says nothing whatsoever about whether the task matters. And the tasks that reliably produce flow are, almost by definition, the ones you're already good at — which means flow is a signal about your history, not about your priorities.

Meanwhile, the tasks that block share a different set of properties. They usually involve ambiguity about the first step, or another person who might say no, or a number you'd rather not look at. None of those are difficulty in the skill sense. They're friction of a kind that skill doesn't reduce, which is exactly why getting better at your craft never makes them easier and can make avoiding them more comfortable.

The tell that separates momentum from avoidance

This is the part I found useful, because "am I avoiding something?" is a question I can rationalise my way out of on any given day.

The distinguishing signal is not whether things slipped. It's whether the same thing slipped.

If different items slide on different days, that's an ordinary busy period and it self-corrects. If one specific item slides for eight consecutive days while everything else ships on time, that is not a scheduling problem. Scheduling problems are indiscriminate. A perfectly stable exception is a structural preference — and if productive work is what's filling the slot that item keeps not occupying, then the productive work is funding the avoidance.

Avoidance that produces nothing is easy to catch; it looks like a bad week. Avoidance that produces a finished piece of work looks like a good week. That's the whole trap.

The change

Two adjustments, both structural rather than motivational, because motivational fixes are what got me eight days deep.

Track the age of the oldest untouched item, not the volume of what got done. Daily output is a terrible metric here — mine was excellent throughout. The number that would have caught this on day three is "how long has the oldest open item been open," and it's a number I wasn't looking at because nothing in how I review my days surfaces it.

Schedule the blocked item first, and not because it's more important. On most individual days it genuinely isn't more important. It goes first because it's the only item on the list that will not happen otherwise. Everything that flows will find its way into the day regardless; that's what flowing means. The blocked item has exactly one chance, and it's before the good work starts.

The uncomfortable version of the lesson: a business with sharp positioning and unfiled taxes is still a business with unfiled taxes. The quality of what I built during the avoidance doesn't offset it. It just made it take eight days to notice.