Idea examples
25 Employee Suggestion Box Ideas for Work (With Examples)
Concrete suggestions your team can adapt, plus the one question that gets people talking about their real work.
Published by the makers of IdeaKanban. See sources and how this guide was prepared.

Ask your team "any ideas?" and you mostly get silence. Or a request for a better coffee machine. Good employee suggestion box ideas start smaller: a tool someone couldn't find this morning, a handover that lost a detail, a form that keeps coming back incomplete.
Below you get 25 suggestion box ideas for work, grouped into five areas from the workshop to the office. Each one comes with a suggestion you can adapt and a question that gets your team talking about their own work. All 25 are also in a free printable PDF.
How to use these employee suggestion box ideas
A list of 25 ideas can backfire. Hand it out as it is, and you get 25 copies of the same suggestions back. Use it as a conversation starter instead:
- Pick one area. Workstations, handovers, office information, coordination or facilities. One area per meeting is plenty.
- Ask the question under the idea. Then wait. Give people time to think of a real situation from their own work.
- Write down three things: the problem you saw, the change you would try and where it applies. A photo helps.
Read the transcript
“We need better communication.” That's a complaint, not a suggestion. A useful suggestion names one problem, one change, and where it applies. Here are five examples. One. A marked spot for the shared torque wrench, right beside station three. Two. A minimum-level line in the screw bin, and one named person who refills it. Three. A three-line note for every open issue at shift handover: what happened, where it stands, and the next action. Four. One link to the current customer form, with an owner, and the old shortcuts deleted. Five. A photo beside the packing instruction that shows where the protective insert goes. To get ideas like these, don't ask for ideas. Ask about the last shift: what did you have to look for? Then make sure people see a decision, an owner and a result. That's what keeps the ideas coming. Get all twenty-five examples in this article, and send your first one in the live demo. IdeaKanban. From idea to done.
Pressing play loads the video from Vimeo. Privacy policy
Example: idea 18 proposes three lines at every customer-case handover: status, next action and who is responsible. Your service team tries those lines on the next ten handovers. Then you talk about what helped. That is far easier to review than "we need better communication".
When someone is ready to write an idea down, hand them our free employee suggestion form. It comes with a filled-in example and a smartphone demo.
Ideas 1–5: Workstations and tools
1. Give shared tools a marked home
Example to submit“I suggest a marked spot on the wall beside our station for the shared torque wrench, so the next person can find it and put it back.”
Ask the teamWhich item did you have to look for during your last shift?
2. Add a refill marker to a small-parts bin
Example to submit“I suggest a minimum-level line in the screw bin at Station 4 and one named person who refills it when the line shows.”
Ask the teamWhich item runs out before anyone notices that stock is low?
3. Create a return point for empty containers
Example to submit“I suggest a marked return point for empty containers next to the goods-in door, with one team responsible for collecting them.”
Ask the teamWhere do empty containers pile up during the day?
4. Replace confusing shelf labels
Example to submit“I suggest replacing the faded labels on our shared shelf with larger ones we can read from the normal working position.”
Ask the teamWhich label do new colleagues regularly need someone to explain?
5. Keep the current setup checklist at the station
Example to submit“I suggest one approved setup checklist at the machine, with a named person who swaps out old copies when it changes.”
Ask the teamWhich setup step is easy to miss, or known by only one colleague?
Ideas 6–10: Quality checks and shift handovers
6. Show a photo of the correct packout
Example to submit“I suggest an approved photo beside the packing instruction that shows where the protective insert goes, because that step is often missed.”
Ask the teamWhich detail would be easier to explain with one clear picture?
7. Make open shift issues visible
Example to submit“I suggest a three-line handover note for each open issue: what happened, the current state and the agreed next action.”
Ask the teamWhat did the last shift know that the next shift had to find out again?
8. Mark the place for items awaiting a check
Example to submit“I suggest a marked, labelled area for parts waiting for a quality check, agreed with Quality and in line with our process.”
Ask the teamWhere is it unclear to the next person whether an item is cleared or still waiting?
9. Capture the context of a recurring defect
Example to submit“I suggest taking a photo and noting the job number each time this scratch defect appears, so Quality has enough detail to investigate.”
Ask the teamWhich repeated issue do we discuss without enough detail to investigate it?
10. Match the visual check guide to the part
Example to submit“I suggest printing the part number in large type on each visual check guide at the inspection point, so nobody picks up the wrong one.”
Ask the teamWhen might someone pick up the wrong version of a check guide?

