Look at your list.

Whatever form it takes — the app, the notebook, the running mental version. Look at what you did today and what’s still on it.

There’s a pattern, and it’s the same for almost everybody: you did the items in order of ease.

Not deliberately. You didn’t rank them. But the small, clear, low-friction items got done and the item you’ve been carrying for three weeks is still there, and it’s still there because every time you scanned the list your attention slid off it.

Now the uncomfortable part. That ordering is close to exactly inverse to the order of return.

Here’s why, and there’s an important exception that most versions of this argument get wrong.

Why Costly Actions Return More

Actions that a person finds difficult tend to produce higher returns than actions they find easy, for three structural reasons rather than moral ones. First, difficulty functions as a proxy for scarcity: an action that is easy has generally already been taken, both by the person and by others, so the remaining value in it is low. Second, difficult actions are the ones that change the actor, since an action requiring nothing of a person leaves them unaltered, and outcomes follow from the person. Third, aversion is a reasonably reliable indicator of load-bearing constraints — people preferentially avoid the actions that would resolve the binding limitation, so the avoided item is frequently the one the sequence depends on. This produces a systematic misallocation, since work is typically ordered by ease rather than by return. The relationship holds only where difficulty arises from consequence rather than from tedium, which is a distinction worth checking before applying it.

Three mechanisms. Then the exception.

One: Easy Means Already Done

The simplest and least discussed.

If something is easy for you, it’s probably easy for most people in your position. Which means it’s been done — by them, and probably by you already, several times.

The remaining value in easy actions is low because the field is crowded. There’s no scarcity, and scarcity is where returns live.

The difficult action has thin competition precisely because it’s difficult. The conversation nobody wants to have hasn’t been had. The unglamorous groundwork nobody wants to do hasn’t been done. The person nobody wants to approach hasn’t been approached.

Difficulty is a proxy for how many people got there before you. Not a perfect one, but a decent one, and it’s available for free on every item on your list.

Two: Costly Actions Change You

Second, and it connects to the mechanism in half good and full good.

An action that costs you nothing leaves you exactly as you were. You executed something already within your repertoire, at no expense, and the person who finishes the action is identical to the person who started it.

An action that costs you something requires you to be slightly different for a moment — to tolerate discomfort, to risk standing, to do something you weren’t sure you could.

And outcomes follow from the person.

So the easy items produce output without producing change, which means they produce output on your existing trajectory. The costly ones move the trajectory slightly, which compounds.

That’s why a year of exclusively comfortable work leaves someone in exactly the position they’d have predicted, having been genuinely busy the whole time.

Three: Aversion Detects the Constraint

Third, and it’s the most immediately useful.

You don’t avoid randomly. You avoid the things that would require something of you — and the things that require something of you are disproportionately the things that would change your situation.

Which makes your own aversion a rough instrument for locating the binding constraint.

The item you keep sliding past is frequently the one the rest of the sequence depends on. The call you haven’t made. The number you haven’t checked. The person you haven’t asked. The thing you’d have to admit.

That’s not mystical. It’s the same reason the load-bearing wall is the one you’re nervous about touching — you have an accurate, unarticulated sense of what’s holding weight, and you route around it.

The practical version: on any list, scan for what you’ve been sliding past, and treat that as a candidate for the actual constraint. It’s right often enough to be worth checking every time.

The Exception That Matters

Now — and this is where most versions of this argument go wrong, and where I need to reconcile something.

Elsewhere in this material I’ve argued the opposite: start with the easiest action, not the most important one.

Both are correct, and they apply to different problems.

Easiest-first applies to starting. When the problem is that you cannot begin at all — the project is dormant, the file hasn’t been opened, you’re paralysed — the easiest action is the right first move. Its purpose isn’t output. It’s to move the project from dormant to active, and the cheapest thing that does that is the correct thing. Attempting the hardest item while paralysed produces failure, and failure at that moment becomes evidence you can’t do this. That’s the argument in why you can’t start something you actually want.

Hardest-first applies to allocating. Once you’re already working — once the thing is live and you’re choosing what to do next with a working session — the difficult item has the higher return, and doing the easy items first will consume the session and leave it untouched.

So: easiest to break the state, hardest to spend the state.

If you’re stuck, take the trivial action. If you’re moving, take the costly one.

Getting this backwards in either direction is expensive. Hardest-first while paralysed produces another failed start. Easiest-first while working produces a very busy year with nothing to show.

