The Clock on the Idea Board: Why Every Line Suggestion Needs a 30-Day Answer
Photo by Photo by Homa Appliances on Unsplash on Unsplash
Walk through almost any plant and you can find one: a wooden box, a laminated sign, a slot that hasn’t produced a useful conversation in months. The suggestion box isn’t a bad idea. It’s just a place where good ideas go to wait. And on the shop floor, waiting looks a lot like dying.
Assemblers don’t stop offering ideas because they run out. They stop because they learn the math: submit an idea, hear nothing, watch nothing change, and decide the box is theater. The fastest way to extinguish a fired-up team is not a firm no. It’s “we’ll get back to you” with no date, no owner, and no follow-up.
The Box Isn’t the Problem. The Silence Is.
A suggestion box can work. What fails is the black hole behind it. Ideas go in, a supervisor says they’ll review them, and then the week gets loud. There’s a line down, a parts shortage, a customer tour, a new hire on station four. The idea sits. Two weeks later, the person who submitted it has already decided what the silence means.
Rejection stings, but it’s information. Silence is a different message: your idea wasn’t worth a reply. That message travels faster than any memo. Pretty soon, the only people using the box are the ones who don’t care whether anyone answers.
The fix doesn’t require a software platform or a corporate kaizen program. It requires a clock.
One Rule: A Verdict in 30 Days
Every idea gets a verdict within 30 calendar days: yes, no, or not yet. Not “we’re looking into it.” Not “let’s circle back.” A verdict, a reason, and an owner.
- Yes means we’re going to try it, and here’s who owns the next step.
- No means we’re not doing it, and here’s the specific reason.
- Not yet means the idea has merit, but the timing, budget, safety case, or upstream change isn’t there. It gets a revisit date and an owner.
The 30-day clock is not a promise to implement. It’s a promise to answer. That distinction matters. A supervisor can’t always say yes. But a supervisor can almost always say no, or not yet, with a reason, inside a month.
The Weekly Triage: Fifteen Minutes, Three Buckets
Keep it small. One standing 15-minute meeting a week with the area supervisor, a lead, and one assembler who rotates through. Open the log. Sort each new idea into one of three buckets: answer now, gather one fact, or schedule a test. If an idea needs more than one fact, assign the fact to a person and a date. Then close the log.
A simple idea log is enough. Paper works. A shared spreadsheet works. The point is that it’s visible and it has an owner.
| ID | Date in | Idea (one line) | From | Owner | Verdict | Reason | Next step or revisit |
|---|---|---|---|---|---|---|---|
| 014 | 11/02 | Move torque wrench holster to left side of station | R. Diaz | M. Chen | Not yet | Need ergonomics review before mounting change | Review 12/01 |
| 015 | 11/03 | Color-code bins for left/right hand parts | T. Brooks | A. Patel | Yes | Low cost, fits standard work | Trial on Line 2, week of 11/16 |
| 016 | 11/04 | Buy a second air dryer for Line 3 | J. Nguyen | K. Moore | No | Current dryer meets capacity; capital request not justified | Revisit if line speed increases |
Three columns do the heavy lifting: owner, verdict, and next step. If any one is blank, the idea isn’t done being handled.
Scripts That Don’t Sound Like HR
Supervisors don’t need a script, but a few plain sentences help when the line is moving and the conversation is public.
When an idea comes in: “Thanks. I’m logging it today. You’ll get a yes, no, or not-yet by December 13. If I need one more detail, I’ll come find you before then.”
When the answer is yes: “We’re going to try it. [Name] owns the first step. You’ll see a trial on the line the week of [date]. Thanks for pushing on it.”
When the answer is no: “We’re not doing this one. The reason is [specific reason—safety, cost, duplicate of another fix, not enough volume]. I know that’s not the answer you wanted. If that reason changes, bring it back.”
When the answer is not yet: “This has legs, but we can’t do it now because [reason]. It’s parked with a review date of [date]. [Name] owns the revisit. I’ll post it on the board so you can see it didn’t disappear.”
Notice what’s missing: “We’ll get back to you.” That phrase feels polite in the moment and corrosive by Friday.
Keep the Loop Where People Can See It
A feedback loop only works if people can see it without asking. Put a small idea lane on the existing communication board: Submitted, In Review, Verdict Posted. Use the log ID on a sticky note or a printed card. When an idea gets a verdict, move the card and write the date.
This is not about decorating the wall. It’s about making the process legible. An assembler on second shift should be able to walk by at 10 p.m. and see that idea 015 got a yes and idea 014 got a not-yet with a December revisit. That visibility does more for trust than a quarterly all-hands.
One caution: don’t let anonymous ideas become the default. Anonymity has its place, especially when the idea touches supervision or safety. But most line ideas benefit from a name and a conversation. If someone wants to submit anonymously, give them a pickup code so they can still get the verdict.
Why ‘We’ll Get Back to You’ Burns Trust
“We’ll get back to you” sounds harmless. It’s not. It transfers the burden of follow-up to the person with the least power to move the process. The assembler has to ask again, remind a supervisor, or watch the box. Most people won’t. They’ll just stop.
The cost isn’t only the lost idea. It’s the next idea, and the one after that. A team that believes suggestions go nowhere stops noticing small improvements. The scrap-saving tweak, the fixture that would save a wrist, the labeling change that would stop a mix-up—those don’t get submitted. The line keeps paying for the same problems.
A verdict, even a no, tells people the process is real. A reason tells them you actually thought about it. An owner tells them someone is on the hook. That’s not bureaucracy. That’s respect with a deadline.
The 30-Day Clock Is a Sign of Respect
The suggestion box isn’t a graveyard if someone is tending it. Give every idea a clock. Post the verdict. Name the owner. Keep the log where the line can see it. It won’t make every idea a winner, and it shouldn’t. But it will keep the good ones from dying of silence—and it will keep a fired-up team from deciding that speaking up isn’t worth the trouble.
