Why Communication Fails Before Companies Do: What Business History Tells Us About Treating Communication as Overhead

If you're an internal communications leader right now, there's a reasonable chance you've had some version of this conversation recently: the budget got tightened, the headcount got cut, or someone in finance decided that the company's existing stack, SharePoint, ServiceNow, Workday, or whatever enterprise system already has a seat at the table, is "good enough" for employee communication. Why pay for a dedicated platform when the intranet already technically exists?

It's a familiar pressure. In times of economic uncertainty, communications is often one of the first places organizations look to cut or consolidate. It's treated as a support function, not a strategic one. And so comms teams end up trying to reach a workforce of thousands through tools built for document storage, IT ticketing, or HR workflows. The information gets published somewhere. Whether it reaches anyone is a different question.

We hear this directly, and often. Internal communications leaders across industries consistently describe being under-resourced, under-funded, and perpetually making the case that their function deserves real investment. Many run their entire operation on tools their organizations never intended for communication in the first place. The result is that reaching frontline workers, driving alignment around strategy, and getting critical information to the people who need it all becomes harder, slower, and more fragile than it should be.

This piece is a response to that pattern. Because the assumption that communication can be deprioritized, consolidated into a secondary tool, or treated as a budget line to trim in a difficult quarter, isn't just organizationally frustrating. It's historically dangerous. Every time an organization makes that bet, it's betting that the information people need to do their jobs will find its way to them anyway, through hallway conversations, email chains, manager updates, intuition. It's betting that communication is overhead on top of the real work, rather than the substrate that makes the real work possible.

Business history keeps showing us what happens when that bet goes wrong.

The pattern is remarkably consistent. The information almost always exists somewhere in the company. It just doesn't reach the people who need it, in the form they need it, in time to act on it. That's not a knowledge problem. It's a transmission problem. And it has quietly ended more companies than any market downturn or disruptive competitor on its own.

Here's what that looks like across five of the most documented cases in modern business history.

Kodak invented the thing that killed it

In 1975, a Kodak engineer named Steven Sasson built the world's first digital camera. It was the size of a toaster, took 23 seconds to capture a black-and-white image, and stored it on cassette tape. It was also, unmistakably, the future.

When Sasson demonstrated it to leadership, the reaction he described was one of "curiosity and skepticism." The camera was patented but never put into production. Digital threatened the film business, which was the most profitable thing Kodak had ever done. Kodak's marketing department, as later reporting confirmed, was not interested in the prototypes. The information existed inside the company. The technology existed inside the company. The strategic implications were obvious to the people who built it. None of that knowledge was allowed to travel between the labs and the strategy meetings. It got walled off because it was inconvenient.

By the time Kodak's leadership was ready to communicate honestly across functions about what digital meant, the market had moved past them. Kodak filed for bankruptcy in 2012.

Kodak didn't fail because it didn't know. It failed because what it knew couldn't move.

Nokia knew it was losing. Nobody would say it out loud.

A 2015 study by researchers Timo Vuori and Quy Huy, published through INSEAD, looked at why Nokia, the dominant mobile phone maker on Earth, lost the smartphone race so completely. The study involved 76 interviews with Nokia's top and middle managers, engineers, and external experts. The answer wasn't that Nokia's engineers couldn't see what was happening. They could. By the late 2000s, plenty of people inside the company understood that Symbian, Nokia's operating system, couldn't compete with iOS or Android.

What the researchers found was a culture where bad news didn't travel up. Middle managers feared the reaction of senior leadership and softened what they were hearing from below. Senior leaders, in turn, communicated unrealistic expectations downward and assumed silence meant things were on track. The INSEAD researchers concluded that "a culture of fear stifled communication and innovation, rendering the company unprepared when new smartphone entrants reshaped the sector." Engineers who knew the truth told it to each other in quiet conversations. They did not tell it to the people making the decisions.

Nokia's market capitalization fell from roughly $250 billion at its peak to a fraction of that. Microsoft eventually bought the phone business and wrote most of it off within two years.

The technology was salvageable. The communication culture wasn't.

Blockbuster passed on Netflix for $50 million

