Melting The Iceberg of Ignorance: What We Built After 30 Years of Watching It Reform

Part 2 of 2. Read part 1 here.

In 1989, a consultant named Sidney Yoshida observed something at a Japanese manufacturer that business leaders have been citing ever since: frontline workers know about 100% of the operational problems in their organization. By the time that knowledge travels through management layers, only 4% reaches senior executives. He called it the Iceberg of Ignorance.

The iceberg forms because of 3 specific forces working simultaneously inside most large, multi-location operations.

• The first is filtering — information gets edited at every management level as it moves upward, not out of deception, but because the path for difficult news to travel upward was never designed to be frictionless. In most organizations, raising a problem that reflects poorly on your area or your team has rarely been consequence-free, and people remember that.
• The second is learned silence — employees who raised issues and saw nothing happen eventually stop raising them. The knowledge didn't disappear but the willingness to surface it did.
• The third is structural exclusion — more than 83% of frontline workers have no company email address and no intranet access, meaning the channels most organizations use to collect input were never reachable by the people with the most operational knowledge.

Understanding those 3 forces is the first step, knowing what to do about them is the harder part, and it's what this article is about.

What Organizations Typically Do When They Recognize the Visibility Gap

Most leaders who encounter the iceberg problem reach for one of 3 approaches, each of which has genuine logic behind it:

They bring in consultants

Outside experts with permission to talk to everyone, skilled at creating the kind of conversation where people share what they'd otherwise keep to themselves. It makes sense, if the problem is that internal information gets filtered on the way up, bring in people who aren't subject to that filtering.

They launch an improvement initiative

A dedicated team — a VP of Operational Excellence, a reengineering office, a Six Sigma rollout — gets a budget and a timeline. If the operation needs to improve, give the problem a home at the leadership level and drive it deliberately from the top down, right?

They set a BHAGs (Big, Hairy, Audacious Goals)

A bold, long-range ambition that gives the entire organization a direction to align around. If people can see clearly where the company is trying to go, the thinking goes, they'll find their way there.

Why Each of Those Approaches Leaves the Deepest Layers Untouched

Each of the 3 approaches addresses part of the iceberg problem, but none of them reaches all 3 layers. And without reaching all 3, the iceberg reforms.

Outside consultants start at the top too

When a large outside firm comes in, interviews the leadership team, reviews the data on the dashboard, and builds recommendations from there, the floor rarely gets asked. The data they're working from is the same filtered data that already made it through the management chain — the 4% the iceberg left visible.

Or worse, they fill the gaps with benchmarks from other industries and other companies, recommending ideas that the people closest to the work know don't make sense in their particular situation.

And even when they do surface something real, there's a second problem: the people who have to implement it weren't part of finding it. The answer arrived from outside, got handed down, and now someone has to execute a change they had no hand in diagnosing. That's not how buy-in works.

But perhaps the biggest cost is the signal it sends. Bringing in an expensive outside firm to find the answers tells your organization you don't believe they have them. And once people get that message, why would they ever try to give you any?

Top-down initiatives don't reach what's below

An improvement initiative is designed at the top and flows downward. It addresses the symptoms visible at the leadership level: the escalated incidents, the metrics on the dashboard, and the problems that made it through the filter to the 4% the leadership team is aware of.

But the 3 layers of the iceberg are untouched because the initiative moves in the wrong direction. Leadership designs it, managers cascade it, frontline workers receive it. That's top to bottom. But the knowledge that would actually improve the operation — the process workarounds, the invisible waste, the things the floor already knows about — needs to travel the other way.

No initiative that starts at the top and works downward can surface what's sitting at the bottom.

We once worked with a large food manufacturer that was purchasing a key ingredient from an outside vendor every month without knowing another facility inside the same company, a few hundred miles away, had the equipment, the capacity, and the capability to produce that exact ingredient. Nobody at the leadership level knew the connection existed because no one had ever asked both facilities the same question at the same time.

Most people inside an organization are so busy running alongside their bicycle they don't have time to get on it — so fully occupied keeping things moving that stopping to document a structural observation and send it up five levels of management to get it fixed simply isn't on the list.

A top-down initiative adds a new destination without changing the direction information travels.

BHAGs leaves the iceberg frozen

A BHAG tells your organization where it's going but it doesn't tell you what's standing in the way.

And here's what usually happens when a bold goal has to turn into action: it becomes a number.

"Become the most efficient operation in the sector" turns into "cut 15% from operating costs," which turns into “do more with less.”

But the broken process on the floor doesn't get fixed, the workarounds don't get eliminated, and the waste employees already sees doesn't get addressed. The frontline just absorbs more pressure on top of the same system that was already broken.

