Most improvement efforts start in the wrong place. Someone sees a demo, or hears what a competitor bought, and the question becomes "how do we make this faster?" It feels like progress. Meetings get scheduled. A tool gets trialed. Six months later, the work looks about the same, and everyone is a little more tired.

The problem usually isn't the tool or the people. It's the order of the questions.

One belief, worked out in detail

Everything in Earn the Change rests on one sentence:

Prove it's worth doing before you make it easy to do.

It sounds obvious. It's also the step most teams skip. When you skip it, you end up polishing a process that should have been changed, merged, or stopped. You make the wrong thing efficient. And efficient wrong things are harder to remove later, because now somebody built them and somebody is proud of them.

What "worth doing" actually means

Proving something is worth doing doesn't take a business case or a consultant. It takes three honest answers:

  • Why does this process exist? Who is it for, and what would break if it stopped tomorrow?
  • What is actually in the way? Not the general frustration, but the specific step where the work slows down, breaks, or gets redone.
  • Can we show it, small? Change one thing, on real work, for a short time, and see if the number moves.

Those three questions are the W, O, and R of the WORTH method. The last two, Trade-offs and Habit, are how you keep the change fair and make it stick. But they only matter once you know the change earned its place.

Why skipping the proof is so expensive

When a change hasn't been proven, every disagreement about it becomes a matter of opinion. The person who likes the new way says it's working. The person who doesn't says it isn't. Nobody can settle it, because nobody wrote down what "working" was supposed to look like.

A proof settles it. Before the change, you pick one number that should move if the change is right. You write down where it starts. You set a target and a date. Then the change either earns its way forward or it doesn't. That's not bureaucracy. It's the kindest thing you can do for the people who'll have to live with the result.

Exhibit 1

Prove it's worth doing first, then make it easy

Move up before you move right. The bottom right is the trap: popular, but nothing improves.

Hard to adopt

Easy to adopt

Valuable

Stalls after launch

Valuable, but nobody keeps doing it

Fix: Trade-offs and Habit

The goal

Proven, and the new way is the easy way

Lock it in, pick the next one

Not valuable

Fades on its own

Doesn't help and doesn't stick

Stopped early and cheaply

Busy but pointless

Usage looks great; results don't move

Caught at Run it small

Source: Earn the Change, Troy Green

Easy comes second, on purpose

None of this means speed and convenience don't matter. They do. Once a change has proven itself, making it easy is exactly the right next step: a template, a checklist, a tool, sometimes AI. The point is sequence. Easy is a reward for proof, not a substitute for it.

That's also why tools sit at the end of the method. A tool makes a process easier to run. It can't tell you whether the process deserves to be run at all.

Exhibit 2

The line between proving it and making it stick

Three steps prove the change is worth doing. Only then do two steps make it easy to do.

Worth doing · prove it

W

Why

O

Obstacle

R

Run it small

The line

Easy to do · make it stick

T

Trade-offs

H

Habit

Source: Earn the Change, Troy Green

Where to start this week

Pick one recurring process that frustrates you. Before you think about how to fix it, write down one sentence: this process exists so that ___. If you can't fill in the blank, you've learned something more valuable than any fix. If you can, you're ready for the next question: what is actually in the way?

Start there. Prove it. Then make it easy.