In early 2000, Reed Hastings and Marc Randolph flew to Dallas to offer Blockbuster the chance to buy Netflix for $50 million. Blockbuster, then a $5 billion company with thousands of stores, declined. The widely-reported version of the story focuses on the meeting itself. But the more instructive part is what happened inside Blockbuster afterward.

Internal voices, including the company's own digital strategy team, repeatedly pushed for a more aggressive online and subscription-based response. John Antioco, the CEO at the time, eventually launched Blockbuster Online and dropped late fees, which were two of the most important strategic moves the company ever made. He was forced out partly because those moves conflicted with the financial expectations of activist investors, whose picture of the digital threat was filtered through executives who wanted the disruption to be smaller than it was.

The signals were inside the company. The analytical capability was inside the company. Customer behavior data was inside the company. The communication infrastructure to make those signals impossible to ignore at the board level was not. Blockbuster filed for bankruptcy in 2010.

A $50 million decision became a multi-billion-dollar one because the right information lost the internal argument.

Sears had the digital playbook a decade before Amazon

In 1984, Sears was one of the largest retailers in the United States. That same year, it launched a joint venture called Trintex with IBM and CBS, later renamed Prodigy, an early online service that offered home shopping, news, banking, and email. Sears was, in 1984, in a better position to define digital commerce than almost any company on the planet.

Inside Sears, the people working on Prodigy understood what it could become. Inside Sears, the people running stores and catalogs treated it as a side project that risked cannibalizing the core business. The two groups did not communicate effectively about strategy, capital allocation, or customer behavior. IBM and Sears ultimately invested more than $1 billion in Prodigy before selling it off in 1996 at a fraction of that. By the time Amazon launched in 1994, Sears had already let its information advantage evaporate, not because the world changed too fast, but because its own divisions couldn't share what they were learning.

Sears filed for bankruptcy in 2018. Amazon's market cap crossed $2 trillion.

BlackBerry's engineers knew. So did its CEOs. Separately.

When the iPhone launched in 2007, BlackBerry was the dominant enterprise smartphone. Its co-CEOs publicly dismissed the iPhone's significance. Co-CEO Jim Balsillie reportedly told co-founder Mike Lazaridis, "It's okay, we'll be fine." They believed BlackBerry's business customers would never abandon a physical keyboard for a glass screen, and that the iPhone wasn't secure enough for enterprise use.

What's less visible in that narrative is what was happening internally. RIM's own engineers were actively building what they called the "A.K.", an internal code name for "Apple Killer," a touchscreen BlackBerry. The engineers saw the threat. Leadership had a different narrative for the public, for the board, and for themselves.

The two realities never reconciled in time to drive a coherent product response. The result was the BlackBerry Storm, a rushed touchscreen device that was so buggy it had, by one account, a nearly 100% return rate. The platform war was effectively over before the company's internal picture of reality matched what its engineers had been saying for two years.

The company's hardware business ended within a decade of being on top of the world.

The pattern these cases share

These five stories span different decades, different industries, and vastly different competitive contexts. What they have in common is not bad strategy or bad people. In each case:

• The relevant information existed somewhere inside the organization
• The organizational structure, culture, or incentives prevented it from reaching decision-makers intact
• By the time the decision-makers had an accurate picture, the window had closed

This is the pattern. Not ignorance. Transmission failure.

What this looks like at everyday scale

Most companies will never have a Kodak moment. But the same dynamic plays out, scaled down, in nearly every organization every day.

A frontline manager spots a customer behavior shift that never reaches merchandising. A field engineer flags a defect pattern that never reaches design. A salesperson loses three consecutive deals to the same competitor objection that never reaches product marketing. A new policy rolls out without the people enforcing it understanding the reason behind it. A new hire spends their first week searching for documents that exist somewhere but can't be found anywhere they look.

None of these are dramatic. None of them make the case study. But they compound.

McKinsey's research found that knowledge workers spend nearly 20% of the workweek searching for internal information or tracking down colleagues who can help. That's one full day a week, per employee, lost to information that exists but can't be reached. According to Gallup's 2026 State of the Global Workplace report, only 20% of employees globally are engaged at work, a five-year low, and one of the strongest predictors of engagement is whether people feel informed and connected to their organization's purpose. Among frontline workers, the 80% of the global workforce that doesn't sit at a desk, only 22% feel their work is important to the company vision. That isn't a disposition problem. It's a transmission problem.

