Measure the Before
Record how long the workflow takes today so you can prove what your automation changes.
Objective
By the end of this lesson, you have a baseline: a written record of how long the workflow takes and how often it goes wrong today.
No baseline, no proof
At the end of this course, you will say, "My automation saved this many hours a week." Someone will ask, "How do you know?" Your baseline is the answer.
A baseline is a measurement taken before you change anything. Without it, any claim about time saved is a guess.
What to measure
Pick three to five numbers. Keep it simple.
| Measure | How to get it | Example: taquería catering |
|---|---|---|
| Minutes per item | Time 5 to 10 real runs, take the average | 15 minutes per request |
| Items per week | Count from the inbox, notebook, or sheet | 12 requests |
| Response time | Time from request to first reply | About 20 hours |
| Error or miss rate | Count missed or wrong items out of the total | 2 of 12 missed |
| Handoffs | Count from your map | 4 |
How to time it fairly
- Time real work, not a demo.
- Time at least five runs. One run can be unusual.
- Include the hidden steps, like looking things up.
- Write down the date and who did the work.
- Do not rush the worker to make the numbers look bad. Honest numbers protect your credibility.
Try the baseline calculator
Change the numbers in the code to match your partner's workflow. Then press run and read the console.
Baseline calculator
Replace the sample timings with your own. The calculator finds the average and the weekly hours. Keyboard users: press Esc, then Tab, to leave the editor.
Save your results in a sheet named "Baseline" with the date. You will compare against it in Module 7.
Quiz: Module 2 check: map and measure
Go deeper: AI, Minus the Hype: A Practical Guide to Solving Real Business Problems by Dom Davis, Temerarii Media. It explains why you start with a bottleneck and a metric, not a tool.