Write the job down before you open the AI

Most people open the AI first and work out what they want as they go.

Type something. Get something back. Fix it. Type again. Forty minutes later you've got something close, and you've got no idea how to get it again next week.

I do it the other way round. I don't open the AI until I've written the job down.

Why paper first

If you can't explain how a job works, AI can't do it either. It'll guess. And every guess is something you'll have to fix.

Writing it down first forces you to work out the bits you do without thinking. The step you always skip. The check you do in your head. The thing that goes wrong every third time. Those are exactly the things AI needs to know.

This isn't a new idea. Surgeon Atul Gawande wrote The Checklist Manifesto about what happens when experts write down the steps they think they already know. A surgical checklist study he worked on, run in eight hospitals around the world and published in 2009, found deaths after surgery nearly halved once teams used a simple checklist. Experienced surgeons weren't missing steps because they didn't know them. They were missing them because they were busy.

You're busy too.

The Checklist Manifesto, Atul Gawande
Nearly half
fewer deaths after surgery once teams used a simple checklist
8
hospitals around the world in the 2009 study
Experienced surgeons missed steps because they were busy, not because they didn't know them.

The order I build in

Here's how I built an AI system recently for someone I work with. It's how I build all of them.

1. Write out how the job actually works.
The way it really happens, step by step, warts and all. I talk it through with the person who does it, because they know the bits nobody's written down.

2. Write down what they need at the end.
The finished thing. What it looks like, what's in it, who it goes to. If there's an example of a good one, I grab it.

3. Write the instructions for the AI.
Now I write it up as instructions. The job, what goes in, what comes out, the steps, the rules, what good looks like, what to do when something doesn't fit.

4. Test it myself until it's right.
I run it on real examples. Every time it gets something wrong, I change the instructions so it doesn't make the same mistake twice.

5. Set it up together.
Then I sit with the person who'll use it. They drive. I tell them what to put where. That way they know how it works and they're not scared of it.

6. Test it together on the real thing.
We run it on a real job, check what comes out, and fix anything that's off.

That's it. No code. Most of the work happens before the AI's even open.

“

Most of the work happens before the AI's even open.

What to write down

Use these questions:

  • What starts this job? (A day of the week, an email, a client booking?)

  • What information do you need before you start?

  • What are the steps, in order?

  • Where do you usually get stuck or make mistakes?

  • What does finished look like?

  • Who gets it at the end?

  • What should never happen?

Answer those and you've got 80% of your AI instructions written.

It's slower the first time

Yes. Writing it down takes an hour. Typing a prompt takes thirty seconds.

But you pay for those thirty seconds every single time you do the job. You pay in rewrites and checking and "that's not what I meant". The hour up front, you pay once.

It's one part of how I use AI across my businesses. The full picture is in How I actually use AI to run three businesses and a community.

Not sure which job to write down first?

Take my free quiz, Why isn't it getting done? It shows you which part of your back end you keep putting off. Start there.

Take the quiz

HI, I'M SAM

I've co-run a field service business for 22 years and served 12 years in the Navy. Now I help solopreneurs get the back-end stuff done, the money, systems, marketing and AI, so they get their weekend back.

NOT SURE WHAT'S SLIPPING?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore.

+123-456-7890000

Newsletter

Subscribe now to get daily updates.

Created with © systeme.io