Your Cheapest Consultant Is Standing in the Dish Pit

Sep 15, 2026

Why frontline employee feedback never makes it upstairs, and three ways to build the pipe.

The Dishwasher Knew

A few years ago, a hotel hired me to “fix” their operation. As part of the process, I ran a SWOT analysis.

I did what you’re supposed to do. I interviewed the general manager. I interviewed the department heads. I interviewed the supervisors. Everyone had a binder’s worth of opinions, and roughly half of them were about each other.

My last stop was the restaurant. I bought a tea, sat down across from the dishwasher and asked him what got in his way.

He didn’t need a minute to think. He’d had years.

During a rush, the dish pit fell behind because there was no central drop-off spot. Servers dropped dirty plates wherever they happened to be standing , a bus station here, a side stand there which meant the dishwasher spent the busiest hour of the night walking. Not washing. Walking. For a guy whose job is to stand in one place and feed a machine, he was racking up 25,000 steps before his break.

No wonder he needed a smoke. He had to let his shoes cool down.

He knew exactly where the bottleneck was, why it happened and roughly what it would take to fix it. Nobody had ever asked him. Add to that, because he was the lowest person on the totem pole, he saw the kitchen from a completely different perspective. He’d been standing next to the answer for years, waiting for a question.

When the owner got back from vacation, he found me in the lobby.

“I hear you’re talking to the staff about my hotel.” He said Staff, the way you’d say raccoons.

I told him yes, that’s part of my process. I asked whether he thought the dishwasher might know which chemicals actually work, where the pit gets jammed and how he could be more effective.

He considered this for exactly as long as it takes to not consider something.

“The only thing a dishwasher can tell you is when payday is and when his smoke break is.”

He’d just paid a consultant to find out what his dishwasher already knew. Then he explained to that consultant why the dishwasher couldn’t possibly know it. I’ve seen tighter logic on a bar napkin.

That one sentence told me more about the hotel’s problems than the SWOT did.

Why the Frontline Knows First

As a Hospitality specialist, I know that housekeepers, for instance,  often know a hotel is in trouble before the general manager does. They know which room springs the same leak every time the weather turns. They notice the guest who suddenly seems upset. They know which policies confuse people, because they’re the ones hearing the complaint after everyone else has walked away.

Why do they know?

Because they’re there.

Not in the strategy meeting. Not studying the monthly dashboard. Not waiting for the quarterly customer-experience report, which arrives in time to explain last quarter.

They’re standing where the experience actually happens.

The same is true in every business. The frontline sees and hears more than a manager ever will. The server knows which menu item keeps coming back to the kitchen like it forgot something. The receptionist knows which policy customers hate hearing explained, because she’s the one who has to explain it with a straight face, hoping her rolling eyes don’t give it away. The warehouse picker knows which step in the process exists only because somebody in 2019 said so, and that somebody has since retired to Kelowna. The salesperson knows which promise marketing keeps making that operations keeps failing to keep.

And then, occasionally, leadership hires an expensive outside consultant to discover all of it.

I say that as a consultant.

There’s a real place for outside expertise. An outsider can see patterns insiders miss, challenge assumptions, borrow ideas across industries and have conversations that internal politics make impossible.

But here’s the part my industry leaves out of the proposal: half the time, we’re not discovering anything. We’re laundering. Maria at the front desk has been saying it since February. Her version comes in a break-room voice with a complaint attached. Mine comes in a binder with a cover page. Same fact. One of them gets an eye-roll. The other gets an invoice.

That’s not a knowledge gap. That’s a status filter. Organizations don’t ignore frontline intelligence because it’s wrong. They ignore it because of who’s holding it.

The information was never missing. What was missing was permission — to speak, to be heard, to be believed.

Frontline Employee Feedback Is Data. You’re Just Not Collecting It.

Businesses spend enormous amounts on customer intelligence and almost nothing on frontline employee feedback. Surveys. Review tracking. Dashboards. Social listening. Mystery shoppers. Journey maps with more arrows than an airport.

Meanwhile, your employees are collecting qualitative data all day long, for free, and nobody’s built the pipe.

They hear the hesitation before a customer complains. They see the workarounds people invented because the official process doesn’t work. They notice the same question being asked for the fortieth time, and they’ve started answering it before the customer finishes.

This isn’t an argument against data. It’s an argument for recognizing another source of it. One that already has a parking pass.

Your frontline is a living intelligence network. Most organizations are barely plugged in.

The fix isn’t another annual employee survey. Surveys can help. But asking people what they think once a year, then sending them a 37-page PowerPoint six months later, isn’t a listening strategy. It’s a ritual. It’s Groundhog Day with a Likert scale.

Here are three things that actually move frontline knowledge upward.

1. Make It Safe to Tell You Something You Don’t Want to Hear

Years ago, I took over a department at a casino. One of the top-selling employees was, to put it kindly, a force of nature. She got the best sections, the best tippers and the biggest sales numbers, and she didn’t much care who she stepped on to keep it that way. If you’d charted her career path, it would have been a straight line with footprints on it.

Management loved her numbers. Numbers don’t file complaints.

When I eventually let her go, something strange happened. One by one, staff came to my office. Not to complain. To thank me. And then, almost every time: “Marc, do you know what she used to do?”

The stories poured out. 

I asked the obvious question. Why didn’t anyone tell a manager?

“Because she was the favourite. Nothing would have happened.”

Here’s what stuck with me. The silence didn’t stay contained to her. Once people learned that raising a problem was pointless, they stopped raising all problems. Broken equipment went unreported. Customer issues got buried, because reporting one meant being accused of underperforming. One untouchable employee had taught an entire floor to keep its mouth shut, and management was somehow the last to know the thing they’d caused.

