Why suggestion systems die and how they live: response time, visibility, thanks
In brief
Suggestion systems do not die from a lack of ideas but from a lack of answers. The three things that keep a system alive: a fast answer, a visible result and genuine thanks.
16 October 2026 · 4 min read
Sample company · demo data
My records
According to Toyota's own history records, its Creative Idea Suggestion System was set up in 1951 and still runs today. The secret of a suggestion system older than seventy years is not the design of the form but the discipline of the answer. In many companies the suggestion box fills up in its first year and gathers dust in its second. The difference lies not in the employees but in how the system answers.
How a system dies
No answer comes: the idea goes into a folder and nobody knows who is holding it. The employee does not write a second one.
Rejection without a reason: “not considered suitable” teaches the author nothing; it only hurts.
No visible result: even implemented ideas are not announced, so everyone assumes the system does not work.
Thanks is mistaken for money: when the reward budget runs out, so does the system.
Managers do not take part: if the team leader never opens a record, employees conclude it is not their job either.
How a system lives
First, response time. Evaluation may take a week, but the message “received, now at this step” should go the same day. A company that measures response time can see where the system slows down. Second, visibility: implemented suggestions are mentioned on the board, in meetings and at the start of shifts. Third, thanks. A cash reward is a policy and has its place, but the real return on every idea is showing that it was taken seriously.
The culture page of the UK Health and Safety Executive (HSE) lists management commitment, employee involvement and communication among the biggest influences on workplace culture. A suggestion system is the daily test of all three.
The manager's job
The manager's job is not to filter ideas but to clear the way for them. A good manager tells the author of a declined idea what would make it acceptable, follows the implementation of an accepted idea in their own calendar, and names the author in front of the team when the idea is implemented. The Lean Enterprise Institute lexicon defines Kaizen as small-step improvement involving everyone; “everyone” includes the manager.
What to measure
The number of records alone misleads; a campaign month brings a hundred suggestions, the next six months bring ten. Three measures together show the health of the system: the participation rate (people who opened a record divided by all people), the time to the first decision, and the share of records implemented. If participation falls, the system is losing trust; if decision time grows, there is a pile-up at one step; if the implemented share is low, accepted ideas are staying on paper. All three look at the process, not at the manager.
What to do in the first weeks
Give the fastest answer to the first ideas; the system's first impression lasts.
Open records yourself as a manager; wait for the team to say “this is for us”.
Describe the first implemented idea in the team meeting, with the author's name.
Give the reason for a declined idea face to face; the reason on the screen does not replace the conversation.
Keep the form short; a form longer than three steps makes people give up before writing.
Sample company · demo data
Congratulations on the board
How it is done in Gemy
Once a record is submitted it enters the flow the company has set up; each step can carry a duration in working days. When it expires, a reminder and a notification to the senior manager go out. A task nobody can be assigned to is reported to the type's managers after the period the company sets (three working days by default).
In My records the employee sees the record's step and who is holding it. A returned record sits at the top with its reason; the employee corrects and resubmits.
Reports track decision time as the median number of days from submission to the first decision.
Implemented work appears on the board; if the company has switched on Board applause, anyone can congratulate with one tap. Applause earns no points or reward and does not influence the committee's evaluation.
Committee rewards and participation points are configured and reported separately; points appear only if the company switches them on, and rewards are optional.
The system does not speed up the answer; it shows who is holding it. A person still gives the answer.
In short
A suggestion system is not a box, a form or a reward budget; it is a habit of answering. What kills a system is not a shortage of ideas but ideas left unanswered. Three things keep it alive: a first answer that goes out the same day, a result visible on the board and thanks spoken with the author's name. The manager's job is not to filter ideas but to make the answer regular and the implemented idea visible. With these three in place a suggestion system can last seventy years; without them it does not see its second year.
Every solved problem is a piece of knowledge; in most companies it leaves with the person who solved it. The four places where knowledge is lost, the view of ISO 30401 and ISO 9001, and five habits that make knowledge independent of people.
A supplier audit is a process, not a visit: which supplier, which question, which finding, which evidence. The audit principles of ISO 19011, the structure of the question list, finding classes and how the reply returns to the same record.
Document control ensures the right version of the right document is with the right person. What ISO 9001 asks for, document types and numbering, the approval chain, distribution and reading, withdrawing the old version and the five most common gaps.
9 November 2026 · 6 min
Cookies
Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.