Start with what you have seen. A short description and one good photo give the person reviewing enough to ask the right next question.
Ideas 11–15: Office work and shared information
11. Keep one link to the current customer form
Example to submit“I suggest one link to the current customer form with a named owner, and deleting the old shortcuts in our shared folder.”
Ask the teamWhich file do people keep asking about: is this the latest version?
12. Make ownership of shared inbox requests clear
Example to submit“I suggest tagging each shared-inbox request with the name of whoever takes it, so nobody waits or doubles up.”
Ask the teamWhich requests get checked twice, or wait because everyone thinks someone else has them?
13. Maintain one supplier contact directory
Example to submit“I suggest one shared supplier contact list with an owner and a 'last checked' date at the top.”
Ask the teamWhich contact details do colleagues keep asking someone for?
14. Add a short expense-submission checklist
Example to submit“I suggest a five-point checklist, approved by Finance, of the details and receipts needed before anyone submits an expense claim.”
Ask the teamWhat information does Finance most often have to ask for again?
15. Answer recurring IT questions in one place
Example to submit“I suggest a one-page guide, checked by IT, for the routine questions we keep asking, plus a contact for anything it does not cover.”
Ask the teamWhich everyday support question has come up several times this month?
Ideas 16–20: Team coordination and onboarding
16. Show the decision needed on meeting agendas
Example to submit“I suggest that every decision item on our team agenda shows the decision needed and who prepares it.”
Ask the teamWhich meeting item was hard to prepare for because its purpose was unclear?
17. Create a first-week buddy checklist
Example to submit“I suggest a one-page checklist for onboarding buddies that covers the questions new colleagues ask in their first week.”
Ask the teamWhat did our newest colleague have to learn by trial and error?
18. Use a three-line customer-case handover
Example to submit“I suggest three lines on every open customer case we hand over: current status, next action and who is responsible.”
Ask the teamWhat was missing the last time you took over someone else's case?
19. Clarify shared-resource bookings
Example to submit“I suggest that every booking for the shared van or meeting room shows who booked it, what for and when it is free again.”
Ask the teamWhen did we last discover a booking clash only when we needed the resource?
20. Keep a short project handover summary
Example to submit“I suggest a one-page summary of key decisions, open actions and contacts whenever a project moves to the next team.”
Ask the teamWhich decision did a receiving team have to piece together again?

