Leadership · Business Improvement
Why Have Employees Stopped Reporting Small Problems?
Small workplace irritations become a leadership problem when people conclude that speaking up changes nothing.
The question behind the silence
Why does a team live with an avoidable problem for months without raising it again? Often someone did raise it. A request was filed, a manager promised to look into it, and nothing visible happened. Dr. Tom DePaoli’s Broken Windows Management in Business presentation asks leaders to notice the everyday irritations that people have learned to work around. A broken form, an unreliable handoff, or a recurring supply issue may look trivial in a quarterly review. To the employee who encounters it every morning, it is a reminder that the organization accepts unnecessary friction. The silence that follows is not proof that the issue disappeared.
Take the complaint seriously
Tom’s response begins with proximity. Go to the place where the work happens and ask someone to show the task from beginning to end. A complaint that sounds like a preference may expose a genuine failure in timing, tools, or authority. Watching one case does not establish the entire pattern, so ask how often it occurs and what workaround people use. Then identify the owner of the next step. It helps to distinguish a quick fix from the underlying cause: replacing a missing form may be immediate, but learning why the form goes missing prevents the next interruption. The aim is neither a dramatic initiative nor a larger complaint tracker. It is a credible response to a real problem.
Make the response visible
Pick one issue the team values and give it a clear review date. If a fix is possible within the week, make it and ask whether it worked. If another department must help, explain who is involved and when the team will hear back. A visible list of issues and their status can be useful, provided it reflects actual decisions rather than replacing them. Tom recommends showing progress so employees can see that observations became improvements. Avoid claiming success after moving the delay to another desk. Follow the task through to the people who receive the work next, and let them say whether the change improved the whole process.
Listen for the next signal
The question is not whether a workplace can eliminate every irritation. It is whether employees have reason to believe that reporting one is worthwhile. If a manager returns after acting, explains a constraint honestly, and invites another look, the next problem may surface sooner. If the manager disappears, silence will likely return. Tom’s broken-windows metaphor is a reminder that neglected details send a message about standards and attention. Ask a team today which recurring issue they have stopped mentioning. Do not promise an instant cure. Promise a specific next step, name who owns it, and return with the result. That small cycle is how trust begins to recover.
Keep the language of the next update plain. If the fix will take two weeks, say so; if a proposed change failed, explain what the test showed. People can usually work with a difficult answer when they know someone has taken the issue seriously. They are less likely to trust an optimistic promise that is never revisited. A reliable update is itself a change in how the team is led.
Hear Dr. Tom explain the idea in the book presentation, then explore the book for the full account.