There's an old joke that a consultant is someone who borrows your watch to tell you the time. It lands because it is often true: companies pay outside firms a fortune to hand back a polished version of what their own people already knew.
The same blind spot sits 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 is broken. Each one has its place. Yet none of them was built to capture what the people closest to the work already know. All three have you looking up and out, when what you are after has been down and in all along.
There are rare cases where bringing in a consultant makes sense: when you need real expertise that does not exist in the building, and renting it is smarter than building it. When that is the job, a consultant is the right call.
The trouble shows up when you hire an outside firm to find what is 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 is 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 that same view, or a standardized template for how a company like yours should run.
That is how you end up paying a small fortune for someone to borrow your watch and tell you the time.
When an outside firm does not 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. It cannot tell you why you land there. It does not 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.
However the benchmark lands, it rarely moves anything. If it puts you behind the average, it is fair to wonder whether the comparison even holds up, because different companies count these things differently. If it puts you ahead, it is easy to feel reassured.
Being the best in your industry is a different thing from 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 is slowing this operation down, and where?
We once followed a big-name firm into a company it had spent months benchmarking. The firm left behind a thick binder of recommendations. Years later, that same binder landed on our desk as a "starting point," and not one of them 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 had skipped: we asked the people inside. Our process surfaced a long list of fixable problems, far more than the binder ever found, straight from the people who knew what needed to be prioritized.
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, whether an operational-excellence office, a reengineering push, or 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 floor 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 rarely surface what sits underneath it, and by the time it reaches the floor, it is often one more system to log into and one more meeting to sit through.
Top-down programs get approved on numbers that sound clean: costs a million, returns a million and a half. Yet 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 stays invisible on the P&L.
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 skipped was asking the people who would 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. That is exactly the kind of breakdown the people who use a system daily tend to see coming long before anyone at the top does.
These were smart, capable, well-meaning people. The hard part of a project that size is that the decision gets made several levels above the people who will live with the result, and those are the only people who know where it is going to break.
That is a big part of why projects this size miss the mark 70% of the time.
Then there is the big bet: the bold goal, the Big Hairy Audacious Goal, the transformation everyone can rally behind. There is 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 is 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 own team is sharp enough to be the exception. So the bet gets made on confidence instead of evidence.
Once it is 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 would not fly. It becomes a zombie, the 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 goes unfixed. The floor just carries more weight on top of the same system.
Here is the part that surprises people: the biggest results we have seen came from surfacing many 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 quietly drains the operation every day.
There is one place none of these approaches looks: at the people who run the operation every day.
They already know where it is breaking, and most of them have known for a while. So why does what they know so rarely surface on its own?
Most leaders have tried hard to hear it. They have run engagement surveys, held town halls, set out suggestion boxes, and scheduled skip-levels. Each of those does a real job. Carrying one specific operational problem from the person who sees it to the person who can fix it is a different job, and it is the one none of them was built for, which is also why they rarely reach the 80%+ of people on the floor who work without a desk or a company email.
The effort companies put into improving is real. It just hits a ceiling of scale, speed, and reach. The knowledge stays put because there is 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 have watched it happen. One large company put the question to its own people: what would you fix? In a matter of weeks, they came back with a long list of specific ideas, spanning cost savings and new revenue, far more than anyone expected. Every one of those ideas already existed. They had been sitting in people's heads for years, waiting for someone to ask. The one thing that changed was that, this time, someone did.
It happens again and again. 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 real earnings gains for Fortune 1000 companies.
The consultant, the top-down initiative, the big bet, for all their differences, are the same move: looking up and out for an answer that has been down and in the whole time.
Each has its place. Finding what is 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 is 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. What it needs is a path to travel.
That path is what we built Tell Jules to be. With Tell Jules, the people closest to the work join a short, structured conversation, by phone or through a link the company shares. That is all it takes. Tell Jules turns what they share into a clear report that reaches the person who can act on it, and it surfaces what your people see in the work: the specific problems and the fixes they already have in mind.
Run a free trial with 25 to 50 employees and see it for yourself. You pick one team, your people join Tell Jules at their convenience, and the specific problems and the fixes they would make come back ready to triage.
Discover how an operational intelligence loop can bridge the gap between frontline insights and decision-makers, enhancing your company's efficiency...
Discover how the Idea Harvest methodology and AI tool Jules can bridge the Iceberg of Ignorance, empowering frontline workers to share crucial...
Discover how traditional employee feedback methods obscure operational issues. Learn to capture insights directly from your team with Tell Jules for...