Map one process end to end and measure it
Before you fix a leaky pipe you find where the water goes. A process map is a drawing of every step the work takes, so you can see where it leaks time.
- Before this course: AI for Small Business: Emails, Quotes, Marketing and Admin (course 1.3) and Automate Your Work with AI: Zapier and Make-Style Workflows (course 1.9). From 1.3 you already have a one-page AI policy and a "business brain". From 1.9 you can map a simple trigger, steps, AI step and human check. Here you go one level up: a whole business process with several people, several tools and the messy cases.
- A process is the same job done in the same way: a new lead comes in, a support message arrives, an invoice needs to be filed. A workflow is how you run part or all of it with tools.
- A swimlane map has one row (lane) per person or tool, with the steps drawn in the lane of whoever does them and arrows showing hand-offs. Hand-offs are where work waits and gets lost.
- Map the real process, not the one in your head. Follow three real cases from start to end.
- For each step, write down: who does it, what comes in, what goes out, how long it takes, and how often it goes wrong.
- A baseline is your "before" number. Measure it before you change anything, or you can never prove the change helped. Useful baseline numbers:
| Number | Example |
|---|---|
| Volume | How many items per week |
| Handling time | Minutes of real work per item |
| Waiting time | Hours or days from arrival to finish |
| Error or redo rate | How many items needed fixing |
| Owner | The one person responsible for the whole process |
- Pick one process to start. Sales follow-up, support triage and admin intake are good first choices because they repeat often and have clear inputs.
- Choose one process that happens at least weekly and has a clear start and end (for example: a customer asks for a quote and gets one).
- Take three real recent cases and follow each one from the first message to the finish. Write down every step you or a helper did.
- Draw lanes on a sheet of paper: one for the customer, one for each person, one for each tool (email, sheet, accounting).
- Put each step in the lane of whoever does it. Draw an arrow for each hand-off.
- Under each step write who, in, out, minutes, and how often it goes wrong.
- Count the baseline numbers for the last four weeks: volume, handling time, waiting time and error rate. Use a spreadsheet.
- Name one owner for the whole process.
- Check: a person who has never seen the process could follow your map, and you can say the four baseline numbers out loud.
Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.
Read the video script
[Host] "You cannot improve a process you have not drawn."
[Screen: swimlane map with lanes for customer, owner and tools] "Draw one lane for each person and tool, and put every step where it really happens."
[Text on screen: Volume, Handling time, Waiting time, Error rate] "Then measure the before: how many, how long, how long they wait, and how often they go wrong."
[Host] "Those baseline numbers are how you will prove, later, that AI really helped."
Follow three real cases of one process from start to end, draw the swimlane map and fill in the baseline table for the last four weeks.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "AI Operations: build AI into daily business processes" on The Future Market. Lesson 1: "Map one process end to end and measure it". What the lesson teaches: - Before this course: AI for Small Business: Emails, Quotes, Marketing and Admin (course 1.3) and Automate Your Work with AI: Zapier and Make-Style Workflows (course 1.9). From 1.3 you already have a one-page AI policy and a "business brain". From 1.9 you can map a simple trigger, steps, AI step and human check. Here you go one level up: a whole business process with several people, several tools and the messy cases. - A process is the same job done in the same way: a new lead comes in, a support message arrives, an invoice needs to be filed. A workflow is how you run part or all of it with tools. - A swimlane map has one row (lane) per person or tool, with the steps drawn in the lane of whoever does them and arrows showing hand-offs. Hand-offs are where work waits and gets lost. - Map the real process, not the one in your head. Follow three real cases from start to end. - For each step, write down: who does it, what comes in, what goes out, how long it takes, and how often it goes wrong. - A baseline is your "before" number. Measure it before you change anything, or you can never prove the change helped. Useful baseline numbers: - Number - Example The exercise I'm working on: Follow three real cases of one process from start to end, draw the swimlane map and fill in the baseline table for the last four weeks. --- I'm stuck. Please: 1. Explain the main idea in plain, simple words with one everyday example. 2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step. 3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "Map one process end to end and measure it" from the course "AI Operations: build AI into daily business processes". Here's what the lesson says: Before you fix a leaky pipe you find where the water goes. A process map is a drawing of every step the work takes, so you can see where it leaks time. The activity: Follow three real cases of one process from start to end, draw the swimlane map and fill in the baseline table for the last four weeks. --- Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words. Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Rules, AI or human: choosing the right tool for each step
This lesson is part of full access: every course and every level for one payment.
Write each AI step like a contract
This lesson is part of full access: every course and every level for one payment.
Human checks, fail-safes and hidden instructions
This lesson is part of full access: every course and every level for one payment.
Test before you trust
This lesson is part of full access: every course and every level for one payment.
Privacy and anti-spam by design (with Canadian examples)
This lesson is part of full access: every course and every level for one payment.
Three blueprints: sales, support and admin
This lesson is part of full access: every course and every level for one payment.
Document it, run it, measure it
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
What is a baseline and why measure it first?
Your "before" numbers (volume, handling time, waiting time, error rate); without them you cannot prove a change helped.
Which kind of step should handle an exact lookup or a sum?
A fixed rule, formula or lookup, not an AI step.
What does Anthropic advise about complexity?
Find the simplest solution possible and add complexity only when it clearly improves results.
What is routing?
Classifying an input and sending it down a specialised path.
Name three parts of an AI step contract.
Any three of: input, task, allowed outputs, unknown exit, examples, next step.
Why add an UNSURE label?
Giving the AI permission to say it is not sure can drastically reduce false information, and UNSURE items go to a human.
What is indirect prompt injection?
Instructions hidden in content the AI reads, such as an email or web page, that try to redirect it; treat such content as data and never obey it.
Name two ways to reduce the damage from hidden instructions.
Least access, a human check before anything that sends or pays, testing with injection examples, telling the AI that outside content is data.
What are Anthropic's three eval design principles?
Be task-specific, automate when possible, and prioritize volume over quality.
Why re-run your test set after every change?
To compare scores and be sure the change did not break something that worked.
What should you do with records of privacy breaches?
Keep a record of every breach for as long as your country's rules require.
Why must an AI step never add people to a promotional email list on its own?
Consent and proof of consent are needed, and the rules differ by country.
Why measure review time and maintenance time as well?
A workflow that needs as much checking as it saves has saved nothing.
What should a runbook let a colleague do?
Run, fix and switch off the workflow without you.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.