Every business has more problems than time. The hard part isn't finding something to fix. It's choosing the one thing to fix first, and having a reason you can explain to your team.

Earn the Change starts with a list, and then a simple way to rank it.

Start with the list

Set a timer for 20 minutes. Write down every recurring process you can think of, one line each, using the names people actually use. "Getting the quote out." "Chasing late invoices." "Friday truck check." Don't explain them. Just list.

The easiest way to catch everything is to walk the customer's path: first contact, quote, booking, doing the work, follow-up, getting paid. Then walk the back office. Most owners find fifteen to thirty processes in that first pass, including a few nobody would have put on a standard list.

Exhibit 1

Each stage of the customer's path hides a process

What the customer lives through on the left; the work your team does to carry it on the right.

Customer's path

Process behind it

1. Reaching out
Answering the phone
2. Getting a visit
Booking the visit
3. Getting diagnosed
Running the site visit
4. Getting a price
Getting the quote outScored 18
5. Deciding
Chasing the yes
6. Committing
Taking the deposit
7. Waiting for the install
Scheduling the install
8. Getting it installed
Doing the install
9. Paying
Sending the final invoice
10. After the job
The follow-up call

Source: Earn the Change, Troy Green

Rate three things

For each process, rate three things high, medium, or low:

  • Stakes. How close does it sit to customers, revenue, or risk?
  • Pain. How much does it hurt today: delays, rework, complaints, stress?
  • Frequency. How often does it run?

Not all three count the same

Stakes counts three times. Pain counts twice. Frequency counts once. With high as 3, medium as 2 and low as 1, every process ends up with a score between 6 and 18.

Why weight them? Because a process that runs constantly but doesn't matter much shouldn't outrank one that rarely runs but decides whether you keep a customer. Frequency matters, but it's the tiebreaker, not the headline.

There's also one guard: a process rated low on stakes never gets chosen by default, however painful or frequent it is. Annoying isn't the same as important.

Then decide, out loud

The score sets the starting order. It doesn't make the decision for you. You might pick the second process because the first one is owned by someone who isn't ready, or because a busy season is coming. That's fine. The point is that you write down the reason. A choice with a reason can be discussed. A choice without one just becomes the boss's preference.

In one example from the book, a service business walked its customer path and found fifteen recurring processes. "Getting the quote out" scored a perfect 18: it ran every day, hurt the most, and sat right where customers decided whether to buy. That was the one.

Exhibit 2

Two tests point every process down one of three roads

Name the outcome in one sentence

Stop test

If it stopped tomorrow, would anyone notice?

Nobody →

Stop

Next: Run it small, to prove nothing breaks

Yes

Clean-sheet test

Starting fresh today, would it look like this?

No →

Redesign from the outcome up

Next: Obstacle, to pick a slice to pilot

Yes, keep its shape

→

Improve it

Next: Obstacle, to find the bottleneck

Source: Earn the Change, Troy Green

One at a time

The final rule is the one owners resist most: fix one process at a time. Not three in parallel. One, proven, then the next. Parallel changes tangle together, and when results move you can't tell which change did it.

Try it now

The free WORTH Process Scorer walks you through exactly this: the list, the ratings, the weighted score, and a clear first pick with your reasons. It takes about 15 minutes, and you'll leave knowing which process to fix first.