Employee Suggestion Systems That Work: An Ideas Management Guide

By Mirko Peters · 2026-11-11

An employee suggestion system works when ideas get fast answers. Learn the principles, a six-step setup, triage rules and the metrics for ideas management.

An employee suggestion system works when every idea gets a fast answer, small ideas are fixed by the team that proposed them, and results are visible to everyone. This guide is for continuous improvement managers who run or want to restart an ideas management process in a plant. It explains what a suggestion system is, why most suggestion boxes fail, which principles make one work, and how to set it up in six steps. You also get a worked example and a list of common mistakes.

Key points

• An employee suggestion system works when every idea receives a fast answer, small ideas are fixed by the team itself and results are visible to all.
• A traditional suggestion box often fails because ideas wait for committees, so triage ideas into do now, assess and decline lanes.
• One published plant case set a goal of two ideas per employee per month and had supervisors and teams act on about half of the ideas at once.
• Recognition matters more than money: reward contribution to improvement, and make the person who had the idea part of the fix.
• Track participation, time to first answer and implementation rate, because they show whether staff trust the system.

What is an employee suggestion system?

An employee suggestion system is a structured way for employees to submit ideas for improving their work, with a defined route for review, decision, action and feedback. The channel can be a board with cards, a paper form, an app or a mix. In German-speaking companies a similar scheme is often called the betriebliches Vorschlagswesen. In lean organizations the same idea appears as kaizen suggestions, small improvements proposed and often made by the people who do the work.

The difference between a box and a system is the route. A box collects. A system answers.

Ideas management is the wider discipline. It covers how ideas are collected, sorted, decided, carried out and reported. The continuous improvement of a plant depends on this flow, because most small improvements start as an idea from someone at the workplace.

Why does it matter for the plant?

A working employee suggestion program does more than collect savings. It helps to foster employee engagement, because people see that their feedback changes their own workplace. It gives structure to employee participation in the daily workflow. And it gives managers a stream of facts about problems they would not see otherwise. To evaluate each suggestion on the same simple criteria (effect, effort, risk) keeps decisions fair. Over time the organizational habit of listening becomes part of how the plant is managed, and the data from the board can show where the same problem returns.

Why do many suggestion boxes fail?

Most failures have the same cause: ideas go in and nothing comes out. The typical reasons:

• Slow answers. Ideas wait for a committee or for a monthly meeting. The employee forgets the idea, or concludes that nobody cares.
• Every idea is treated as big. A small fix, such as moving a tool holder, needs the same approval as a major investment.
• Rewards focus on large savings. Staff with small ideas get nothing, so they stop proposing.
• No feedback. People never learn why an idea was declined.
• Managers own the problems. Employees are asked for ideas but never given the authority to act.

Employees feel heard when they get an answer within days, and they stop proposing when the answer takes months. That is the central lesson of every working system.

Which principles make a suggestion system work?

A Quality Digest interview by Norman Bodek describes the program at one plant, Technicolor's site in Livonia, Michigan, which was emulating the Toyota Production System. The numbers are the company's own report, not a multi-company study, but the principles are useful. Read the full Quality Digest article.

The principles it lists:

1. Ask employees what would make their own jobs easier. This is a better prompt than "give us ideas".
2. Let the person with the idea carry it out. If the idea goes beyond their scope, add them to the team that implements it.
3. Act quickly. The plant reports that at least half of the suggestions were implemented within 48 hours.
4. Involve everyone, including senior management. The plant set a goal of at least two ideas per employee per month.
5. Track results and post them publicly.
6. Have managers walk the floor and capture ideas, giving credit to the employee.
7. Empower teams, so that managers are not the only problem solvers. The article says supervisors, employees and work groups implemented 50 to 60 percent of the suggestions immediately.

The Lean Enterprise Institute adds a point about recognition. In its article on respect for people, it notes that lean programs highlight a "suggestion of the month" rather than an "employee of the month".

How do you set up the process in six steps?

1. Choose a visible channel. Use an idea board next to the production area, with cards and a pen. Add a digital option later if needed. Make submission take less than one minute.
2. Define three lanes. Lane A: "do now", small ideas the team can implement within its own area. Lane B: "assess", ideas that need a decision, money or another department. Lane C: "decline", ideas that do not fit, with a reason.
3. Set a response time. Promise a first answer within a few working days, and measure it. Aim for a fast answer, for example 48 hours for triage.
4. Name an owner. Every suggestion in lane B has one owner and a due date. The person who proposed the idea joins the work.
5. Close the loop. Tell the submitter what happened, and thank them. If the idea was declined, explain why.
6. Publish results. Show open, done and declined suggestions on the board. A monthly summary at the team meeting is enough.

A gemba walk is a good moment to collect ideas. Gemba is the Japanese word for "the real place", the shop floor. Supervisors and managers who walk it can ask about problems and write down ideas on the spot.

How should you reward ideas?

Keep rewards modest and fair. Technicolor's program, as the article describes it, used a Bravo award, small thank-you tokens from supervisors and a bonus for suggestions with exceptional savings. Other plants use only recognition. Whichever way you choose, avoid a system where the biggest savings take all the attention. The small ideas are the base of the continuous flow, and they build the habit.

If you pay for ideas, check local labor rules and any works council agreements before you start, and write the rules down.

Example: sizing the workload

This example uses assumed numbers.

A plant has 150 employees. The goal is one idea per employee per month.

• Suggestions per month: 150 × 1 = 150.
• Lane A, "do now" (60%): 150 × 0.6 = 90, handled by the teams without review.
• Lane B, "assess" (30%): 150 × 0.3 = 45.
• Lane C, "decline" (10%): 150 × 0.1 = 15, each with a short explanation.

Suppose each suggestion in lane B and C takes 45 minutes of the supervisor's time: (45 + 15) × 0.75 h = 45 hours per month. With 6 supervisors, that is 7.5 hours each per month.

If every suggestion went through assessment, the load would be 150 × 0.75 = 112.5 hours per month. The triage cuts it by more than half. The numbers are only a planning aid, so replace them with your own data.

How do you measure whether it works?

Use a few simple indicators, shown on the board:

• Participation: the share of employees who submitted or carried out at least one idea.
• Suggestions per employee: the average per period.
• Time to first answer: days from submission to a decision on the lane.
• Implementation rate: the share of ideas completed.
• Effect: a before and after figure for time, quality, safety or cost, measured from a baseline.

Savings matter, but they come later. Early on, participation and time to first answer show whether people trust the system. Check them every month.

Common mistakes

• Running it as a campaign. A launch event without a weekly routine fades.
• Sending every idea to a committee. Lane A must stay free of approvals.
• Ignoring declined ideas. An unexplained "no" does more damage than a slow "yes".
• Paying only for big savings. Small ideas stop.
• Making supervisors the bottleneck. Give them time in the calendar, or the queue will grow.
• Collecting ideas without a baseline. Without a before number, no effect can be shown.

How software can help

A board is enough to start. Software helps once the number of ideas grows: it can capture ideas from a phone, route them to the right owner, send reminders when a due date passes and show the status of every idea to all employees. Reports can also show participation by team and the time to first answer. Choose software only after your lanes and response times work on paper, and make sure submitting an idea remains quick for people without a desk.

Next step

This month, set up an idea board in one area with the three lanes and a 48-hour triage promise. Then review participation and time to first answer after four weeks. That is the simplest way to see whether your employee suggestion system works.