An employee improvement suggestion system should connect an observed problem with a useful response. Collecting ideas is only the beginning. Employees need to know who will consider an idea, how a decision will be made and what happens if the suggestion cannot be tested.
The Lean Enterprise Institute emphasizes the purpose and management process behind a suggestion system. The operating structure below is an illustrative discussion aid. It is not an official LEI method, a compensation program or permission to change controlled work.
Ask for the problem as well as the idea
A short intake can ask: What happens in the work? Where and when does it happen? What have you observed? What change do you propose? Who else would be affected? Allow an employee to describe a problem even if they do not have a solution ready.
Do not require a financial savings estimate from someone who cannot support one. A relevant observation about confusing information or repeated waiting can be worth examining without a fabricated return. Keep sensitive personnel and customer details out of ordinary suggestion records.
Name a response owner and a feasible commitment
Choose an owner who can acknowledge the idea, clarify it and route it to the right decision-maker. Agree a response expectation that the organization can actually meet. Distinguish acknowledgement from approval: “We received it” is not “You may change the process.”
In a fictional office example, an employee proposes adding a receiving-owner field to an internal request. The supervisor checks whether the form owner, receiving team and information rules permit a small test. The employee remains involved rather than watching the suggestion disappear into an invisible queue.
Use a simple status record
Use statuses such as received, clarification needed, under review, approved for a bounded test, awaiting an authorized decision, completed or not proceeding. Add the responsible owner and the next action. Avoid a vague “pending” label that does not explain who is doing what.
A decision not to proceed should explain the reason and, where appropriate, whether another part of the idea can help. A clear response does not require accepting every suggestion. Do not publicly rank employees by the number of ideas submitted or imply that volume measures individual worth.
Define a safe test before changing anything
For an approved test, name the scope, permission, people affected, observation period and conditions for stopping or returning to the prior arrangement. Preserve required safety, quality, security and customer controls. Changes to regulated or controlled processes need their established approval procedures.
The A3 coaching questions can support a more complex investigation. A small suggestion need not acquire a large project template solely to look rigorous.
Close with evidence and recognition
Ask what happened during the test, what evidence supports the conclusion and what the affected people experienced. Decide whether to adopt, adapt, investigate further or stop. If the change is retained, arrange the required documentation, training and ownership so it does not depend on the original proposer’s memory.
Recognize the observation and contribution without claiming unverified savings. Follow authorized recognition and reward arrangements; this guide does not establish legal, intellectual-property or payment terms.
If suggestions repeatedly stall between collection and response, discuss the leadership routine with Shannon. The useful improvement may be protected response capacity and clear authority rather than a new ideas platform.
About this resource: Prepared with AI-assisted drafting. Examples and templates are illustrative, not reported client outcomes, a validated assessment or a substitute for required policies and qualified supervision.