The cost isn't hypothetical. Gallup estimates global disengagement now costs the world economy $10 trillion annually in lost productivity.

So what do you actually do about it?

Identifying the pattern is useful. Knowing what to do about it is more useful. Here's how organizations that take communication seriously actually operate differently.

Treat information access as infrastructure, not administration

The companies that avoided the Kodak and Nokia fate tend to share a structural trait: they design their organizations so that signals from the edges reach the center quickly and intact. That means more than having open-door policies. It means building actual systems for information to flow.

In practical terms, this looks like:

• Unified communication channels that reach every employee, including those without a desk or a company email, so that when something important needs to be said, it actually reaches everyone it needs to reach
• Searchable, centralized knowledge so that when someone needs to know something, they can find it without asking three people and waiting two days
• Feedback loops that make it structurally easy for frontline teams to surface what they're seeing, and structurally visible when that input gets acted on

The goal isn't more communication. It's more signal, less noise, and less distance between where information originates and where decisions get made.

Measure what you can, name what you can't

One reason communication gets cut before other functions is that its value is hard to quantify in advance. But it's not impossible to measure.

Organizations can track and report on:

• Reach and readership on internal communications: who actually received and opened a message, and how many acknowledged it
• Information-search time: how long employees spend looking for things they need to do their jobs, and where the biggest gaps are
• Adoption rates after policy changes or process rollouts: the gap between "we communicated this" and "people actually understood and applied it" is usually where the cost lives
• Engagement scores over time, segmented by team and location, with communication frequency and quality as an input variable

The $10 trillion Gallup figure and McKinsey's 20% time-loss estimate are both useful for executive conversations because they put a dollar frame on what is normally treated as a soft concern. If a company has 5,000 employees earning an average of $60,000 per year, McKinsey's estimate implies roughly $6 million in annual productivity lost to information-search alone. That's a real number, and it's the kind of number that makes the budget case for communication infrastructure.

Build the business case in terms leaders actually respond to

Communications professionals often make the mistake of arguing for their function in terms of outputs: newsletters sent, announcements posted, videos produced. Executives don't fund outputs. They fund outcomes.

The business case for communication and information access infrastructure needs to be built in the language of risk and return:

Risk framing: What is the cost of a product launch where field teams aren't aligned on messaging? What is the cost of a compliance failure because a policy update didn't reach the people responsible for it? What is the cost of losing a senior employee whose institutional knowledge walks out the door with them? These are measurable costs that communication infrastructure directly reduces.

Return framing: What is the value of a 10% improvement in employee engagement? Gallup's research consistently links higher engagement to lower turnover, higher productivity, better customer satisfaction, and fewer quality incidents. What is the value of cutting information-search time by half? That's real hours redirected to actual work.

For organizations evaluating a communication or workforce platform investment, MangoApps' Business Case and ROI Guide includes calculators and a presentation template purpose-built for making this argument to finance and executive stakeholders. It's designed to help communications and HR leaders translate platform value into the business terms that move budgets.

Reach the whole workforce, not just the people at desks

Most enterprise communication infrastructure was built for knowledge workers. It assumes employees have a company email address, a laptop, and access to the intranet. For companies with significant frontline workforces, that assumption excludes the majority of the people the organization depends on.

Healthcare systems where nurses don't sit at computers. Retail chains where store associates don't have company emails. Manufacturing facilities where the shift supervisor is the primary information channel for everyone on the floor. In these environments, the gap between "we published an update" and "our people know about the update" is enormous, and closing it requires a different kind of infrastructure.

The practical answer is a mobile-first employee app that reaches every worker, regardless of whether they have a desk or a company email. Not a consumer messaging tool repurposed for work, but a purpose-built channel with the ability to target communications by location, role, shift, and department, with analytics that show who received, opened, and acknowledged what.

