Leadership

The Small Complaint Nobody Was Assigned to Hear

· 5 min read

Most failures are preceded by something small that someone noticed. The person who noticed it usually had no place to take it, so it stayed with them until the larger problem arrived and made it obvious in hindsight.

Think back to the last thing that went seriously wrong in your unit. Not the moment it became a crisis, but the months before. If you ask around, someone will usually remember an early sign. A client mentioned in passing that a deadline had slipped twice. A new employee asked a question about a process that suggested nobody had explained it the same way to any two people. A report came in a day late, then on time, then late again. A colleague said in a hallway that something felt off with a vendor and could not say exactly what.

Each of those was noticed. None of them was hidden. The person who saw it may even have mentioned it to someone. And then nothing happened, because there was nothing obvious to do with it. Nobody was negligent and nobody was protecting themselves. The observation was simply too small for any of the channels your unit has, and so it stayed where it landed.

Small signals do not fit the channels you built

Most units have good routes for large problems. A clear failure gets escalated. A missed target shows up in a report. A complaint with a name and a date attached goes to the person responsible for handling complaints. Those routes work because the problem arrives already shaped: it has an owner, a category, and a level of urgency that matches the channel.

Early signs arrive without any of that. An offhand comment from a client is not a complaint, so it does not go to whoever handles complaints. A one-time delay is not a trend, so it does not appear in the report that tracks trends. An odd question from a new hire is not an incident, so nobody writes it up. The person who noticed has to decide on their own whether it is worth raising, and most reasonable people decide that it is not, because raising something that small feels like overreacting, or like creating work for someone else over what is probably nothing.

So the observation stays with whoever happened to be in the room. If that person leaves, changes roles, or simply gets busy, it goes with them. Weeks later, when the problem is large enough to fit a channel, it arrives looking sudden, and the review that follows finds the early signs scattered across five people who each saw one piece and had no reason to connect it to the others.

This is different from a team that has stopped telling you things. In that case people are choosing to withhold. Here nobody is withholding. The signal was offered freely and had nowhere to go.

What it costs

You learn about problems at the most expensive point. Almost every problem is cheaper to address early, when it is a slipped date rather than a lost client, or a confusing process rather than a compliance finding. A unit that only acts on signals large enough to fit a channel is choosing, without meaning to, to find out about most problems after the cheap window has closed.

The people who notice things learn to stop. Someone who raises a small concern and sees nothing happen draws a reasonable conclusion: that kind of observation does not matter here. They do not stop noticing, but they stop mentioning. The people most likely to draw that conclusion are often the ones closest to the work and to the people you serve, which means the unit loses its best early warning without anyone deciding to give it up.

Hindsight teaches the wrong lesson. When the review after a failure finds that someone saw it coming, the usual response is to wonder why they did not speak up louder. That puts the burden on individuals to judge, alone, which of many small observations deserves to be escalated. It also makes people more cautious about mentioning anything that might later be held against them as a warning they failed to press. The real gap was never courage. It was that nobody was responsible for collecting what people noticed.

Three moves

Make someone responsible for small things. The fix is not a new reporting form. It is a named person, or a standing moment, whose job includes hearing observations that do not belong anywhere else. That can be a ten-minute item at the end of a weekly meeting where people say what seemed odd that week, with no requirement that it be important. It can be a single person who keeps a running list. What matters is that the person who notices something has a place to put it that does not require them to decide first whether it is serious.

Look for repetition rather than size. One late report means very little. Three late reports from different people in the same month, or the same question asked by two new hires, or two clients mentioning the same slip in different words, means a great deal. A single observation is rarely worth acting on by itself. The value comes from putting several of them next to each other, which only works if someone is holding them in one place. Review the list every few weeks with that question in mind: what keeps showing up?

Close the loop even when the answer is nothing. When someone raises a small concern, tell them what happened to it, even if what happened is that you looked and found nothing. "I checked with the vendor, and it was a one-time staffing issue" takes thirty seconds and tells the person that their observation was received and acted on. People keep offering what they notice when they can see that it goes somewhere. They stop when it seems to disappear.

The part that is about you

Leaders tend to measure their awareness by how quickly large problems reach them, and most leaders are reasonably good at that. The harder question is how much reaches you before it is large. That is mostly not a function of your openness or your approachability. People can trust you completely and still not bring you something that seems too small to bother you with.

You may also be one of the people sitting on a signal right now. Most leaders have a half-formed concern they have not mentioned to anyone because it did not seem worth a conversation yet. Writing it down where someone else can see it, and checking whether anyone else has noticed the same thing, is the same move you are asking of your team.

Three questions

If someone in your unit noticed something odd this week that was not yet a problem, where would they put it, and who would ever see it?

What was the last small observation someone raised with you, and do they know what happened to it?

Looking back at your unit's last serious problem, how many people saw an early sign, and was there any place where those signs could have been seen together?