A good idea still needs a decision and an owner. Agree the next action before you hand an approved idea to a team.
Ideas 21–25: Materials, facilities and working conditions
21. Trial a better-fitting packing option
Example to submit“I suggest that Logistics tests a smaller box for this product that still gives it the protection it needs.”
Ask the teamWhich shipment seems to use more packaging than the product needs?
22. Review unnecessary default printouts
Example to submit“I suggest checking which daily printouts the team actually reads, and switching off the rest where the process allows.”
Ask the teamWhich document gets printed and then left unread?
23. Make the local recycling point clearer
Example to submit“I suggest clearer labels with pictures at our recycling point, checked against the site's collection rules.”
Ask the teamWhich items are people unsure how to separate at this location?
24. Make small maintenance issues easier to report
Example to submit“I suggest a simple way to send the exact location and a photo of small issues, like a dripping tap, straight to the team responsible.”
Ask the teamWhich minor issue have people noticed but nobody knows where to report?
25. Agree a useful quiet-work period
Example to submit“I suggest a four-week trial of a quiet hour each morning, with one person covering urgent requests, and then asking the team how it went.”
Ask the teamWhich recurring interruption makes focused work harder than it needs to be?
From a vague complaint to a suggestion you can act on
Most suggestions start as a complaint. That's fine. Your job is to turn it into something a team can try.
Say someone in your service team tells you: "Communication is poor." That doesn't tell you which handover to look at. So you ask: "What happened to the last request that waited?"
Now the answer is concrete: "On the late shift, two of us saw the same customer request. Each of us thought the other had taken it." The proposal almost writes itself: agree one way to mark who has taken an inbox request, and test it with both shifts for two weeks.
Before you approve it, check the team's actual tools and who is responsible for the inbox. Don't attach a time saving nobody has measured. After the trial, ask the colleagues on both shifts: was it clear who owned each request? Write their answer down with the idea.
How to ask your team for better workplace improvement ideas
"Does anyone have an idea?" puts people on the spot. A question about the last shift, a recurring request or a confusing label gives them something to point at. Four habits help:
- Ask about something recent. Yesterday's shift is easier to describe than "our processes".
- Listen before you solve. If someone says the shared inbox is confusing, ask what happened to the latest request. The real issue might be unclear ownership, missing information or something you didn't expect.
- Shape one change together. Ask who else knows the work and what would show that a trial helped.
- Leave room for a better answer. The first proposal doesn't have to be the final one. A colleague may know another way.
Not everyone wants to share an idea in front of the group. Offer a second way in, such as a paper form or a QR code people can scan on their own.
CIPD's guidance on employee voice stresses that managers need to listen and act on what they hear. So asking for ideas creates an expectation: someone will review them and explain what happens next.
What to do after a suggestion arrives
This is where most suggestion boxes fail. The idea goes in, and nothing comes back out. Five steps keep things moving:
- Review on a fixed rhythm. Decide who looks at new suggestions and how often, for example every Tuesday morning.
- Clarify first. If something is unclear, ask the person before you decide.
- Decide and assign. Approved ideas go to the team that can act, with one clear next action.
- Check the change in use. A new label, a revised handover or a shared guide is only an action. Ask the people doing the work whether it helped before you call it an improvement.
- Tell people what happened. Explain declined ideas as carefully as approved ones.
Want to see this on a board? Our continuous improvement board guide arranges eight production and office examples from New to Done.
IdeaKanban covers exactly this workflow. Employees submit by QR code or link in their phone browser, without an account. Idea Managers review on a Kanban board and assign approved ideas to a department. The department gets an email with a secure link to post updates and photos. You can click through it yourself in the free live demo, no signup needed.
The included features list the current scope. For a wider rollout, use the seven-step implementation guide.
Employee suggestion box ideas: common questions
What are good suggestion box ideas for work?
Ideas that name a concrete problem and propose a change someone can try. A clearer storage label, a refill line in a parts bin, one link to the current form or a three-line case handover are all good examples. The best ones come from the work your team does every day.
Do suggestions need a financial benefit?
No. Most employees can't estimate savings when they submit, and they shouldn't have to. A clear benefit, such as "people find the current instruction faster", is enough to start the review. If you later report savings, check the result first and explain how you calculated it.
How do we get suggestions from employees without company email?
Offer a way in that works where they are. In IdeaKanban, employees scan a QR code or open a link and submit in their phone's browser, without an account. Test the route with the people on the shop floor before you roll it out.
Should a suggestion box be anonymous?
Decide what your process needs and explain it honestly. No account doesn't automatically mean anonymous: the text or a photo can still identify someone. If anonymity matters, check your tool and process before you promise it.
Can we just copy all 25 ideas onto our board?
Better not. Use the list to start conversations. Submit only suggestions that match a real situation in your workplace, with the context needed to review them. A copied list without context just gives the person reviewing more questions to ask.
Sources and approach
The 25 suggestions and team questions were created by the IdeaKanban team to show what useful suggestions look like. The PDF guide contains the same ideas and questions. Sources and the current IdeaKanban workflow were checked on 13 November 2026:
- CIPD: Employee voice, on managers listening and acting on feedback.
- Lean Enterprise Institute: Kaizen, on continuous improvement of a process.
- IdeaKanban: how it works, pricing and the public demo. The drawings follow the style of our How it works page.