In the Plan phase a team pins down the exact nature of a performance gap, works out the mechanism behind it, and designs a targeted countermeasure. That means capturing current baseline figures, isolating the root cause, and naming the one indicator that will later prove whether the fix worked.
Hurrying this phase is the single most common reason improvement efforts stall. Without recorded starting figures and a quantified goal, the later Check phase has no benchmark and becomes guesswork.
Key Concept
Good planning converts a broad operational frustration into a quantified problem statement, a verified root cause, and a measurable target outcome.
Practical Example
A fulfilment centre finds that 14 percent of returns stem from transit damage, traces it to undersized air pillows on the fragile-items line, and predicts that corrugated inserts will cut damage returns below 3 percent.
Standard Procedure
- 1State the gap in specific, observable, quantifiable terms.
- 2Gather reliable baseline data across a representative timeframe.
- 3Investigate the workflow to isolate the primary root cause.
- 4Define the countermeasure together with the numeric target it must hit.
- 5Agree the data-collection protocol: what is tracked, by whom, how often.
Lesson Summary
- ✓Planning turns vague complaints into quantified problems backed by root-cause analysis.
- ✓Baseline data must be captured before any workflow change is introduced.
- ✓Expected gains are expressed as numeric targets so they can be verified objectively.