The best process is worthless if people do not use it. This plan covers the three things every rollout needs: the why, the how, and a new standardThe finalized way of working after rollout — documented, trained, and physically reinforced, so the improvement becomes routine. Click term for full definition. Watch the short video, then work with the toolkit PDF: it explains the method, shows a worked example and gives you a blank template to fill in.
Tool video
The short tool video will appear here.
Rollout Plan in short
- Plan the sequence. Which areas, in which order, by when. Start where support is strongest.
- Share the evidence. PilotA limited, controlled launch of a solution in a small part of the process, to validate real-world performance before full rollout. Click term for full definition data and testimonials, including what went wrong.
- Train at the GembaJapanese for "the actual place"; going to directly observe a process rather than relying on documents or memory. Click term for full definition. Pilot participants train their peers. Hands-on, not by PDF.
- Verify the skill. Trainers observe the new process and confirm it stuck.
- Make it the standard. Update SOPs, install visuals and Poka-YokeJapanese for "mistake-proofing"; designing a process so an error is either impossible to make or immediately obvious. Click term for full definition, retire the old tools.
Key points
- Show the why with pilot evidence.
- Train hands-on, peer to peer.
- Verify that it stuck.
- Retire the old way for good.