Write it down first

Before any of this works, somebody has to write down how the work gets done today.

Not how it is supposed to get done. Not the version in the binder nobody has opened since 2019. How it actually happens. Including the part where you text yourself a reminder, and the part where Maria just knows.

This is the least popular thing I ask people to do. It is also the best sign of whether the rest will work.

Why you cannot skip it

A process that lives in your head has a sneaky quality: it adapts. You handle the weird cases without noticing. You skip a step when it clearly does not apply. You call the customer instead when something feels off.

You cannot hand that to a computer. It has to be written down before it can be automatic. And writing it down is where you find out that four people do it four different ways, and two of the steps only exist because of a problem you fixed in 2021.

Most owners find real money in this exercise before they install a single tool. Not because writing things down is magic. Because nobody had ever looked at the whole thing start to finish.

The exercise

Twenty minutes. Paper is fine. Pick one job that bugs you. Not the biggest one. The most annoying one.

1. What starts it? Something happens. A phone rings. A form comes in. A job gets marked done. Be specific, because that is what a system will watch for later.

2. What happens next, in order? Every step. Even the ones that feel too small to write. Look up the address. Check if we have been there before. Text Dave to see if he is free Thursday. The small steps are usually most of the time.

3. Who does each step? Name a person. If the answer is "whoever sees it first," write that down exactly. That is a real finding, and it is probably why things fall through.

4. Where does it get stuck? Be honest. There is one step where things sit. There always is. Mark it.

5. What happens when it goes wrong? Not the easy version. The customer is not home. The part is on back order. The price changed. Write down the three most common ones.

That is the whole exercise.

What you will find

Three things, almost every time.

A step that exists for no reason anymore. Some form that gets filled out and filed and never read. Delete it. Free.

A stall that is one person deep. Everything waits on the owner to approve something, or on the one person who knows the pricing. This is your real bottleneck, and it is usually not the thing you thought was the problem.

A step that only happens when someone remembers. The follow-up. The confirmation. The reminder. This is the one to automate. Not the step that takes the longest. The step that gets skipped.

That last part matters more than anything else here. People assume you should automate the slowest step. Usually you should automate the least reliable one. A step that takes ten minutes and always happens costs you ten minutes. A step that takes one minute and happens half the time costs you jobs.

What to do with it

Nothing yet.

Sit with it for a week. Cross out the steps that should not exist. Fix the ones that need a decision instead of a tool. A lot of stalls are a pricing rule nobody wrote down, not a software problem.

Then look at what is left. Ask which one step, if it happened every time without anyone remembering, would change your month.

That is the first thing to build. One step. Not the whole process.

Why this is the whole method

Every failed AI project I have seen skipped this. Somebody bought a tool for a problem described in one sentence, like we need to follow up better. Then during setup they found out nobody agreed on what following up meant, when it should happen, or whose job it was.

At that point you are paying a monthly fee to have an argument you could have had for free on a legal pad.

Twenty minutes. Before you spend anything.