You've got surveys, an open door, maybe town halls. Even so, most of what your people know never reaches you. Here's why that happens, and one small change that gets you better answers starting today.
Your people can see problems in your operation that you can't. They know what's broken, what's slow, and what everyone quietly works around. And most of it never makes it up to you, even when you've set up all the usual ways to hear from them.
When I talk with operations leaders about this, they usually react in one of two ways.
Some are confident. They've got surveys, an open door, and a town hall every quarter. When I ask if they're really hearing what their people know, they say, "Yeah, we're pretty good at that."
Others are more honest with themselves. They figure there's a lot they're not hearing, and they've kind of made peace with it. They're running a big, messy operation across a bunch of sites and shifts, and the last thing they want is one more program that dumps a pile of suggestions on their desk to sort through. So they stick to what they can actually control.
I get where both of them are coming from. And I'd say the same thing to each of them.
Let's start with the confident leader. Here's the part that's easy to miss: you can have all these programs running and still not reach most of your people. Let me walk through why, one tool at a time.
Take surveys. A survey mostly tells you how people feel. Do they trust their manager? Would they recommend the company? That's genuinely worth knowing. But how someone feels won't tell you that the night shift in Cincinnati has been working around a broken handoff for three months. A survey was built to measure mood, and that broken handoff lives somewhere a mood score can't see.
Now think about the suggestion box. It only hears from the people motivated enough to log in, type something up, and trust that someone will actually read it. That's a small group. Most of your people are heads-down doing their jobs and never get around to it.
Town halls have the same catch. A town hall is basically a presentation with a few questions at the end. Picture your floor supervisor in Memphis. She is not going to raise a scheduling problem in front of 300 people and a VP she's met once. So she says nothing, and you never hear it.
See the pattern? Every one of these waits for people to come to it, and most people don't come. Your people care and they notice plenty. The catch is that there's no easy path for what they notice to reach you. Each of these tools is fine at the job it was built for. Finding what's quietly broken on your floor is a different job, and it needs a different kind of tool.
Now the second leader, the one who has already taken an honest look and stepped back. I respect that, and I want to be fair about why.
Internal improvement teams take months, talk to only a slice of the workforce, and hand you a report that still needs someone to own it and run with it. Consultants show up, take a snapshot, then leave, and everything they didn't get to just stays where it was. Both cost a lot. So deciding they're not worth the money makes complete sense.
Here's my gentle pushback, though. Deciding those specific tools aren't worth it is fair. Deciding that hearing what your people know, at scale, simply can't be done without a mountain of time and money is a much bigger claim, and it stopped being true a while ago.
Think about it. Your warehouse manager already knows why pick accuracy drops every Monday morning. Your customer service rep already knows she's losing time re-entering the same data in two systems. Neither of them needs a six-month project to tell you that. They just need someone to ask them the right question, directly, in a way that reaches them. That's the piece that's been missing: a simple, cheap way to ask your people and capture what they say.
So you've got two very different leaders. Different programs, different confidence, different decisions. Underneath all that, they're stuck on the same problem, and it's this:
Your people know what's broken. That knowledge just isn't reaching the person who can actually fix it.
The knowledge is already in the building. It simply has no way to get to you, so it stays put, and you keep running the operation without it.
Here's something you can do this week that costs nothing and instantly gets you better answers. Ask your people about their problems before you ask them for ideas. Let me explain why that small switch matters so much.
Most programs ask something like, "What ideas do you have to make us better?" or "How could we be more efficient?" The trouble is, those questions ask a warehouse worker or a service rep to think like a strategist for a minute, when what they actually live with all day is friction. They know what slows them down, what breaks, and what they have to work around every single shift.
So ask them about the friction instead. Ask, plainly, "What problems do you run into doing your job?" Watch how different the answers get:
Your regional manager tells you about the approval that makes her wait three days for a call she could make in twenty minutes.
Your receiving team tells you about the workaround they've run every Friday since a system broke eight months ago.
Your onboarding coordinator tells you exactly why new hires take six weeks to get productive instead of three.
Those are real problems that cost you real money, and your people already know every one of them. You just have to ask in a way that lets them say it plainly.
There's a reason the plain wording matters so much, and Jeremy Eden tells a great story about it from his early days at McKinsey. Right before a client meeting, a senior colleague pulled him aside and said, "Whatever you do, don't tell clients they have problems. Nobody wants to hear that. Tell them they have opportunities."
So Jeremy went in and laid it on thick. He told the client they had a big opportunity, a huge opportunity, a tremendous opportunity. The client stopped him and said, "So what you're telling me is I have an insurmountable opportunity?"
After that, Jeremy went back to just calling problems problems, and the clients appreciated it. They could tell he was being straight with them.
The same thing happens with your own people. The moment you dress up "problem" as "opportunity" or "area for improvement" or "challenge," you send a quiet signal about what you really want to hear. Your people pick up on that signal fast, and they decide, right then, whether it's safe to say the real thing or whether they should soften it and move on.
So keep it plain, ask about problems, in plain words, and your people will tell you what's actually broken.
Here's the part I love. Both kinds of leaders, the confident one and the honest one, tend to find the same thing once they finally ask the right question the right way. There was way more sitting there than either of them expected.
Meet Tell Jules
Tell Jules is the mechanism your operation has been missing: a way to carry the specific problems and ideas your people already have up to the person with the authority to act on them.
It has a roughly 7-minute conversation with the people closest to the work, by phone or a link, at their convenience, in virtually any language, then hands you a sortable report of what surfaced: the specific problem or idea, the fix that employee would make, who to involve, and the questions worth asking before you act.
You finally see what your own people already know, the costly problems they know how to fix and the ideas that could bring in new revenue, and you decide what happens next.
Who it's for
Operations leaders far enough from the floor that they can't personally see what their people see: many sites, many shifts, and layers of management between the work and the decision.
What it's for
Surfacing the specific problems your people run into, the fixes they already have in mind, and the standalone ideas that never make the trip up through the layers on their own.
How it's different
Consultants and top-down initiatives study a sample from the top and hand back a version of what leadership already sees. Tell Jules reaches every person you invite and returns the exact problem or idea and the fix, in their words, in a fraction of the time.
What setup looks like
You send a list of names and share a link or number with your team. There's no software to install, no logins to hand out, and no IT project to stand up first.
Ask them about the specific problems they hit doing their job, in plain words, and ask in a way that comes to them instead of waiting for them to fill out a survey or find a suggestion box. When you ask what actually slows them down, you get concrete answers you can do something about.
Because those all wait for people to come to them, and most people never do. A survey measures mood, a town hall is a big presentation, and a suggestion box only hears from the few who go out of their way to use it. The person with a real day-to-day problem usually stays quiet in all three.
Ask about problems first. "What ideas do you have to improve the business?" asks people to think like strategists. "What problems do you run into doing your job?" asks them about the stuff they deal with every day, which is what they know cold.
They're good at one thing: telling you how people feel about their job and their manager. When you want to find the specific things slowing your operation down, a survey mostly gives you a mood score, so it was never really built for that.