1
Define the process scope and write a measurable objective
Name the specific process, identify its start and end points, and state the improvement target as a number β not a direction. Confirm who the process owner is before proceeding.
π‘ A well-formed objective follows this pattern: reduce [METRIC] from [X] to [Y] by [DATE]. If you cannot fill in all three variables, the scope is still too broad.
2
Map the current-state process by observing it, not describing it
Walk through the process with the people who actually do it. Record every step, every tool used, and every handoff point. Note where people deviate from the official procedure β those deviations are often where problems live.
π‘ Record at least three real instances of the process running rather than relying on one walk-through. Variation between instances is itself a finding.
3
Collect quantified baseline data
Pull at least 4 weeks of real performance data for the process KPIs you plan to improve. Calculate averages and note any significant outliers.
π‘ If data does not exist, spend one to two weeks collecting it before starting the analysis. Starting without a baseline makes it impossible to prove the improvement worked.
4
Conduct root-cause analysis using the 5 Whys
State the problem clearly, then ask 'why does this happen?' five times in sequence. Stop when you reach a cause you can actually control and change. Categorize the root cause as People, Process, Technology, or Environment.
π‘ Run the 5 Whys with the people doing the work, not just with managers. Front-line workers know the real causes; managers often know only the reported symptoms.
5
Complete the gap analysis with numbers
List each KPI where current performance falls short of target, state the current and target values, calculate the gap, and assign a priority based on the business impact of closing it.
π‘ Convert gaps to dollar impact where possible β even an estimate. A gap expressed as '$40,000 per year in rework cost' gets executive attention faster than '12% error rate.'
6
Write recommendations that address root causes, not symptoms
For each root cause, write one or more specific recommendations. Confirm each recommendation directly addresses a root cause identified in Step 4 β not just a symptom that appeared in the current-state map.
π‘ If a recommendation does not trace back to a root cause, remove it. It is likely a workaround that will be undone within months.
7
Assign every action to a named individual with a due date
Convert each recommendation into one or more concrete tasks. Assign each to a single named person β not a team or role β and set a specific calendar date.
π‘ Get verbal or written acknowledgment from each owner before publishing the plan. Owners who are surprised by their assignments miss deadlines at much higher rates.
8
Set interim checkpoints in the measurement framework
Define at least one checkpoint within the first two weeks of implementation to catch early deviations. Schedule a full post-implementation review 30β60 days after rollout against the original baseline.
π‘ Publish the measurement framework to the full team before rollout begins β visible accountability raises follow-through significantly.