The owner of Horizonte wants the sales agent to handle billing too, doing the same thing the team does today. It looks like the safe path. It isn't: a process designed for people to pass paper from hand to hand, run by an agent, just delivers the same error faster. This lesson teaches you to look at each step and ask why it exists.
1Why speeding up the old process also speeds up the error
2The three origins of a step: real requirement, habit, and handoff
3The question that comes before any agent
4What you don't cut, even when it looks like bureaucracy
Objective: explain why automating a bad process delivers the error faster, and mark, in a process of your own, the steps that exist only out of habit.
01 · Four generations of process
Each generation changed what you do with the process after it is designed. Tap each step.
Before moving a process up a step, ask whether it should still exist this way.
Process generations in the AI Management Area (INEMA). They coexist in the same company: one process can be at step 1 and another at step 3.
02 · Why not speed it up
Four ideas. The examples are from Horizonte, a fictional study company.
1. The faster error
A process designed for people has steps that exist because people couldn't reach everything: one copies, another checks, a third carries the paper. Putting an agent to repeat that path keeps every step, just faster.
If the design had an error, the error gets faster too. And harder to see, because now nobody walks the whole path with their own eyes.
At HorizonteToday finance retypes each order into the ERP and only then finds out the customer has no CNPJ on file. With Hora retyping, the order without a CNPJ reaches finance sooner, already picked in the warehouse, and comes back the same way.
2. Three origins of a step
Every step was born for a reason. Real requirement: law, contract, customer, or a risk someone has already lived through. Habit: it's always been this way and nobody can say why. Handoff: it exists only to carry the work from one person to another.
Handoff is the most common habit and the easiest to spot: printing, forwarding, announcing that you're done, copying from one system to another.
At HorizonteIssuing the invoice is a real requirement. Copying the order from the app to the spreadsheet is habit: the spreadsheet existed before the app. Printing the order for the warehouse is a handoff.
3. The question that comes first
The question that changes the work is this: if I had people, agents, and automations available today, would this process still exist this way? It applies to the whole process and to each step.
For a single step, the practical version is: does this step need to exist if the three before it are done all at once, by the same person or the same agent? Many handoffs disappear on their own.
At HorizonteIf the order is born complete in the app, the warehouse sees it on screen, and finance receives it in the ERP, five steps no longer have a reason to exist: the spreadsheet, the paper, the WhatsApp notice, the email to finance, and the retyping.
4. What you don't cut
Habit sometimes hides a reason nobody wrote down. Before marking a step as habit, ask the person who does it: why does this exist? What has gone wrong when it wasn't done? If the answer is a real risk, the step is a requirement.
The steps of judgment, exception, oversight and strategy also stay. They change place and size, but they still belong to a person.
At HorizontePatrícia approves any order above R$ 5 mil before picking: that is a real requirement (a fictional company policy). Checking the price of every order, including the standard-price ones, is a habit born from a scare. The risk is real; the form is not.
03 · Template to copy: tagging sheet
One line per step, in the order it happens today. Paste it into a spreadsheet or a document. The tab next to it shows the Horizonte sheet.
Process tagging sheet
TAGGING SHEET · process: <from where to where> · owner: <name> · date: <mm/dd/yyyy>
Tags
X = real requirement (law, contract, customer, a risk someone has already lived through)
H = habit (it has always been this way; nobody can say why)
P = handoff (it only exists to carry the work from one person to another)
| # | Step (verb + object) | Who does it | Tag | Why it exists (answer from the person who does it) | If it disappeared, what would break? |
|---|---|---|---|---|---|
| 1 | <receive the order> | <name or role> | <X, H or P> | <...> | <...> |
| 2 | <...> | <...> | <...> | <...> | <...> |
COUNT: X = <n> · H = <n> · P = <n>
QUESTIONS I ASKED THE PEOPLE WHO DO IT: <names and date>
CLOSING QUESTION: if I had people, agents and automations today,
would this process exist this way? <yes or no, in two sentences>
Prompt · look for handoffs
You are a process analyst. Below is the list of steps of a process
in my company, in the order they happen, with who does each one.
Do not rewrite the process and do not decide anything. Just point out:
1. Steps that seem to exist only to pass the work from one person to
another (printing, forwarding, notifying, copying from one system to another).
2. Steps that repeat a check that was already done earlier.
3. For each step you point out, the question I should ask the person who
does it to find out whether there is a real reason.
Steps:
"""<paste the list>"""
Simulation: illustrative example
WhatsApp order → invoice · v1.0 · Horizonte Distribuidora, fictional study company
#
Step
Who
Tag
1
Reply to the customer on WhatsApp
Hora or Juliana
X
2
Build the order in the app
Hora
X
3
Copy the order into the sales spreadsheet
Juliana
H
4
Check the price and discount of every order
Patrícia
H
5
Approve any order above R$ 5 mil
Patrícia
X
6
Print the order and take it to the warehouse
Juliana
P
7
Check availability in the ERP
warehouse
X
8
Pick the items
warehouse
X
9
Tell Juliana the items were picked
warehouse
P
10
Send an email to finance
Juliana
P
11
Retype the order in the ERP
finance
P
12
Check the customer record and issue the invoice
finance
X
13
Send the invoice to the customer
Juliana
X
Count: X = 7 · H = 2 · P = 4. Step 4 was born on 10/14, after the improper discounts that week: the risk is real, but the form (checking every order) is habit.
Step written as a department ("finance") instead of verb + object ("retype the order in the ERP"). Without a verb, you can't ask why it exists.
Tag given without asking the person who does it. The "why it exists" column must hold the person's answer, not your guess.
Everything becomes habit. If you marked more H and P than X, double-check: invoices, value approvals and stock checks are usually real requirements.
Process with no ends. The first line is the trigger (what comes in); the last is the conclusion (what goes out and to whom).
04 · Practice
The Horizonte sheet to train your eye; the one for your own process for real.
1 · The Horizonte tags
15 min
Copy the 13 steps from the example tab without the "Tag" column and give each one an X, H or P, with one line of reasoning. Only then compare with the tab and note where you disagreed and why.
Done when: all 13 steps have a tag and a reason, you found at least 4 H or P steps, and you wrote the answer to the closing question in two sentences.
2 · The tags for your process
30 min
Pick one of your processes that repeats every week and involves more than one person. List the steps in today's order, with who does each one. Ask at least two people who run the process why the suspect steps exist, and fill in the sheet.
Done when: the sheet has 6 to 15 steps with a verb and who does them, at least 3 marked as habit (H or P) with the reason given by the person who does them, the names of the people you consulted, and the closing question answered.
4 questions. The explanation appears after your attempt.
Question 1 of 4
A company put an agent in charge of doing exactly the steps the team used to do, in the same order. The time dropped by half. What happened to the process?
Correct
Saving time is not redesigning. It is AI on top of the old process: a real gain, but the useless steps and the design errors are still there, now faster and less visible.
Not that one
Saving time is not redesigning. It is AI on top of the old process: a real gain, but the useless steps and the design errors are still there, now faster and less visible.Review: Why not speed it up
Question 2 of 4
At Horizonte, Juliana sends an email to finance with each picked order. What is the most likely tag for this step?
Correct
Finance needs the order; it doesn't need the email. If the order reached the ERP straight from the app, this step would lose its reason. Handoff is the most common habit and the easiest to find.
Not that one
Finance needs the order; it doesn't need the email. If the order reached the ERP straight from the app, this step would lose its reason. Handoff is the most common habit and the easiest to find.Review: Why not speed it up
Question 3 of 4
You suspect a check is only habit. What should you do before tagging it H?
Correct
Habit sometimes hides a risk nobody wrote down, and neither the time spent nor the manual tells you why the step exists. The answer from the person who does it decides whether it's a real requirement. And even when the risk is real, the form can be habit, like checking every one of Patrícia's orders.
Not that one
Habit sometimes hides a risk nobody wrote down, and neither the time spent nor the manual tells you why the step exists. The answer from the person who does it decides whether it's a real requirement. And even when the risk is real, the form can be habit, like checking every one of Patrícia's orders.Review: Why not speed it up
Question 4 of 4
Which of these steps still belongs to a person after the redesign?
Correct
Deciding outside the rule is judgment and exception: it stays with a person. Checking the registration is a rule (same information, same answer) and can become a system check; copying from one system to another is a handoff, a candidate to disappear.
Not that one
Deciding outside the rule is judgment and exception: it stays with a person. Checking the registration is a rule (same information, same answer) and can become a system check; copying from one system to another is a handoff, a candidate to disappear.Review: Why not speed it up
Quiz complete
You got {a} of {n} right. Get them all right and the lesson is marked as complete.
Choose an option. The explanation appears after you try.
06 · Summary
Speeding up is not redesigningThe agent inherits the design, mistakes included, just faster.
Three originsA real requirement stays. Habit and handoff are candidates to go.
The question that comes firstWith people, agents, and automations today, would this exist in this form?
Ask before you cutThe person who does it knows the risk the step hides. The answer goes on the sheet.