Knowledge Base · Solutions
How do I run a small improvement experiment this week?
Pick one small, nagging frustration, ask why it happens until you have a plausible cause, then test one tiny change through a single PDCA cycle: state a one-sentence prediction, try the change for a day or two, check with the team whether it helped, and decide to keep it or try something else.
Both Chapter 4 and the book's starter kit point to the same small loop. The starter kit's Week 3 goal is to test a small change: start from a frustration already explored with the 5 Whys, think up one tiny change, and test that change as an experiment rather than launching a project.
- Plan: state a prediction in one sentence: if we change this, we expect that to follow.
- Do: try the change for a day.
- Check: did it work? What actually happened?
- Act: keep doing it, or try something else.
Chapter 4's version of the exercise uses the same shape on any small problem your team faces. Its example prediction is deliberately ordinary: moving the printer across the room should cut the time spent walking to and from it. Make the change, ask the team after a day or two whether it made a positive difference, then keep it or change it.
The book is explicit about the standard to hold yourself to here: perfection is not the aim. Practising the discipline of the cycle is. One small completed loop teaches more than a large plan that never leaves the page.
Related questions
- What is the PDCA cycle, and how do I run one?
- How do I run a 5 Whys analysis?
- What should my first 30/60/90 days of CI look like?
Source: Continuous Improvement in the Workplace, Ch. 4 (Solution Creation and Implementation) and the CI Starter Kit in the book's Appendix.