Consider a support specialist who handles the same customer complaint every week. They suggested changing the process months ago and never received a response. The complaint keeps coming; the suggestions have stopped. A manager might see a lack of initiative. The history of that unanswered idea deserves a closer look.
Employees can have useful observations and good reasons to keep them to themselves. Restoring employee voice means deciding who reviews suggestions, how decisions get made, and what the contributor hears next. Launch an idea campaign when you have the capacity to handle what it brings in.
Employee voice and employee silence
Employee voice is employees' ability to express views, ideas, and concerns and influence decisions about their work. CIPD's guidance connects effective two-way communication with managers listening and acting on feedback.
Employee silence occurs when someone has something relevant to say and withholds it. CIPD reports that a quarter of employees in its research reported high levels of silence. That finding doesn't establish the rate in your company. It does explain why an empty suggestion channel tells you little about whether work is going well.
Voice also differs from engagement. A committed employee may stay quiet about a failure because they fear damaging a relationship with their manager. Submission volume won't tell you which explanation applies. Our guide to employee engagement metrics explains how to compare workplace indicators with what employees say.
7 reasons employees stop sharing ideas
1. Earlier suggestions went unanswered
After several submissions without a response, an employee has little reason to spend time on another. Their idea may have been discussed, rejected, or held for the next budget cycle. None of that is visible to its author.
Give someone responsibility for a substantive first response: a decision, a request for clarification, or an explanation of the next step and its timing. An automated receipt confirms delivery. It leaves the review question open. A clear rejection can bring the conversation to a useful end; indefinite waiting cannot.
2. Speaking up feels risky
Reporting a problem can mean questioning a decision made by the person who controls your performance review or promotion. An invitation to be candid carries little weight if the next uncomfortable observation gets mocked in a meeting.
Managers need to make the conversation possible: ask about the facts, acknowledge the concern, and discuss disagreement without punishing good-faith input. Provide appropriate confidential routes for sensitive issues. Anonymous feedback may remove some barriers, but employees will also judge how the organization uses what it receives.
3. Improvement is treated as someone else's responsibility
A warehouse employee sees an unnecessary handoff, but another department owns the procedure. They may assume they shouldn't interfere. Explicitly welcome observations across functions and give a coordinator responsibility for finding the relevant process owner. Reporting a delay shouldn't require knowing the entire management structure.
4. The submission form demands a business case
Cost estimates and implementation plans belong in an investment review. For an initial observation, ask what is happening, where, and who is affected. Make a proposed solution optional. Bring in financial or technical detail when the review needs it; otherwise, the process selects for willingness to complete paperwork.
5. The manager agrees but can't move the proposal forward
A manager may support an idea while lacking the budget or authority to change a neighboring process. Emails circulate between departments, and the employee experiences another silence.
Distinguish responsibility for responding from authority to decide. A coordinator needs a route to the process owner and a way to escalate disputed ownership. Local improvements can be reviewed locally; changes affecting several departments need a joint decision. Make time for reviewing submissions in the responsible people's workload.
6. Something changed, but nobody told the contributor
An improved approval process may already be running while the employee who suggested it still believes they were ignored. Tell them what changed, who is checking the result, and what remains unresolved. A wider update can connect the original issue with the action taken. Agree on public attribution with the contributor.
7. An idea becomes an extra job
If every observation earns the response “then you fix it,” silence becomes understandable. Recognizing a problem doesn't establish that its author has the capacity, resources, or authority to solve it. Discuss their involvement separately, agree on workload, and appoint an implementation owner. Identifying the obstacle is a contribution even when another team develops the solution.
A fresh idea contest can simply add to the unanswered queue. In their 2025 study of voice implementation, Ann E. Schlotzhauer and Mark G. Ehrhart distinguished efforts to enact suggestions from appreciation and endorsement. Their implementation measure improved prediction of future voice behavior beyond those other measures. This supports examining follow-through after a response; it doesn't imply that every idea should be implemented.
Employee ideas and workplace problems need different responses
“We could introduce a shared onboarding checklist” proposes a change. “New hires wait for access because the request never reaches the right department” reports an obstacle. The first needs an assessment of a possible solution. The second calls for checking where the request gets lost and who owns the handoff.
Accept both. Requiring a solution with every problem report will hide some useful information: an employee can accurately describe a failure without knowing how to fix it. Distinguish these contributions in the submission process and initial review.
Repeated reports from several departments can justify investigating a shared process. First check whether they describe separate incidents or the same event. Compare dates and circumstances, then talk to the people involved. For delays at functional boundaries, see our guide to organizational silos.
Build an employee suggestion workflow from submission to outcome
Start with an accessible channel and someone responsible for moving each submission forward. The example below is a recommended operating process to adapt to your organization. Agree separately on the statuses, deadlines, and automation available in your chosen tools.
| Stage | Responsible role | Required result |
|---|---|---|
| Capture | Employee and coordinator | A short description of the idea or problem with context |
| Route | Program coordinator | A review owner and first-response deadline |
| Evaluate | Process owner, with specialists as needed | Checked circumstances, costs, and possible actions |
| Decide | Manager with the necessary authority | A test, implementation, clarification, deferral, or reasoned rejection |
| Act and verify | Assigned implementation owner | A completed change and evidence about whether it helped |
| Respond | Coordinator and process owner | The contributor knows the outcome; open issues remain visible |
A deferred idea needs a review date or a condition for reconsideration. Without one, the contributor is still waiting indefinitely. A rejection needs an understandable reason: perhaps the cost exceeds the likely benefit, or another solution to the same problem is already being tested.
Check the outcome of approved work too. In the illustrative access example, updating an instruction doesn't establish that waiting time fell. Review subsequent requests and ask new hires whether they receive access when they need it.
A 30-day plan to test the process
Choose one team or process where reviewers have the capacity to respond and test changes. Set a response commitment they can realistically meet.
- Week 1. Review a sample of earlier suggestions. Find where work stopped: routing, decision, or feedback to the author. Agree on pilot scope and responsibilities.
- Week 2. Open a simple channel for ideas and problems. Explain who sees submissions, when contributors can expect a response, and where sensitive reports belong.
- Week 3. Review incoming observations. Choose a feasible change to test and provide substantive responses to the other submissions.
- Week 4. Check deadlines, decisions, and test results. Ask participants whether the process made sense, share unresolved issues, and decide what to improve before expanding.
A month can test accessibility and handling discipline. Assessing a sustained change in trust or psychological safety requires longer observation and separate employee feedback.
Six employee voice metrics worth tracking
Define the period, eligible population, and deadlines before calculating rates. A substantive response means a decision, an explained next step, or a clarification request. Exclude automated delivery confirmations.
| Metric | Calculation | Question to investigate |
|---|---|---|
| Participation rate | Unique contributors / eligible employees × 100 | Can the intended employees access and use the channel? |
| On-time response rate | Submissions substantively answered by deadline / submissions with response deadlines in the period × 100 | Do employees receive the promised response? |
| First-response time | Median elapsed time from submission to substantive response | How quickly does the process respond? Show unanswered submissions and their age separately. |
| On-time decision rate | Submissions decided by deadline / submissions with decision deadlines in the period × 100 | Does review reach a decision? |
| On-time implementation rate | Approved ideas implemented by deadline / approved ideas with implementation deadlines in the period × 100 | Are commitments being delivered? |
| Problem recurrence | Verified repeat incidents over comparable periods | Does the cause persist? Compare incidents per request or operation if workload changes. |
Include older submissions when their agreed deadline falls in the current period. Keep previously overdue items visible as a separate backlog. If a denominator is zero, report the rate as unavailable. There is no universal quota of ideas per employee.
A rise in problem reports could reflect worsening conditions or greater trust in the channel. Low participation could mean that team meetings already resolve most issues. Ask employees about the experience before judging culture from the counts.
How HiveHR makes employee ideas and problems visible
HiveHR's “Million-dollar idea” activity lets employees propose improvements. “Highlight a problem” provides a separate way to report difficulties and bottlenecks. The distinction helps a reviewer decide whether to assess a proposed change or first investigate an existing obstacle.
“Say thanks” adds context about colleagues' help. In the illustrative onboarding situation, one record might describe a checklist idea, another an access delay, and a thank-you message the specialist who helped trace the handoff. These are different pieces of evidence. Check their relationship with the people involved before drawing conclusions about the process or anyone's skills.
Recorded activity helps leaders investigate recurring themes and working relationships. It covers what employees actually enter in the system. An absence of records doesn't establish that problems are absent; recognition alone doesn't confirm that a failure was fixed. The organization and pilot team still need to agree on review responsibilities, decision authority, and outcome checks.
Avoid tying recognition solely to idea counts or votes. A useful contribution can be a precise problem description, a checked assumption, or help with a test. Our guide to launching an employee recognition program discusses fair participation and acknowledgment.
Before launch, explain who can see records and how they will be used. Reports of harassment, misconduct, or serious safety threats need appropriate dedicated routes and escalation procedures. A general improvement channel cannot replace those. See our guide to ONA privacy and ethics for principles of responsible data use.
Frequently asked questions
Why don't employees speak up when asked for ideas?
Possible reasons include unanswered suggestions, fear of consequences, difficult submission processes, and extra work attached to initiative. Trace a few earlier proposals and ask employees about their experience. An invitation alone won't remove those barriers.
What is an employee suggestion system?
It is a process for collecting, evaluating, and responding to improvement proposals, with owners, deadlines, and feedback. For approved ideas, it also includes implementation and checking the outcome.
Should employees report a problem without a solution?
Yes. Someone may know where a delay occurs without having the authority or expertise to redesign the process. Assign a reviewer to check the circumstances and involve the right specialists.
Do we need to implement every idea to build trust?
Decisions depend on usefulness, cost, risk, and priorities. Fair consideration means explaining a rejection or deferral, then delivering accepted commitments or openly revisiting them.
How do you measure whether employee voice is heard?
Compare response deadlines, decisions, and verified changes with participants' accounts. A high handling rate describes the process. Employees' sense of safety and influence needs separate investigation.
Test the path from employee idea to decision with HiveHR
Start with one team and a 30-day pilot. Agree on which ideas and problems to make visible and how your team will review the resulting signals.
Sources
- CIPD: Employee voice — guidance on voice, silence, and managers' responses.
- Schlotzhauer, A. E., & Ehrhart, M. G. (2025): From idea to action: Defining and measuring voice implementation. Journal of Occupational and Organizational Psychology. First published May 21, 2025.