Lesson 1: See the System (it is already there)

🎯 Overview

This lesson has one job. It shows you that your business already runs on systems. You do not need to invent anything. You need to see what is already there, and write it down.

Every repeated job in your business has a method today. A quote request arrives, and things happen in a certain order. An invoice goes out, and things happen in a certain order. The method exists. It just lives in someone's head, so nobody else can see it, check it, or improve it.

By the end of this lesson you will have one real job written down, step by step, as it actually happens.

📌 The rule of this lesson: you cannot improve a method you cannot see.

🧭 Context

A method in a head has three problems. Only one person can run it. Nobody can check it. And it changes without anyone noticing.

A method on paper fixes all three. Anyone can run it. Anyone can check it. And a change to the paper is visible, so people can agree to it.

Construction already knows this. A site diary records what happened. A work method statement records how a task is done. This lesson brings that same habit into the office.

<!-- image: The same quote-request job twice: on the left a cloud over one person's head with question marks; on the right the identical job as seven numbered steps on paper that anyone can follow -->

🔧 How it works: shadow one job

Pick one job that repeats every week. A good first pick: a quote request arrives by email. Now write down what actually happens, in order. Not what should happen. What does happen.

For a quote request, the real list often looks like this:

1. The email arrives in a shared inbox.
2. Someone notices it, today or in three days.
3. Someone decides if it is worth quoting. The rule for that decision lives in one person's head.
4. Someone digs out the last similar quote to copy prices from.
5. Someone writes the quote and sends it.
6. Someone remembers to follow up, or does not.
7. The result goes nowhere. Nobody records won or lost.

Write your own version. Be honest. The gaps and the "someone"s are the point. Every "someone" is a step with no owner. Every "or does not" is a step that fails quietly.

🧠 Why this works

Writing the job down does two things at once. First, it makes the method visible, so you can improve it in Lesson 3. Second, it shows you where the business depends on one person's memory. Those spots are where jobs get dropped when that person is sick, busy, or on holiday.

You are not judging anyone. The person who holds the method in their head is usually the hardest worker you have. The problem is the storage location, not the person.

🧩 How it fits

This written list is the raw material for the whole course. Lesson 2 asks where the information in your list lives. Lesson 3 turns the list into a proper method. Lesson 4 makes the method improve itself. The paid courses later hand that same method to an AI program. It all starts with this one honest page.

🛠️ Build it / try it

1. Pick one job that repeats weekly. Quote request, invoice run, or new-job setup all work.
2. Open a blank document, or use paper. Title it with the job name.
3. Write the steps in order, as they really happen. Ten steps or fewer.
4. Mark every step where the doer is "someone" rather than a named person.
5. Mark every step that sometimes gets skipped or forgotten.

✅ What good looks like

• One page, one job, steps in order.
• At least one honest gap is marked. If your page shows no gaps, it shows the brochure version, not the real one.
• A colleague reads the page and says "yes, that is what happens."

💡 Key takeaways

• Your business already runs on systems. Seeing them is step one.
• Write what actually happens, not what should happen.
• Every "someone" is a step with no owner. Every silent gap is a job waiting to be dropped.
• One honest page beats a folder of tidy fiction.

Next: Lesson 2, One Home for Everything (why copies of information start fights).