Employee suggestion program best practices that keep people submitting

Most lists of employee suggestion program best practices start with the box on the wall, but the programs that last start somewhere else: with a clear goal, a named sponsor and a promise that every idea gets an answer. This guide covers the practices that separate a program people keep using from one that goes quiet after the launch email, from how you frame the question to what you measure at the end of each quarter.

It is written for the people who usually own the program: innovation leads, HR and people teams, operations managers and the executive who agreed to sponsor it. None of it requires a large budget. Almost all of it requires consistency, because employees judge the program by what happens to the second and third idea they submit, not by the launch.

Start with goals, not with a box

A suggestion program without a stated goal becomes a complaints channel with a nicer name. Before you invite a single idea, write down what the program is for. Two or three goals is enough, and they should connect to things leadership already cares about.

• Operational goals, such as reducing rework, shortening cycle times or cutting avoidable costs in a specific process.
• Customer goals, such as fewer support tickets, faster onboarding or higher renewal rates.
• Growth goals, such as new services for existing customers or better ways to reach a segment you already serve.
• Culture goals, such as giving frontline staff a real route to decision makers and showing that their knowledge counts.

The goals do two jobs. They tell employees what kind of idea is welcome, and they give reviewers a fair basis for saying no. An idea that is clever but serves none of the goals can be thanked and parked with a reason, instead of vanishing into a backlog. If you have not defined how ideas will be judged yet, our guide to idea evaluation criteria is a good place to start.

Run challenges instead of an open box

The open box, physical or digital, asks employees to think of anything, anytime. In practice that produces a thin stream of loosely related suggestions, many of them about parking, coffee or the air conditioning. A challenge asks a specific question for a limited time: "How could we cut customer onboarding time in half?" or "Where do we lose the most hours to manual data entry?"

Challenges work better for three reasons. A concrete question is easier to answer than a blank page. A deadline creates a reason to contribute now rather than someday. And a single topic lets a small review team compare ideas against each other instead of weighing a safety fix against a marketing slogan. You can still keep a general channel open for anything urgent, but make challenges the main event. For a step by step walkthrough, see how to run an idea challenge.

Writing a good challenge question

• Tie it to one of the program goals and say which one.
• Make it narrow enough that a person in the affected team can answer from experience.
• Avoid hiding the answer in the question. "How could we automate invoicing?" presumes automation. "How could we get invoices out two days faster?" leaves room.
• State the window, usually two to four weeks, and the date by which decisions will be shared.

Answer every author quickly

Silence is the most common reason suggestion programs die. An employee submits an idea, hears nothing for two months, and concludes the program is decoration. They do not submit again, and they tell colleagues not to bother. The detailed failure pattern is covered in why employee suggestion programs fail, and the fix is simple to describe and hard to sustain: every idea gets a human response within a fixed window.

Set a service level you can actually keep. An acknowledgement within a few working days and a first decision within a few weeks is realistic for most organizations. The first decision does not have to be final. "Shortlisted for review in the next cycle" or "not moving forward because it overlaps with a project already under way" are both answers. "Under consideration" for three months is not.

Make the response specific. A short note that shows the reviewer read the idea, names the reason for the decision and, if the answer is no, says what would change it, keeps people engaged even when their idea is declined.

Publish the criteria before ideas arrive

Employees accept a no much more easily when they knew the rules in advance. Publish how ideas will be judged at the start of every challenge. A short list works: expected impact on the stated goal, cost and effort to implement, risk, and fit with company strategy. If some criteria matter more than others, say so and show the weights.

Visible criteria also discipline the reviewers. It becomes harder to reject an idea because the reviewer dislikes the author or to approve one because it came from a senior manager. If the criteria are weighted, write a short rationale for each score so the decision can be explained later. The mechanics of building a fair scorecard are covered in how to score ideas against strategy.

Recognition and rewards without inflated bonuses

Many programs assume money is the main motivator and attach a cash award or a percentage of savings to every implemented idea. That can work in narrow cases, but it creates problems. People hold back half formed ideas to avoid sharing credit. Arguments start about how savings were calculated. Teams compete instead of building on each other's suggestions. And when the budget runs out, participation often collapses.

Recognition usually does more for less. Consider these options:

• Name the author when an idea is approved and again when it is implemented, in a channel the whole company reads.
• Invite the author to join the team that implements the idea, if they want to.
• Have the executive sponsor thank contributors directly at a quarterly review.
• Offer small, consistent rewards for implemented ideas rather than rare large ones.
• Recognize good challenge participation, not only winners, so that people who build on others' ideas get credit too.

Whatever you choose, keep it predictable. A reward system that changes every quarter signals that the program itself is unstable.

Secure a sponsor on the leadership team

A suggestion program owned only by HR or a single innovation manager tends to stall at the point where an approved idea needs budget or cross team time. A sponsor on the leadership team solves that. Their job is not to review every idea. It is to protect the program's time, unblock approved ideas, and show up visibly when results are shared.

A good sponsor does four things. They help choose challenge questions that matter to the business. They commit in advance to a decision meeting at the end of each cycle. They make sure approved ideas get an owner and resources. And they report outcomes upward, which keeps the program on the leadership agenda when priorities shift.

Work in a quarterly cycle

A predictable rhythm is easier to run and easier to trust than an always on program. A quarterly cycle fits most organizations and aligns with planning and reporting.

Keep a record of every decision and the reason behind it. When someone asks in six months why an idea was rejected, you should be able to answer in one sentence. A clear pipeline of stages, from submitted through in review, shortlisted, approved, in progress and implemented or rejected, makes that easy. The broader structure is explained in our guide to the idea management process.

What to measure

Measure the program by what it produces and how people experience it, not by the raw number of submissions. A flood of low quality ideas is not success, and a small challenge that yields one implemented process change can be.

• Participation, meaning the share of eligible employees who submitted or voted at least once in the cycle, broken down by team.
• Response time, meaning median days from submission to first human response and to first decision.
• Conversion, meaning the share of ideas that reach shortlisted, approved and implemented stages.
• Implementation lag, meaning time from approval to the idea actually running.
• Outcomes, meaning the measured effect of implemented ideas on the goal they were meant to serve, using the success measure defined when the idea was approved.
• Repeat contributors, meaning how many authors submit again in the next cycle, which is the clearest signal that people trust the program.

Report these to the sponsor every quarter. If response times grow or repeat contribution falls, fix the process before launching the next challenge.

Where software helps

A spreadsheet and a shared inbox can run a small pilot. Past that point, the administrative load, from chasing duplicates to writing up every decision, is what usually breaks the response promise. Brainstormer is built for this job: you run challenges in a company workspace, employees submit and vote, and AI expands each idea into problem, solution, first step and success measure, scores it against your weighted strategic goals with a written rationale, and merges duplicates so reviewers see one clean list. The decision pipeline keeps the audit trail, and a board report per challenge gives the sponsor the ranking and themes in one page. You can see how it fits a suggestion program on the employee suggestion program page.

Tools do not replace the practices above. They make it realistic to keep the promises: every idea answered, every decision explained, every cycle closed on time.