Every plant manager who has run a suggestion scheme knows the curve. Launch week: forty submissions. Month three: four. Month six: the box comes off the wall.

The usual explanation is engagement — people lost interest, the culture is not there, we need to relaunch with better comms. That explanation is comfortable and almost always wrong.

Reporting is a cost-benefit calculation

Raising a problem is not free. It takes time in a shift that has none spare. It carries a small social cost, because you are pointing at something that might be somebody's decision. And it carries a risk of looking like a complainer if nothing comes of it.

Against that, the benefit: the thing might get fixed.

People run this calculation, mostly unconsciously, and they update it based on evidence. Four things raised, nothing came back, so the expected benefit is near zero and the cost is not. Silence is the correct answer to that arithmetic.

Your floor is not disengaged. It is well calibrated.

The three failure points

1. It never became a record

Somebody said something in passing. It was heard, agreed with, and never written down. From the operator's side this is indistinguishable from being ignored, and it is by far the most common failure.

2. It became a record nobody reopened

It went in a report. The report was filed. From the operator's side: identical to the first case.

3. It got fixed and nobody told them

This one is genuinely painful, because the work happened. The change was made, six weeks later, in a different part of the process, and the person who raised it never connected the two. You paid the full cost of the fix and got none of the credibility.

The asymmetry
A fix nobody hears about buys you nothing in reporting behaviour. A "we looked at this and decided not to, here's why" — delivered in person — buys you almost as much as a fix. The loop closing is what matters, not the outcome.

What actually rebuilds it

Not a relaunch. Not a poster. Three mechanical things:

  • Everything raised becomes a visible record, immediately. Logged on the floor, in front of the person who raised it, so they watch it happen. This alone changes behaviour, before any fix lands.
  • The record has a name on it. Not a department. A person. Unowned items are the ones that die quietly.
  • The person who raised it hears the outcome. Fixed, deferred or rejected — all three are acceptable. Silence is not.

Note that none of these require you to fix more things. Your capacity to make changes is roughly fixed. What is not fixed is how much reporting behaviour you get per fix, and that is almost entirely a function of whether the loop is visible.

The timeline for recovery

A floor that has learned not to report does not un-learn it in a week. Expect roughly this:

  • Weeks 1–3: nothing. You ask, you get "it's fine". Keep asking.
  • Weeks 4–8: the first test cases. Small, safe things from one or two people watching what happens.
  • Months 3–4: if the test cases closed visibly, volume arrives — including the things that have been annoying people for years.

The dangerous moment is month three. Volume goes up, your capacity does not, and the temptation is to start quietly not responding to the small stuff. That is the same signal that broke it the first time, and the second recovery is much harder than the first.

Better to say no visibly than to say nothing.