When Difficulty Isn’t Leverage

One more distinction, because “do the hard thing” is bad advice applied indiscriminately.

Difficulty comes from two sources and only one of them indicates value.

Consequential difficulty. The action is hard because something is at stake — you might be refused, you might be seen failing, you’d have to change something, you’d have to admit something. This is the kind that indicates leverage.

Tedium. The action is hard because it’s long, repetitive, and dull. There’s no stake, just friction.

Tedium is not leverage. A four-hour data cleanup you’re avoiding because it’s boring is not secretly the constraint — it’s just boring, and if someone else can do it, they should.

The test: if this were somehow made pleasant, would it still matter? If yes, it’s consequential. If the only thing making it hard is that it’s dull, delegate it or batch it and stop treating your aversion as a signal.

That distinction saves people from the version of this advice where they heroically do their own filing.

What This Is Not

It is not “do things because they’re hard.” Difficulty isn’t the value — it’s a proxy for the value, and proxies fail. A pointless difficult task is still pointless. The claim is that among actions genuinely relevant to your objective, the costly ones return more.

It is not an argument for constant discomfort. Most of any working week is legitimately routine and should be. The claim concerns allocation of your limited high-capability time, which is a small fraction of the total. That interacts directly with where your best hours actually go.

It is not a moral point. Nothing here says the hard path is more virtuous. It’s a leverage claim, and if the easy action genuinely returned more I’d tell you to do that.

The Cost

The price is ongoing rather than one-off, which makes it worse.

You have to reorder your day against your inclination, permanently.

This isn’t a decision you make once. Every working day presents a list, and every day the easy items will look more appealing, and the appeal is not a rational assessment you can argue with — it’s a pull.

So you’re signing up for a small act of resistance every morning, indefinitely, with no point at which it becomes automatic.

Second cost, and it’s more subtle: doing the hard item first means your day feels less productive. You’ll finish having completed one thing instead of nine, and the nine-item day feels enormously better even when it produced less.

You’re trading the sensation of productivity for the fact of it, and the sensation is what you get every day while the fact arrives months later.

Common Questions

Why does difficult work produce more results than easy work?
Three reasons. Easy actions have generally already been taken by you and others, so the remaining value is low. Costly actions change the person taking them, and outcomes follow from the person. And people preferentially avoid the actions that would resolve the binding constraint, so the avoided item is often load-bearing.

Should I always do the hardest task first?
No — it depends which problem you have. If you’re stuck and can’t begin at all, take the easiest action, because its job is to make the project active rather than to produce output. If you’re already working and choosing what to spend a session on, take the hardest.

Why is the thing I’m avoiding usually the important one?
Because avoidance isn’t random. You avoid what would require something of you, and what requires something of you is disproportionately what would change your situation. Your aversion functions as a rough detector for the load-bearing item.

Does difficulty always indicate value?
Only when the difficulty is consequential rather than tedious. If something is hard purely because it’s long and dull, that’s friction rather than leverage. The check: if it were made pleasant, would it still matter?

Why do I feel less productive on days I do this?
Because you complete one thing instead of nine, and completion count is what produces the sensation of productivity. You’re trading the feeling for the result, and the feeling arrives daily while the result arrives much later.

What if I can’t tell which item is the constraint?
Look for what you’ve been sliding past — the item your attention leaves every time you scan the list. It’s right often enough to be worth checking, and it costs nothing to test.

Where to Start

Tomorrow. One change. One day.

Before you open anything reactive, do the item you’ve been sliding past.

Not the whole thing if it’s large. Thirty minutes of it, or the first genuinely costly step within it — the call, the question, the number you’ve been assuming.

Then check it against the two filters, honestly, before you start:

Is the difficulty consequential or tedious? If it’s just dull, it isn’t the item and you should pick a different one.

Am I stuck or am I moving? If the project is dormant and you haven’t touched it in months, this instruction doesn’t apply to you today — take the easiest action instead, and come back to this when the thing is live.

Assuming both filters pass, do that one thing first, and then go and have your normal day.

At the end of it you’ll have completed fewer things and you’ll feel worse about the day, which is the correct and expected experience.

Check what actually moved.

I’ve spent twenty-five years working on how ordinary people develop capabilities that look impossible from the outside, and one of the more reliable differences is unglamorous.

Their lists look the same as everyone else’s. They just work down them in a different order.