A process runs.
What is the smallest part of it worth automating?
The problem
Automation projects rarely fail on the technology. They fail because the scope is too wide, and because nobody separated legal judgement from what is merely repetitive.
You describe a real process, break it apart, isolate one single step, build it, hunt for what breaks it and measure what it saves.
A process that comes back every week, the documents it produces, and a sense of the volume involved.
The people who actually carry out the task, and whoever can decide to change the process.
The protocol
The real process
You describe the process as it actually runs, not as it is supposed to run.
The split
You separate legal judgement from the repetitive part. The first stays human, and the rest of the day leaves it alone.
Cutting down
You cut the scope down to one single step that stands on its own. This is the hardest hour of the day.
Building
You build it, in your environment, with what is already there.
Edge cases
You hunt for what breaks it: the exception, the badly named document, the missing approval, the rare case that happens anyway.
Measurement
You count the time before and after, on a real volume. Without volume there is no saving.
Out of scope
You write down what you are not automating, and why. That page is what protects the object.
What you leave with
- An automation running on one real step.
- The rule for cutting scope, reusable on the next process.
- A before-and-after measurement on a real volume.
- A written list of what stays human.
- A fully automated process.
- A move into production.
- An IT integration project.
The details
- Format
- In-house on your process, or open on an Academy process.
- Length
- One day.
- Group
- 4 to 10 people.
- Prerequisites
- You know the process being worked on. No development skill required.
- Environment
- The automation tools already sitting in your Microsoft 365 or Google Workspace. We introduce no additional software.
- Afterwards
- A one-hour review, thirty days later.
Price
- The process chosen, and its scope.
- The number of people.
- Preparing the process and the test cases.
- The technical environment to prepare.
The open-session price is the same for everyone in a given edition. In-house sessions are quoted after the scoping call, in writing.
Interested in this workshop?
On your process, with the people who carry it out. One hour to pick it together.
On an Academy process, signing up on your own. We let you know when the next edition opens.