Knowledge Base · Engagement
How do I turn employee ideas into real impact?
Ideas create impact when there is a system behind them: an easy way to submit, a named review process with a set rhythm, public acknowledgment of every idea, and credit when one is implemented. For a focused problem, run a short Kaizen event that maps the process, makes changes during the event, measures the result, and standardises what worked.
The book's main tool is the Idea Box, and its warning is blunt about what kills it.
- Choose an accessible format: a physical box in a high-traffic area, or a digital one such as a dedicated email address, a Teams or Slack channel, or a simple online form.
- Set a clear review process: name who reviews submissions, and how often. The book's example is a small committee reviewing every submission each Friday.
- Communicate throughout: publicly acknowledge every idea, explain plainly when one is not feasible, and celebrate and credit the person when one is implemented.
- Add light structure if it helps: a short form asking for the problem, the proposed solution, and the potential benefits.
For one defined problem, use a Kaizen event instead: a focused workshop, typically one to five days, with the people who do the work. Define the scope and goal first, map the current process, make changes during the event, measure the results, then standardise and share what worked.
The pattern in both routes is the same. An idea is received, tested, measured, and either adopted openly or answered honestly. That follow-through is what turns suggestions into further suggestions.
“Ideas that go into a black hole will kill your program faster than anything.”
Continuous Improvement in the Workplace, Ch. 10
Related questions
- How do I build a digital idea box that people actually use?
- How do I recognise and thank people for improvement ideas?
- What is a rapid improvement event (a kaizen event)?
Source: Continuous Improvement in the Workplace, Ch. 10 (Engaging Activities for CI).