Nobody issued a memo saying please stop telling us the truth.

Culture handled it. Culture is very efficient.

Harvard Business School professor Amy Edmondson has spent decades studying this. Her advice to leaders is blunt: “Don’t shoot the messenger. Don’t get angry when you hear a dissenting view or bad news.” Employees are constantly calculating whether speaking up is worth the risk, and they run that math by watching what happened to the last person who tried. Nobody needs a spreadsheet. The guy who spoke up last month now has the Sunday brunch shift. Case closed.

So leaders need a response protocol. When someone raises a legitimate concern:

1. Thank them for raising it.
2. Ask questions before defending the current process.
3. Separate the person from the problem.
4. Ask who else might be seeing the same thing.
5. Say what happens next.

This isn’t organizational anarchy. Employees don’t get a veto, and not every suggestion deserves implementation. Someone will always propose a nap room. But every legitimate observation deserves consideration.

One of the most powerful questions a manager can ask on a regular basis is: “What are you seeing that I might not be seeing?”

There’s humility built into that question. It admits something leaders occasionally forget: the higher you climb, the farther you get from the work (This is why Undercover Boss is so fun to watch). Your title gives you more authority. It does not give you better eyesight. If anything, the view from the corner office is mostly parking lot.

2. Run a Frontline Intelligence Huddle

Most meetings push information down. Here are today’s priorities. Here are the numbers. Here’s what head office wants. Here’s what you’ll do about it.

Useful. But where and when does information travel up?

Once or twice a week, gather the team for ten minutes and ask three questions:

• What are you noticing?
• What keeps getting in the way?
• What are customers asking for, complaining about or working around?

That’s it. No pastries, no 42-slide deck. The Institute for Healthcare Improvement uses brief huddles, typically ten minutes or less, to surface operational and safety problems before they grow. If it works in a place where the stakes are literal lives, it’ll survive a hotel, a hardware store, or a welding shop.

A housekeeping team might flag that the same door lock has generated four complaints. A retail team might point out that customers can’t find a product category. A dishwasher might mention he’s training for a marathon he never signed up for.

None of that shows up on a financial statement.

Yet.

That word is doing a lot of work. Small operational irritations have a nasty habit of becoming expensive precisely when it’s least convenient, which is the only time anything becomes expensive.

Keep it short. Write things down. Look for repetition. Rotate who speaks first so it doesn’t become the manager talks and everybody nods.

And whatever you do, don’t turn observations into interrogations. If someone says, “Guests keep getting confused by the parking instructions,” the first response cannot be, “Well, did you explain it properly?”

Congratulations. You’ve just taught the room not to bring you problems. They’ll bring them to the break room instead, where the solutions are worse and the coffee is better (if the machine is working).

Your job in that moment is to collect intelligence. Diagnosis comes later.

3. Close the Loop, or Stop Asking

This is where most listening programs go to die.

Leadership asks for ideas. Employees provide them. Nothing happens. Leadership asks again, this time with a branded mug.

Gallup reported in 2023 that only 8% of employees strongly agree their organization takes action on employee surveys. Eight. That’s not a feedback problem. That’s a credibility problem. When people repeatedly speak up and hear nothing back, they learn that speaking up is administrative theatre. And unlike real theatre, nobody’s getting a standing ovation.

Eventually they stop.

Build a simple closed loop. Every issue raised lands in one of three buckets:

ACT. We can fix this quickly.

INVESTIGATE. We need more information before deciding.

EXPLAIN. We’re not changing this, and here’s why.

Notice the third one. Closing the loop doesn’t mean saying yes. Sometimes the answer is no: too expensive, creates a bigger problem, or the employee is seeing one piece of a larger decision.

People can handle no. They’ve been hearing it since they were two. What they can’t handle is disappearing into a black hole with a suggestion-box logo on it. 

One caveat on that no. Before you deliver it, try a detour through INVESTIGATE. Ask why this matters to them and what they think it would fix. Half the time the suggestion is aimed at a symptom, and the symptom can’t be fixed, but the problem underneath it can. I’ve built a whole career on one question:

If it’s not impossible, what would it take?

Give each concern an owner, a next step and a date. A whiteboard will do:

Issue → Owner → Next step → Target date → Outcome

Then celebrate the intelligence that paid off. “Sarah noticed customers kept missing the pickup instructions. We changed the confirmation email. Complaints dropped.”

Now everyone sees the equation: I notice something + I speak up + someone listens + something improves.

That’s how a listening culture starts feeding itself.

Listening Is an Operating System, Not an Event

Leaders love to say, “My door is always open.”

An open door is not a communication system. It’s a door. It still requires the employee to spot the problem, decide it matters enough, leave their station, walk past three coworkers who will ask where they’re going, step over the threshold into your office and take the social risk of saying it out loud. By that point, most people decide the leak can wait.

Great organizations reduce that friction. They create regular moments for frontline intelligence to surface. They train leaders to receive bad news without shooting the messenger. And they visibly close the loop so people know speaking up mattered.

None of this is expensive. That’s almost the problem. Simple management habits don’t come with a software demo, a glossy binder or a consultant holding a laser pointer. They require something harder: consistency. Nobody’s ever been given a plaque for consistency. Hold that thought.

The dishwasher shouldn’t have to hope a consultant buys him a tea. The housekeeper shouldn’t have to hope the GM asks the right question. The server shouldn’t have to wait for the one-star review to become the messenger.

Your people are already telling you what’s happening in your business. Sometimes with words. Sometimes with workarounds. Sometimes with frustration.

And sometimes, after enough attempts to be heard, with silence.

Pay attention to that last one.

The owner of that hotel was right about one thing. The dishwasher did know when payday was. He also knew why the kitchen fell apart every Friday night.

Only one of those facts ever made it upstairs.