Everything you are tolerating

One

Two kinds of hard

There is a kind of difficulty that builds something. Training that leaves you shaking. A problem you cannot yet solve. A conversation you have been avoiding and finally have. Deep work held for three hours without looking up. Risk taken deliberately, with the downside known.

And there is a kind of difficulty that builds nothing at all. Looking for the keys. A process that breaks every third time and gets patched by hand. A bill nobody cancelled. A person who is unreliable in a way everyone has silently agreed to work around. A decision that gets re-made every Tuesday because it was never actually made. A room you cannot think in.

The second kind feels like effort. It even feels a little like virtue — you were busy. But it produces nothing, and worse, it consumes exactly the resource the first kind needs.

Make the important things hard, and everything surrounding them easy.

That sentence is the whole design brief. It is also why the popular framing of this — optimise, streamline, hack — misses. You are not trying to reduce total difficulty. You are trying to move it: out of the plumbing and into the work.

And there is a reason to do it now rather than later. Friction compounds with responsibility. At a small scale, inefficiency is annoying. As the scale of what you are responsible for grows, the same unresolved drag stops being annoying and starts being the thing that breaks. What follows is a way of designing that operating system before scale exposes every weakness in it.

Two

Vague suffering cannot be engineered away

The first pass is a census. You write down every recurring source of drag, dread, resistance, leakage or unnecessary complexity — and you do it without editing. No solving yet. No deciding whether it is reasonable to be bothered. Just the list.

There is exactly one rule, and everything downstream depends on it: be specific. A named category is not a friction point. It is a place where a friction point is hiding.

Notice what happened in the right-hand column. The vague version can only be endured. The specific version already suggests where the lever is. That is not a writing trick — it is the actual mechanism of the exercise. You cannot engineer against a mood. You can engineer against a described event.

The prompts below are there to jog the list, not to constrain it. Go through them slowly. Most people stall around item four and then find eleven more.

Three

Four boxes, and the three ways people misfile

Now sort every item into one of four categories. This step alone tends to expose more than the writing did.

Control — you can directly change this. Influence — you cannot dictate it, but your actions materially affect it. Accept — a reality you genuinely cannot alter. Exit — you can remove yourself from the system entirely.

People burn enormous energy in three specific ways, and each is a misfiling:

They pour effort into things that belong in Accept — arguing with weather, with other people's temperaments, with the past. They tolerate things that belong in Exit, because leaving feels dramatic and enduring feels mature. And they fail to execute on obvious items in Control, which are usually small, boring and entirely within reach.

The fourth box is the interesting one. Exit is the least-used option and the most underrated. A surprising share of long-running friction is a system somebody could simply stop being in — and the reason they haven't is almost never the reason they'd give.

Four

You do not have seventeen problems

The third pass is the one that changes the shape of the thing. For every item you ask a single question: why does this repeatedly generate friction? Not what it feels like. What causes it.

Almost all recurring drag traces back to a surprisingly small set of mechanisms. Ambiguity. Too many decisions. A poor environment. Work a machine should be doing. Not enough resources. Incentives that reward the friction. Boundaries that let it in. Commitments never closed. Things done in the wrong order. Dependencies that needn't exist. A routine that changes daily. Standards never specified. A skill not yet learned. The wrong people in the loop. An arrangement that is simply wrong. And doing any of it while depleted.

When people run this honestly, seventeen complaints usually collapse into three or four causes. That is the most valuable output of the whole exercise, because it changes what you work on. Seventeen problems is a life sentence. Three mechanisms is an afternoon's design work with very large downstream effects.

A symptom list is long by nature. A cause list is short by nature.

Five

Keep the good friction

Before designing anything away, separate the two kinds of hard. Some of what you wrote down is supposed to be difficult, and removing it would be a loss dressed as an improvement.

Keep: hard training, difficult research, concentrated thinking, uncomfortable conversations, calculated risk, deliberate practice, long stretches of focused execution. These are costly on purpose. If they became effortless they would stop doing what they do.

Remove: looking for things, broken workflows, unnecessary bills, administrative chaos, unreliable people, unclear expectations, the same argument for the fourth time, bad sleep caused by preventable behaviour, cluttered surfaces, decisions that should long ago have become rules, and anything at all that sits beneath your comparative advantage.

The distinction is not how unpleasant. It is whether you chose it and whether it builds anything.

Six

What would have to be true?

This is the question that turns an audit into an architecture, and it has to be asked in a particular form. Not what should I do about this — that produces a task, and tasks recur. Ask instead: what would have to be true for this friction to largely disappear?

The answer must describe a state of the system, not an action. The difference is not pedantry; it is the difference between a chore and a design.

You are not trying to clean the office. You are trying to create an environment that naturally produces the thing you want. That is a different level of thinking, and it is the only one that stops the problem coming back.

Then: the ladder

There are only a handful of ways to remove friction, and they are not equal. Work down the list in order and take the first one that will actually hold:

Eliminate, then Automate, then Delegate, then Standardise, then Batch, then Constrain, then Relocate, then Renegotiate, and only then Accept.

The order carries the argument. The best solution to a recurring task is very often not doing it at all — so do not optimise something you could delete. If it cannot be deleted but software can do it, that is the next rung, not the third. If software cannot, hand it to someone whose comparative advantage it actually is. And if you must do it personally, at least standardise it, so you are not deciding how every single time.

Most people skip the top three rungs entirely and start at Standardise, because the top three feel like they require permission. They usually don't.

Seven

The question underneath all of it

One last thing, and it tends to reveal more than the census did.

What am I repeatedly tolerating that the person I intend to become would simply not tolerate?

Not because that person has finer taste. Because the tolerance itself is the constraint. Every standing irritation you have quietly agreed to live with is a small ongoing withdrawal, and the account it draws from is the one you were going to use for the work that matters.

Answer it in a sentence. It goes at the top of your sheet.