Piloting and scaling solutions
A pilot is a controlled, limited-scope implementation of the proposed solution. It generates evidence that the solution works in the real production environment — beyond what DOE or confirmation runs alone can prove — before committing to a full, irreversible rollout.
Why pilot? What the pilot answers
DOE and confirmation runs operate under controlled conditions, often with close monitoring by the project team. A pilot tests:
- Operational feasibility: Can operators execute the new process reliably without the Black Belt watching?
- System interactions: Does the change affect adjacent processes, scheduling, or material flow in unexpected ways?
- Sustained performance: Does the improvement hold over multiple shifts, days, or batches?
- Implementation risks: What breaks when you change this in a real environment?
Designing a pilot: key decisions
| Decision | Guidance |
|---|---|
| Scope | One line, one shift, one product family — small enough to manage, large enough to be representative |
| Duration | Long enough to capture meaningful variation (shifts, days, raw material lots). Minimum one full production cycle. |
| Control group | Run the old process in parallel (another line or shift) so you have a direct comparison, not just a before/after time comparison |
| Success criteria | Defined before the pilot starts. What metric must improve by how much to declare success? |
| Failure criteria | Conditions that trigger stopping the pilot and reverting. Do not define these after you see the results. |
| Monitoring plan | Who collects data, how often, using what method — the same measurement system as the baseline |
Evaluating pilot results
After the pilot, the team performs a statistical comparison to baseline (or to the control group). A favorable-looking chart is not sufficient — the improvement must be statistically significant and large enough to matter in practice (meet the pre-defined success criteria).
Common pilot failure modes
- Hawthorne effect: Performance improves because people know they're being watched, not because the solution works. Counter: monitor the pilot passively where possible; extend the pilot duration until team behavior normalizes.
- Piloting the wrong scope: Pilot on the "best" line with the "best" operators. The solution fails everywhere else. Counter: pilot on a representative line.
- Declaring victory too early: Two good days of data. Extend the pilot long enough to cover typical variation sources (shift changes, material lot changes, maintenance windows).
- No rollback plan: The pilot degrades product quality and the team cannot quickly revert. Counter: document the rollback procedure before starting; retain the old SOP version.
Scaling to full rollout
After a successful pilot, the rollout plan must address:
- Training: All operators, supervisors, and QC staff trained before their area goes live. Training records completed and retained.
- SOP updates: Controlled document revision — new version issued, old version archived. In regulated industries, formal change control and deviation handling if applicable.
- Physical changes: Equipment adjustments, tooling changes, new fixtures — verified on each piece of equipment, not just the pilot equipment.
- Monitoring expansion: SPC charts or tracking systems deployed on all new production lines, not just the pilot line.
- Lessons learned: What surprised the team during the pilot? What will you do differently in the rollout?
Try 5 free CSSBB practice questions on piloting and scaling solutions. No account needed.
Take the free CSSBB diagnosticMore: DMAIC overview · Project charter · VOC & CTQ · SIPOC · MSA in DMAIC · Process capability · Data collection planning · Graphical analysis · Root cause analysis · Multi-vari analysis · Hypothesis testing · Regression · DOE · FMEA · Define tollgate · Change management · Financial benefits · Team dynamics · Improve tollgate · Piloting & scaling · Poka-yoke (BB) · Solution selection · Control plan · SPC in DMAIC · Sustaining gains
CSSBB Quest by Bizarre Act. Original study material; not affiliated with ASQ. CSSBB is a certification of ASQ. Terms · Privacy