Suggestion Scheme

A warehouse worker knows that moving a label printer could reduce walking and errors, but without a route to raise the idea the team may keep an inefficient process. A suggestion scheme can help test it.

The Lean Enterprise Institute discusses practical ways to help workers contribute improvement ideas, emphasising engagement with real work rather than treating submissions as a contest of cleverness. Lean guidance also warns that poorly handled suggestion systems can lose trust, and asking for ideas and never responding is worse than a small honest process.

Define the scope (are ideas about work methods, customer experience, safety or new products welcome?) and tell people where urgent hazards must go instead of waiting for a monthly panel. Make submission easy, since a short form, team discussion or supervisor note can work while a complex portal may exclude field staff, and ask for the problem, not only a solution, because workers may see a pain point without knowing the best fix.

Assign a reviewer, since someone must acknowledge each idea, route it to the right owner and report a decision, and anonymous submissions need a way to share the outcome broadly. An illustrative response rate is suggestions receiving a documented answer within the stated period divided by suggestions due, so if 45 of 50 receive one that is 90%, which does not prove the responses were useful.

Set a realistic response time, as a simple housekeeping idea can be tested quickly while a software change may need budget and security review, and give interim updates on longer work. Use fair criteria, because impact, feasibility, safety and cost can guide review and a manager's personal preference should not be the whole decision.

Include the proposer in testing, since they know the work and can spot a new problem created by the proposed fix, and do not transfer the idea to a distant committee without feedback. Record decisions as accepted, testing, deferred or declined, explaining why, especially when a suggested fix cannot be used, and treat failed tests as learning by explaining what was learned rather than labelling the proposer wrong.

Recognise contributions appropriately, since thanks, time to test or a reward may be valuable, and any cash or intellectual-property terms should be stated before promising a share of savings. Do not reward only large cost savings, because a small safety change or clearer customer message may be valuable but hard to price, and avoid competition that suppresses collaboration, since if only one person gets credit workers may stop building on each other's ideas and team recognition can fit shared improvements.

Protect against retaliation, because suggestions may expose a poor process or management choice and workers need to be able to speak without punishment, and separate grievance channels, since a harassment or pay complaint should follow a protected route, not a public improvement board, with clear signposts. Check for duplicate themes, since ten suggestions about the same broken tool may indicate urgency, and combine work without erasing individual contributors.

Measure implementation, because counting submissions can reward volume and noise, so track useful tests, changes and whether the problem actually improved, and review barriers, since if one location rarely submits ideas, ask whether staff lack time, language support or trust. Give managers capacity, close the loop publicly where appropriate with personal details protected, and keep ownership after rollout with a process owner and updated standard work, because otherwise the improvement fades when the proposer leaves; for owners, a suggestion scheme creates a path from firsthand knowledge to tested change, and workers judge it by the response they receive, not the number of posters inviting ideas.