This isn't a nice-to-have. In frontline-heavy industries, it's the difference between a safety update that reaches every worker in the building and one that gets posted in the break room and seen by whoever happens to walk past it.

Make knowledge findable before it walks out the door

Every time an experienced employee leaves an organization, knowledge leaves with them. In most companies, there's no system for capturing what that person knew, which customers they understood, which processes they had internalized, which workarounds existed for problems the organization doesn't even know it has.

This is the slow version of the Kodak problem. The information existed. Nobody built the channel to move it from inside someone's head into a place where others could find it.

Practical knowledge management looks like:

• A searchable knowledge base where institutional knowledge gets documented and maintained, not just filed
• AI-assisted discovery that can surface relevant information without requiring employees to know exactly what to search for
• Clear ownership so that knowledge base content doesn't go stale while the person who wrote it is still around to update it

MangoApps' ROI Report examines the quantified impact of unified knowledge management, including reductions in time-to-competency for new hires, decreases in repeated questions, and improvements in policy compliance. These aren't soft benefits. They're measurable, and they compound over time.

Making the internal argument

If you're a communications or HR professional trying to make the case for communication infrastructure investment, here are the most effective frames for different audiences.

For the CFO: Lead with the McKinsey 20% figure, apply it to your headcount and average salary, and show the annual dollar figure of time lost to information-search. Then show what a 30-50% improvement in that number would return. Frame the platform investment against the productivity recovery, not against the communications budget.

For the CEO or COO: Use the Nokia and Blockbuster stories directly. Ask: if the signals your frontline teams are seeing right now aren't reaching this room, how would you know? The inability to answer that question confidently is the business case.

For the CHRO: Lead with engagement. Gallup's 20% global engagement figure, combined with the $10 trillion productivity cost, makes a powerful argument for the organizational cost of disconnection. Show how communication infrastructure is a prerequisite, not a supplement, for any engagement improvement initiative.

For IT/Operations: Frame around consolidation and security. Most organizations are running multiple overlapping communication tools, none of which reach everyone, none of which talk to each other, and none of which have enterprise-grade analytics. A unified platform with proper security and compliance posture reduces risk while improving reach.

The test every organization should run

Here is a simple diagnostic. Ask your leadership team these four questions:

1. If your most experienced frontline employee observed something important today, how many steps would it take for that information to reach someone with the authority to act on it, and how many of those steps might it not survive?
2. If a critical policy changed this morning, how confident are you that every employee in every location would know about it by end of day?
3. When a new employee joins, how long does it take them to find the information they need to be independently productive, and what does that time cost?
4. When a key employee leaves, what happens to what they knew?

Most organizations, if they answer those four questions honestly, will find gaps they hadn't quantified before. Those gaps are the business case.

Communication is not the overhead. It's the operating system.

The instinct to treat communication as a cost center comes from a reasonable place. Communication outputs are visible in a way that communication infrastructure isn't. You can see a newsletter. You can't see the absence of a rumor that would have spread if the newsletter hadn't existed. You can measure the cost of running an internal communications team. You can't easily measure the cost of the strategic decision that didn't get made because the right signal didn't reach the right room.

But the historical record is not subtle. When information access and internal communication break down, organizations don't just get less efficient. They make wrong decisions with information they already have. They miss markets they saw coming. They ship products their own engineers warned against. They lose people who could have warned them louder.

The work communication professionals do is not decoration on top of the real work. It's the thing that makes the real work possible. It's how a company of 10,000 people behaves like it has one nervous system instead of 10,000 disconnected ones. It's how a frontline employee in a warehouse knows what the executive team decided this morning. It's how a customer signal raised at a checkout counter reaches someone with the authority to act on it.

Every organization is already making the bet, whether it knows it or not, about whether its information will reach the people who need it. The question isn't whether to make the bet. It's whether to fund the infrastructure that makes the bet safe.

The companies that didn't are case studies now.

Ready to build the business case for communication infrastructure at your organization? Download MangoApps' Business Case and ROI Guide, which includes calculators, benchmark data, and a presentation template designed to help you make the investment argument to executive stakeholders. Or explore MangoApps' ROI Report for a detailed look at how unified workforce platforms translate into measurable business outcomes.**