Continuous improvement
Employee suggestion systems: idea to action
Build an employee suggestion process that reaches a decision and feedback. Use Toyota's documented history without assuming rewards cause results.
An employee suggestion system gives people a defined route to propose improvements, receive a response and see what happens to the idea. The system includes the work after submission: review, ownership, a decision and follow-up.
Toyota's historical record dates its Creative Idea Suggestion System committee to May 1951 and the first implemented ideas to June that year. The record also documents later changes, including a handbook distributed in 1964.
That history establishes a long-running programme. It does not isolate which reward or form caused an improvement in business performance.
Make the response route visible
| Stage | What the person proposing the idea should be able to see |
|---|---|
| Receipt | The idea has been recorded and has a reference |
| Review | An owner understands the problem and any requirement it affects |
| Next action | A check, a bounded trial, a decision or a clear reason for further work |
| Outcome | What happened and the evidence behind the decision |
| Follow-up | Who maintains an accepted change and whether the result held |
An ideas count reports submissions. It does not establish useful changes, realised savings or participation across the workforce.
Ask for the problem before polishing the proposal
Allow people to describe an observed difficulty in the work. A suggestion need not arrive with a complete business case, but the reviewer needs enough detail to locate the condition and speak with the people affected.
Keep potentially urgent safety or quality concerns on their required reporting and response route. They should not wait in a general improvement queue for a popularity vote.
The gemba-walk guide explains observing the work with the people who perform it. That can help develop a workable test from an initially incomplete suggestion.
Test and reply
Use a trial suited to the change and its consequences. Write the expected result, retain the relevant records and compare the outcome with the prediction. The PDCA Note provides the full worked approach.
Reply when the idea is declined as well as accepted. State the reason or the evidence still needed. An unresolved status with no owner leaves the employee unable to tell whether the proposal was considered.
NIST's learning-and-improvement guidance connects reviewing results with choosing improvement work. It does not establish a payment, suggestion quota or savings target that every organisation should adopt.
Track the work after adoption
Record who owns the changed method and when it will be checked. The daily-management guide connects issues and actions to a continuing review routine.
Review one existing suggestion from receipt to response. Identify its current owner and next action, then close any unexplained gap before requesting a larger volume of ideas.