A bolder goal at the top doesn't change what's frozen at the bottom.

What Reaching All 3 Layers Actually Takes

Now that the gap is clear, the requirements for a solution that actually addresses all three layers become specific:

To reach the filtering layer, a solution has to bypass the management chain entirely — not improve how information travels through it, but go around it. The knowledge has to move from the employee directly to the person with authority to act on it. Any solution that routes insights through managers puts those insights back into the same hands that filter them.

To reach the learned silence layer, a solution has to be proactive — it has to go to employees rather than wait for them to come to it. Every passive tool that asked employees to initiate (to log in, fill something out, decide it was worth trying again) reinforced the learned silence layer every time a submission went without a visible response. You can't reverse that conditioning with another passive tool.

To reach the structural exclusion layer, a solution has to work on a channel that every employee already has, with no login, no app, and no company email required. The tools organizations typically reach for were built for desk-based employees. For the 83% of frontline and shift-based workers without company email access, those tools were never accessible to begin with. The channel has to be one that's already in their lives.

We Built the Tool We Kept Wishing Existed

Thirty years of working inside manufacturing plants, retail chains, banks, and distribution operations taught us one thing above everything else: the answer is almost never the big idea.

Companies reach for big ideas because the big ideas feel like progress. A bold goal, a transformation program, and a major outside engagement feel like serious responses to serious problems, but the improvements that actually moved the needle were almost always small, specific, and already sitting inside the building.

The person who knew what was broken just had no real way to surface it.

That's why we built the Idea Harvest™ methodology — to go to every employee, not just the ones who typically speak up. To ask about problems before asking about solutions and to turn what people share into something specific enough to act on: the problem, the root cause, a proposed fix, and the financial questions worth asking before you move.

It works. The Idea Harvest™ methodology has driven $4.5+ billion in earnings for Fortune 1000 companies over 30 years.

The question we kept coming back to, engagement after engagement, is: what if we could easily reach even more of the people closest to the work — and do it quickly?

That's why we built Tell Jules — a conversational AI that does what we spent 30 years doing by hand.

It uses AI to reach your employees directly on their phones, and asks structured questions designed to surface specific operational problems, not how people feel, but what they're seeing. Every conversation turns into a structured report your team can act on.

How Jules Melts The Iceberg of Ignorance

The filtering layer — Jules goes directly to the source

Employees reach out to Jules directly from their phones.

The conversation follows the same structured framework Harvest Earnings Partners have used for 30 years to surface specific operational problems and ideas, not general sentiment.

What comes out of that conversation goes into a report that reaches the decision-maker directly so the management chain isn't in the loop.

The learned silence layer — the barrier to speaking up disappears

Every passive tool that reinforced learned silence in your organization had the same design flaw: it asked employees to decide it was worth trying again and wait for a response that might never come.

Jules works differently. When something occurs to an employee on the floor, between shifts, or at the end of a long day, they reach out. They don’t need to login or fill out a form. It’s a quick AI-assisted conversation, whenever they have a moment.

Jules asks follow-up questions and makes sure the full picture comes through. She is knowledgeable and interested in what each employee has to say.

The structural exclusion layer — a phone call, not an app, email, or login

There’s no need to download an app or have a corporate email address.

The frontline workers who were never reached by tools built around email and intranet access already have what Jules works with: a phone. The channel that's already in their pocket, already used every day, finally pointed at the right conversation.

What Comes Back Up When Every Employee Actually Gets Asked

What Jules produces isn't a sentiment score or an engagement trend line but a structured report for each idea or problem surfaced with:

• The specific issue the employee identified
• Their proposed solution
• Financial impact and risk-related questions to help assess the value of acting on it
• Recommended stakeholders to collaborate with

Jules reaches the full roster you pick, not just the small group who responds to surveys or the vocal few who speak up in a meeting. Every person on the list gets a call or message, and every conversation gets structured into the same output format. What comes back up is the complete picture, not the version that was filtered, shaped, and narrowed on its way through layers of management.

There's no IT integration required or change management program to run first. You just upload a roster, Jules handles the conversations, and structured reports start arriving within days.

The Knowledge Has Always Been There

In 30 years of surfacing ideas from the people closest to the work, we never once walked into a company where employees didn't know what needed to be improved. The people running the operation always know about broken processes, wasted capacity, and risks absorbed into how things are done.

The problem was that not much of that knowledge had a direct path to the people with the authority to act on it.

Outside firms work from the top down, improvement programs act on what leadership could already see, and bold goals create direction without creating a channel from the bottom. What's always been missing is something that surfaces frontline employee operational knowledge continuously.

That's what Jules is built to do.

If you'd like to see how Jules works inside your organization, let's talk. We're currently onboarding a limited number of companies.