# Signal rises from the work, not from the room where you talk about it.
The people closest to the work always know what's broken first. Always. Before the executive team sees it in a quarterly review. Before the dashboard turns red. Before the customer complaint reaches someone with a title. The person on the floor, on the phone, at the keyboard, in the truck — they felt it weeks ago.
This isn't a controversial observation. Every leader I've ever worked with will nod along and say, "Of course, we listen to our front line." And most of them believe it. The gap isn't in intention. It's in infrastructure. The organization hasn't built a system that lets signal travel upward without being filtered, summarized, politicized, delayed, or softened into uselessness.
The front line doesn't have an insight problem. The organization has a plumbing problem. The pipes that carry signal upward are clogged.
How signal dies
Signal from the work dies in predictable ways. I've seen the same patterns in companies of 30 people and companies of 3,000.
**The aggregation kill.** A warehouse worker notices that a specific supplier has been shipping damaged pallets for the past three weeks. They mention it to their supervisor, who mentions it at a team meeting, where it becomes "some quality issues with incoming freight," which gets rolled into a monthly ops summary as "receiving efficiency is trending down." By the time it reaches someone who could actually call the supplier and fix it, the specific, actionable signal has been averaged into a vague metric. The resolution is a task force to "improve receiving processes." The worker who noticed the problem rolls their eyes.
**The hierarchy filter.** A customer service rep knows exactly why call volume spiked last Tuesday — the new billing format is confusing and customers can't find their account number. But the rep reports to a team lead, who reports to a manager, who reports to a director, who has a monthly meeting with the VP of product. By the time the signal could reach someone who can change the billing format, it's been through four filters and three weeks have passed. Meanwhile, the company launches a project to "reduce call center volume through self-service options." The right answer was making the account number bigger.
**The culture mute.** In some organizations, the signal is there but nobody wants to send it. Raising a problem feels like complaining. Identifying a flaw in a process feels like criticizing the person who designed it. Saying "this doesn't work" in a culture that rewards positivity feels like career risk. So people compensate silently. They build workarounds. They absorb the friction. And leadership concludes that things are running smoothly because nobody's saying otherwise.
Build signal paths, not suggestion boxes
The instinct, when leaders realize they're not hearing from the front line, is to create a feedback mechanism. A suggestion box. An anonymous survey. An "open door policy." A Slack channel called #ideas.
These almost never work, and the reason is structural. A suggestion box asks people to do extra work — to stop what they're doing, articulate a problem, submit it into a system, and hope that someone reads it, cares about it, and has the authority to act on it. That's a lot of hope. Most people have been burned enough times to know that the suggestion box is where ideas go to die quietly.
What actually works is building signal into the flow of work itself. Not as an extra step, but as a byproduct of the work that's already happening.
A dispatch system that automatically flags when the same route has three late deliveries in a week — that's a signal path. A customer service tool that tags patterns in call reasons and surfaces them in real time — that's a signal path. A project management setup where blockers are visible the moment they're logged, not when someone remembers to mention them in standup — that's a signal path.
The difference is friction. A suggestion box adds friction. A well-designed signal path removes it. The signal should flow upward because the system is built that way, not because someone took the time to push it.
The listening problem
Even with good signal paths, there's a second problem: the receiving end. Leadership has to actually want the signal, including the uncomfortable signal. Especially the uncomfortable signal.
I worked with a company where the CEO had excellent instincts and an open-door policy that people actually used. Front-line employees would come to him with real problems and he'd listen carefully and take notes. Good so far. The problem was what happened next: he'd fix the problem personally. Quick call, direct intervention, done.
This felt responsive. It was actually catastrophic. By fixing problems one at a time through personal intervention, he was training the organization that the way to get things fixed was to go to the CEO. He became a bottleneck for every problem that mattered. The middle management layer — the people who should have been empowered to fix these things — atrophied because they were constantly being bypassed.
The signal was flowing. But it was flowing to the wrong place, and the response was creating a dependency instead of building capacity.
What good signal infrastructure looks like
The best organizations I've worked with share a few traits:
The front line has agency. Not just voice — agency. The person who spots the problem has the authority and the tools to fix a meaningful percentage of problems without escalating. Escalation is for the problems that need someone else's authority or resources.
Signal is specific and visible. Not buried in a report that nobody reads until the monthly review. Visible in real time, in the tools people already use, with enough specificity that someone can act on it today.
Leadership looks at leading indicators, not just trailing ones. They don't wait for the quarterly numbers to tell them what the warehouse supervisor knew six weeks ago. They build systems that surface early signals — the kind that are still cheap to act on.
One more thing: bad news travels fast. If the culture punishes people for surfacing problems, you'll never hear the important ones until they're expensive. The organizations that learn fastest are the ones where saying "this is broken" is treated as a contribution, not a complaint.
The signal is always there. The work always knows. The only question is whether you've built the infrastructure to hear it.