It's Not Four Problems. It's One, Wearing Four Masks

If you've ever tried to fix your "priority problem" and found that the fix didn't stick, I want to offer a different diagnosis:

You didn't have a priority problem. You had a capacity problem wearing a priority problem's clothes.

I see this constantly. Someone comes to me convinced their real issue is that they can't decide what matters. So they try a new prioritization framework — Eisenhower matrix, MoSCoW, whatever's trending this year — and for about a week and a half, it helps. Then it stops helping, in exactly the way every previous system stopped helping, and they conclude (again) that they're just bad at this.

They're not bad at this. The framework was never going to hold, because prioritization wasn't the actual problem.

Why "everything feels urgent" is almost never true

Here's the thing about priorities: they only compete with each other when there's no slack in the system.

If your workload has real breathing room, misjudging what matters this week is a minor, recoverable event. You put the wrong thing first, you notice within a day or two, you adjust. No crisis. That's what a functioning priority system looks like from the inside — quiet, boring, mostly invisible, because small errors get absorbed before they become emergencies.

But when the total amount of work already exceeds what you can realistically do, there's no room left to be wrong. Every task starts competing for the same vanishingly small margin. A minor misjudgment that would have been invisible under normal conditions instead becomes the reason you missed something. And because it feels like a prioritization failure — you picked the wrong thing! — that's exactly what gets blamed. Not the overload underneath it, which is the thing that turned a normal, ordinary imperfection into a five-alarm fire in the first place.

This is why "I just need to get better at prioritizing" is one of the most common things I hear, and one of the least often true. Most people asking that question don't have a priority problem. They have a capacity problem that's currently disguising itself as one.

Most prioritization frameworks quietly assume a working memory that holds everything in view at once, and a decision-making budget that's roughly the same on Tuesday as it is on Friday. Neither of those is a safe assumption for most people, and it's a particularly unsafe one for anyone whose attention and energy genuinely fluctuate day to day. A framework built on a flat, always-available baseline is going to fail exactly the people whose baseline isn't flat — not because the framework is wrong in general, but because it was never tested against in their reality.

The masks change. The root usually doesn't.

Priority chaos is one shape this takes. It's not the only one.

Sometimes it shows up as a system that worked beautifully for three weeks and then quietly fell apart — and the story becomes "I can't stick with anything," when the more accurate story might be that the system was never actually tested under real pressure, only under the ideal conditions in the designer’s mind.

Sometimes it shows up as a strange kind of busy-without-progress — weeks of genuine effort that don't add up to forward motion, because the effort was never anchored to a clear enough destination to navigate towards.

And sometimes, it really is straightforward overload: too much on the plate, full stop, no disguise required.

Four different-looking problems. Four different first instincts about what to fix. And underneath at least some of them, frequently, the same root cause wearing a different mask depending on which part of your work happened to be under the most pressure that particular month.

Why this distinction matters

It matters because the fix is completely different depending on which one you're actually looking at.

If your real constraint is capacity, no prioritization framework will save you — you'll just get more sophisticated at deciding which fires to let burn. If your real constraint is that your systems were never built to survive a bad week, no amount of willpower will make them survive one now. Treating a capacity problem as a prioritization problem doesn't just fail to help. It actively wastes the one thing you were already short on: time and attention you could have spent on the real problem.

So before reaching for a better framework, a better tool, or more discipline, it's worth asking a more basic question first: is this actually about what I'm choosing — or about how much I'm choosing from?

Four patterns, one series

Over the next few posts, I want to walk through four patterns I see constantly in this work — the priority one I've described here, along with two others that tend to travel with it, and a fourth that looks nothing like overload from the outside but often shares more with it than people expect.

Each one deserves its own look, in its own right, because each one calls for something a little different. But keep this post in the back of your mind as we go: sometimes the mask and the face underneath aren't the same thing, and knowing which one you're looking at is most of the battle.

One more thing worth naming before we get into the four patterns themselves: none of this is new to human brains. But something has clearly shifted, because I keep meeting people — neurodivergent people especially — who carried patterns like these for decades without them turning into a crisis …until fairly recently. I've got a separate piece of writing brewing on exactly that question: why traits that didn't used to be a problem need a diagnosis now. More on that soon. For now, the four patterns ahead are worth understanding on their own terms, whatever's driving them for you specifically.