When an employee raises an improvement idea, thank them, understand the problem, agree on the next action and its owner, and tell them when they will hear back. Follow up with the decision or result, including when the answer is “not now.” A quick acknowledgment starts the conversation; a useful response shows what will happen next.
This applies whether the idea comes from a production operator, a nurse, a customer service representative, or an office team. Employees do not need a fully developed solution before a problem deserves attention.
See the five response steps · Handle “not now” and “no” · Read a healthcare example · Read Greg's transcript
In this KaiNexus Education Video, Greg explains why prompt responses matter even when a solution cannot be implemented immediately.
Watch the rest of the KaiNexus Education Video series.
In Healthcare Kaizen, Mark Graban and Joseph E. Swartz describe an employee idea as the beginning of a dialogue with a supervisor. The aim is to understand the problem and work together toward an improvement, even when the original proposal needs to change.
Graban's forthcoming The Silence Tax adds a useful distinction. Fear can discourage people from speaking because they expect a negative reaction. Futility can discourage them because they expect nothing useful to happen. An invitation to submit ideas needs to be supported by what leaders do afterward.
The sample wording below is illustrative. Adapt it to the situation and make commitments you can keep.
Thank the person for bringing the problem to your attention. Be specific about what you heard, without promising that their proposed solution will be approved.
Try: “Thank you for pointing out the repeated search for that tool. I can see how it interrupts the job. Let's look at what is happening.”
An automated receipt confirms that a submission arrived. A personal acknowledgment shows that someone has heard it. Neither replaces investigating the concern.
Ask where and when it happens, who is affected, and what the employee has observed. When possible, go see the work together. If the person suggests a purchase or process change, ask what problem it would address before deciding whether to accept it.
Try: “When is the information missing, and what do you have to do to get it? Could we look at a recent example together?”
Invite the employee's ideas, but avoid making a complete solution the price of being heard. If they do not know what would help, bring in others who can investigate with them.
Decide whether the team can try a small change, needs more information, or requires help from another department. Give the person doing the next step the time, authority, and support needed. Involve the employee who raised the issue rather than automatically handing the idea to someone else.
Try: “Would you be willing to test a different storage location with the team? I can make time during Thursday's shift and ask maintenance to help. Let's agree on what we'll check before we move it.”
Match the method to the problem. A low-risk local change may need a small PDSA test; an uncertain or consequential issue may require more investigation. An employee reporting an urgent risk needs the organization's immediate response and escalation process, rather than the routine idea-review queue.
Distinguish the date of the next conversation from a promise to have everything solved. Choose a follow-up that fits the issue's urgency and complexity. If another team needs to respond, retain responsibility for keeping the employee informed.
Try: “I need engineering's input before we decide. I'll contact them today and update you by Friday, even if we're still waiting for an answer.”
A useful update says what has happened, what remains unresolved, and what comes next. If a commitment slips, explain that and agree on a revised follow-up rather than waiting for the employee to chase it.
Tell the employee what was decided and why. If a change was tested, discuss what happened and whether the original problem improved. Recognize the contribution even when the test does not produce the expected result.
Try: “We tried the revised handoff on two shifts. The team found the missing information more easily, but one field still needs work. What did you notice, and what should we try next?”
Recording an item as complete is not the same as telling the person what happened. Equally, a declined proposal does not establish that the underlying problem has gone away.
A respectful response can be clear about a constraint while keeping attention on the problem. Avoid an unsupported “yes” that leaves employees waiting for resources that have not been committed.
Try: “We don't have capacity to run this trial this month because the same team is completing the equipment move. Let's review it two weeks from today. Meanwhile, is there a smaller step we can test with the resources we have?”
Explain the reason, agree on when or under what conditions the idea will be reconsidered, and make that follow-up visible. A review date is a commitment to review, not a promise to approve.
Try: “The replacement request wasn't approved in this capital cycle. I know that leaves you dealing with the breakdowns. I'll explain the decision at the huddle, and let's work with maintenance on what we can improve now. I'll also confirm what evidence is needed for the next review.”
Keep the decision about the request separate from the condition of the equipment. Mark the proposal's decision honestly and continue appropriate work on the unresolved problem. Do not keep describing a settled decision as “under consideration.”
Try: “I understand why you want to remove the duplicate check. That check currently catches errors we haven't prevented yet. Let's look at the cause of those errors and whether we can simplify the work while maintaining the protection.”
Explain the concern without dismissing the employee. The conversation may lead to a safer or more effective alternative.
Healthcare Kaizen describes coaching on idea cards at Children's Medical Center Dallas. When a proposal was not going forward, supervisors explained the reasoning and continued the conversation with the employee, individually or in a team huddle. The discussion could lead to a different way of addressing the problem.
The broader lesson applies to a factory, a service operation, or a hospital: recognizing a problem is valuable even when the first proposed countermeasure is unsuitable. Thank the person, explain the constraint, and investigate alternatives together. An idea system that only sends back an approval or rejection loses that opportunity for learning.
In the video, Greg recommends responding within a day or two, at least to acknowledge a routine opportunity. Healthcare Kaizen similarly emphasizes prompt feedback and describes same-day response as an ideal for visual idea boards. Use these as starting points for an explicit team commitment, rather than a universal deadline for resolving every issue.
Make it clear who checks incoming ideas, what happens when that person is away, and how urgent concerns are escalated. Review the response process when volume increases so that asking for more ideas does not create a growing queue of unanswered concerns.
In The Silence Tax, Graban recommends examining the response and follow-through, alongside the number of items raised. Useful questions include:
Count automatic acknowledgments separately from substantive responses. Review declined and deferred proposals separately from implemented improvements. A short backlog may reflect better problem solving, but it may also reflect employees giving up on submitting ideas.
A paper board or digital improvement system can make these commitments visible. KaiNexus can support managing improvement work, but managers still need to listen, provide help, explain decisions, and follow through.
Choose one item that has gone quiet. Contact the person who raised it, explain its current status honestly, and agree on the next step and when they will hear back. Then keep that commitment. Repeated experiences of a useful response give people a reason to participate again.
Hi, I’m Greg Jacobson from KaiNexus, where we make improvement happen.
You always hear that timing is everything, and it’s the same in continuous improvement. In successful improvement cultures, one of the most important things is giving a fast response to opportunities for improvement. While ideas might sit for a month or two in traditional suggestion box systems, leaders need to respond to opportunities for improvement in a day or two, at least acknowledging the opportunity even if the solution can’t be put in place right away.
Employees respond best to timely feedback, so it’s important that leaders at all levels make time each day to follow up on new opportunities for improvement. In just a few short minutes, you can send a powerful signal that improvement is a priority, and your actions can emphasize the importance of improvement more than words ever could. Managers need to respond to their employees’ input, and senior leaders need to ensure that the managers under them are responding quickly. Managers should take a few minutes (prompted by their daily email digest, in KaiNexus) to review and assign opportunities for improvement. KaiNexus makes this transparent, trackable, and extremely easy. We still encourage managers who have a question about the opportunity to talk to the employee face to face or bring it up in a team huddle or meeting, but responding quickly in KaiNexus makes this a snap.
Our experience shows that the most successful improvement programs are those where leaders quickly respond to new opportunities for improvement. Managers can best demonstrate their enthusiasm for improvement by responding quickly, which leads to more enthusiasm and participation from their employees. As a staff member, there are ways you can hold your leader accountable. Enter a comment about your opportunity for improvement in KaiNexus, or better yet, talk to your manager when you see them. Ask them about the opportunity. In many cases, you’ll be empowered to start taking action. KaiNexus helps make improvement easier partly because communication about the improvement happens quickly.
So don’t wait, participate in improvement today.
Watch more videos from the KaiNexus Education Video series.
Copyright © 2026
Privacy Policy