Measure before you change: the three numbers every process needs
Teams often start improving a process without knowing how it performs today. Months later, nobody can say whether it worked. Three simple numbers fix that.
1. Time
How long does one case take from start to finish, and how much of that is waiting? Time a handful of real cases rather than guessing.
2. Volume
How many times does the process run each week? A slow process that runs twice a week matters less than a small delay that runs a hundred times.
3. Errors
How often does something need to be fixed, redone or escalated? Rework is hidden time, and it is often the biggest gain.
How to start this week
- Pick one process.
- Record time, volume and errors for one week in a simple sheet.
- Change one thing, then measure again for a week.
That small habit turns opinions into evidence and makes every later improvement easier to justify.
Related reading and services
MethodA process improvement framework you can run in six weeksA six-stage process improvement framework for small teams: pick, measure, map, diagnose, change and hold. With the question and output for each stage.ChecklistsBusiness process audit checklist: 40 questions to ask before you change anythingA practical business process audit checklist covering ownership, triggers, handoffs, data, controls, performance and documentation. Use it before any improvement or automation project.ServiceProcess consultingFind out how work really flows, with the numbers to prove it.GuideHow to Identify Process Bottlenecks: 5 MethodsFive practical ways to find a process bottleneck: queue observation, timestamp sampling, work-in-progress counts, rework tracking and asking where people wait.
Want to fix a process like this?
Book a free process review. Bring one slow process and leave with three improvement ideas.
Book a free review
