There's an old joke that a consultant is someone who borrows your watch to tell you the time. It’s not just a joke, it's often true: companies pay outside firms a fortune to hand back a polished version of what their own people already knew.
But the same blind spot is hiding inside top-down initiatives and big strategic bets, too.
Consultants, C-Suite initiatives, and big bets are the three most common ways companies go looking for what's broken. Each one may have some value. But none of them was built to capture what the people closest to the work already know. These methods have you looking up and out, when what you're after has been down and in all along.
1. Consultants Borrow Your Watch to Tell You the Time
There are rare cases where bringing in a consultant makes sense: when you need real expertise that doesn't exist in the building and that expertise is smarter to rent than to buy. When that's the job, a consultant is the right call.
The trouble shows up when you hire an outside firm to find what's wrong inside your operation.
Consultants get their access from the top: leadership frames the problem, picks who gets interviewed, and signs off on the findings. They spend their weeks with the executives and the dashboard, working from the same picture leadership already has. And that picture has already been filtered. As information climbs the layers of management, the inconvenient details get summarized away at each step, so what reaches the top is a tidier version of what's really happening on the ground.
The people the firm sends to do the digging tend to take that tidy version at face value and treat a living, complicated operation like a case study. You brought them in to get past your own filtered view of the business, and what comes back is a more polished version of the same view …or their own cookie cutter version of how you should operate.
That's how you end up paying a small fortune for someone to borrow your watch and tell you the time.
A benchmark tells you the score but never the reason
When an outside firm doesn't have your answer, it reaches for benchmarks: what a company your size and industry supposedly spends, staffs, or produces.
A benchmark can tell you whether you land above or below average, but it can't tell you why you land there. It doesn't know that one of your branches has quietly worked around a broken system for two years, or that a single understaffed shift is dragging a whole site's numbers down. Those reasons live inside your specific operation, and an average borrowed from other companies was never going to see them.
And however the benchmark lands, it rarely moves anything. If it puts you behind the average, it's fair to wonder whether the comparison even holds up because different companies count these things differently. And if it puts you ahead, it's easy to feel reassured.
But being the best in your industry isn't the same as being as good as you could be; it can simply mean the rest of the field is further behind. Either way, the benchmark leaves the real question untouched: what's actually slowing this operation down, and where?
$100 million in recommendations, not one used
We once followed a big-name firm into a company it had spent months benchmarking. The firm left behind a thick binder with $100M worth of recommendations. Years later, that same binder landed on our desk as a "starting point," and not one recommendation had been acted on.
Generic, benchmark-shaped advice rarely survives contact with a real operation, and the people who would have had to carry it out had no hand in creating it.
So we did the obvious thing the firm hadn't: we asked the people inside. Our process surfaced roughly $400 million in fixable problems coming straight from the people who knew what needed to be prioritized.
2. Top-Down Initiatives Can't Reach the Floor They're Meant to Fix
Pointing the company in a direction is leadership's job. The problems show up when the fix itself is designed at the top and pushed down.
An improvement initiative (e.g.: an operational-excellence office, a reengineering push, a transformation program) gets a budget, a timeline, and a leader. It targets what leadership can already see: the escalations, the dashboard metrics, the problems that survived the trip upstairs. Then it travels downward. Leadership designs it, managers cascade it, the frontline receives it. But the knowledge that would actually fix the operation is sitting at the bottom, and it has to move up to be useful.
A program running top to bottom can't surface what's underneath it, and by the time it reaches the floor, it's often just one more system to log into and one more meeting to sit through.
A return nobody can trace isn't a return
Top-down programs get approved on numbers that sound clean: costs a million, returns a million and a half. But no one traces how that return actually shows up in the general ledger, which positions, which hours, which line items really change.
A lot of the time the "savings" turn out to be 3% of everyone's time; real working hours, scattered across hundreds of people. That loss is invisible on the P&L.
The technology was never the hard part
A few years back, the leadership team of a large consumer-products company decided their operation needed a major new system. They scoped the project, approved the budget, set the timeline, and kicked it off all from the top.
What they didn't do was ask the people who'd actually run the system every day what might go wrong with it.
Plenty would have gone wrong, and plenty did. We sat in on a meeting with that leadership team partway through the rollout, and one executive had to join by speakerphone from the road. He was driving customer to customer, apologizing in person, because the new system was scrambling their orders. Exactly the kind of breakdown the people who'd use it daily tend to see coming long before anyone at the top does.
These weren't careless people. They were smart, capable, and well-meaning. The hard part of a project that size is that the decision gets made several levels above the people who'll live with the result—and those are the only people who actually know where it's going to break.
That's a big part of why projects this size miss the mark 70% of the time.
3. Big Bets Fly Right Over the Small Stuff
Then there's the big bet, the bold goal, the Big Hairy Audacious Goal, the transformation everyone can rally behind. There's nothing wrong with ambition, and a clear direction is a good thing. The risk is that a bet that size asks the whole company to commit before anyone has learned what's actually true on the ground.
Most leadership teams know, somewhere, that bets this size usually disappoint. They just assume the odds are about other companies, that their team is sharp enough to be the exception. So the bet gets made on confidence instead of evidence.
And once it's announced, the company is committed. Every milestone and budget cycle raises the cost of changing course, so the bet tends to keep rolling forward long after the floor could have told you it wouldn't fly. It turns into a zombie, the kind of project that should have been killed or reshaped a year ago and somehow keeps lumbering forward.
Meanwhile the goal shrinks into a number on the way down: "be the most efficient operation in the sector" becomes "cut 15% of costs," which becomes "do more with less."
The broken process still doesn't get fixed. The frontline just carries more weight on top of the same system.
Singles and doubles beat the grand slam
Here's the part that surprises people: the biggest results we've ever seen came from surfacing a thousand small, specific, fixable problems and working them all at once.
Run at scale, singles and doubles beat the grand slam, because the grand slam sails right over the small stuff that's quietly draining the operation every day.
The People Closest to the Work: The Place Consultants, Top-Down Initiatives, and Big Bets Never Look
There's one place none of these approaches looks: at the people who run the operation every day.
They already know where it's breaking, and most of them have known for a while. So why doesn't what they know ever surface on its own?
This isn't for lack of trying. Most leaders have run engagement surveys, held town halls, set out suggestion boxes, and scheduled skip-levels. But none of those tools was built to carry a specific operational problem from the people who see it to the person who can fix it, and none was ever going to reach the 80%+ of frontline workers who don't sit at a desk or have a company email.
The effort companies put into improving is real, but it usually hits a ceiling of scale, speed, and reach. The knowledge stays put because there’s just no mechanism built to move it.
So what happens when a company finally builds a way to move that knowledge—when it stops looking up and out and goes straight to the people doing the work?
We've watched it happen.
One large company we worked with put the question to its own employees: what would you fix? In 40 days, they came back with more than 6,000 specific ideas worth a combined $300 million in cost savings and $100 million in new revenue. None of those ideas were new. They'd been sitting in people's heads for years, waiting for someone to ask. The only thing that changed was that, this time, someone did.
And that wasn't a lucky one-off. Going straight to the people who run the operation and drawing out what they already know is the whole idea behind the Idea Harvest™ methodology, and over three decades, it has driven more than $4.5 billion in earnings for Fortune 1000 companies.
Your Operation Already Knows What's Broken
The consultant, the top-down initiative, the big bet, for all their differences, they're the same move: looking up and out for an answer that's been down and in the whole time.
Each has its place, but finding what's broken inside your own operation was never the job any of them was built for. That has always come down to one thing: asking the people who run it every day, and actually hearing what they say.
That's the gap all three leave open: the distance between what your people already know and what reaches the leaders who can act on it. The knowledge is there; the path for it to travel isn't.
That gap is what we built Tell Jules to close.
Jules is a voice AI-powered tool that reaches your frontline employees through a short, structured conversation by phone or text, with no app, no login, and no company email required. Jules turns what they share into a clear report that reaches the person who can act on it. It doesn't surface how people feel; it surfaces what they're seeing.
If you'd like to see what your own people already know, let's talk. We're onboarding a limited number of companies for early access right now.