top of page

The Cost of Seeing What the Organization Wants to See

Writer: Derik Robinson
Derik Robinson
Sep 1
9 min read

Six catastrophes. One recurring failure. Reality was visible before it became expensive.


The catastrophe usually arrives late


The meeting before the disaster rarely feels historic.


The dashboard is green enough. The risk is contained enough. The deadline is close enough. Someone close to the work has concerns, but those concerns are softened as they move upward. A warning becomes a caveat. A caveat becomes a watch item. A watch item disappears behind a metric that still looks acceptable.


Then reality collects the balance.


Over the last decade, some of the most consequential organizational failures did not begin because nobody knew. They began because the organization could not convert what people knew into what leadership was willing to see. Engineering evidence competed with schedule pressure. Maintenance history competed with cost and continuity. Resident warnings competed with institutional confidence. Frontline behavior competed with executive narratives. Technical dissent competed with urgency. A routine software release competed with the true scale of downstream dependency.


An execution failure is something the organization did wrong. A perception failure is the system that allowed the organization to believe it was still right.

This distinction matters because organizations usually respond to catastrophe by fixing the final mechanism. They revise a checklist, replace a component, add an approval, retrain a team, or fire an executive. Those actions may be necessary. They are not sufficient when the deeper problem is how the organization forms, protects, and corrects its view of reality.


Six breakdowns that made perception measurable


The following cases are not identical, and they should not be flattened into one moral. Some involved misconduct. Some involved weak governance. Some involved technical failure. Some involved fragmented public and private accountability. The organizational perception lens is an interpretation of documented findings, not a substitute for those findings. What connects the cases is the distance between available reality and accepted reality.


1. Boeing 737 MAX: when certification confidence outran system truth


Two 737 MAX aircraft crashed in October 2018 and March 2019, killing 346 people. The United States Department of Justice later charged Boeing with conspiracy to defraud the Federal Aviation Administration Aircraft Evaluation Group. The 2021 resolution required more than $2.5 billion, including a $243.6 million criminal penalty, $1.77 billion for airline customers, and a $500 million crash victim beneficiaries fund.


The financial figure is already enormous, but it still understates the consequence. The aircraft was grounded globally. Airlines lost capacity. Families lost 346 people. Boeing lost trust with regulators, customers, employees, and the flying public. Years later, the company remained under scrutiny over whether its safety and quality systems could reliably surface reality before schedule or commercial pressure defined it.


The perception breakdown was not simply that one technical system behaved unexpectedly. It was the gap between what parts of the organization understood about the Maneuvering Characteristics Augmentation System, what regulators and pilots were allowed to understand, and what the enterprise treated as acceptable program risk. Information existed. Organizational confidence filtered its meaning.


2. PG&E and the Camp Fire: when an asset register becomes a false sense of control


On November 8, 2018, PG&E equipment ignited the Camp Fire. California regulators report that the fire burned about 153,336 acres, destroyed 18,804 structures, and caused 85 deaths. PG&E later pleaded guilty to 84 counts of involuntary manslaughter. The California Public Utilities Commission imposed penalties totaling $2.137 billion, while the company entered bankruptcy under the weight of wildfire liabilities.


The physical failure was a worn transmission component. The organizational failure was larger. State investigators found that PG&E could not determine when, or even whether, relevant maintenance and inspections had occurred on the Caribou Palermo line. The failed component showed wear accumulated over a long period. Similar severe wear was found on another tower. Records, inspections, maintenance priorities, and risk classification did not combine into an accurate picture of asset condition.


The community impact cannot be represented by an insurance ledger. Paradise was physically destroyed. Homes, businesses, schools, infrastructure, tax base, social networks, and individual histories disappeared together. Financial loss was concentrated on a company. Human and economic disruption was distributed across an entire region.


3. Grenfell Tower: when residents can see what institutions cannot


Seventy two people, including 18 children, died in the Grenfell Tower fire in London on June 14, 2017. The final public inquiry described a chain of failures across government, regulators, testing bodies, manufacturers, contractors, the building owner, its management organization, and the fire service. The United Kingdom government later characterized the tragedy as the product of systemic failures requiring reform across construction products, regulation, and institutional accountability.


This was perception fragmentation at its most lethal. Each participant held a portion of the reality. Manufacturers understood product behavior. Contractors made design and installation decisions. Regulators operated inside a weakened assurance regime. Managers knew residents had concerns. Residents understood the lived condition of the building. No accountable system assembled those perspectives into a reality strong enough to stop the danger.


The human consequence was 72 lives. The community consequence extended through displacement, trauma, distrust, long term health concern, and the destruction of confidence in institutions that existed to protect residents. The economic consequence moved far beyond the tower through remediation of unsafe cladding across the country, housing disruption, public inquiry costs, legal exposure, and years of delayed redevelopment.


4. Wells Fargo: when the metric becomes more real than the customer


Wells Fargo's sales practices scandal became public in 2016 after employees opened millions of unauthorized accounts under intense sales pressure. In 2018, the Federal Reserve imposed an unprecedented asset growth restriction because the bank had prioritized growth without effective management of key risks, preventing serious compliance breakdowns from being properly escalated to the board. The restriction remained until June 2025. In a separate 2022 action, the Consumer Financial Protection Bureau ordered Wells Fargo to pay $3.7 billion for widespread mismanagement affecting more than 16 million consumer accounts, including customers who lost vehicles and homes.


The organizational perception failure was built into the scorecard. The system treated product volume as evidence of customer value and employee performance. Frontline misconduct was visible through complaints, terminations, exceptions, and impossible sales patterns, yet the institution continued to perceive the problem as individual behavior instead of a predictable output of its own design.


The human cost landed on customers and employees. Customers absorbed fees, credit damage, repossessions, foreclosures, and time spent correcting problems they did not create. Employees operated in a system where preserving employment could conflict with serving the customer. The financial cost included penalties, remediation, legal expense, leadership turnover, constrained growth, and a reputation that took nearly a decade of corrective work to begin repairing.


5. East Palestine: when urgency excludes dissent


A Norfolk Southern freight train derailed in East Palestine, Ohio, on February 3, 2023. The National Transportation Safety Board found that an overheated wheel bearing caused the derailment. It also found that Norfolk Southern and its contractors failed to communicate relevant expertise and dissenting opinions to the incident commander. The risk of catastrophic tank failure was inaccurately represented, creating urgency that led to the unnecessary vent and burn of five vinyl chloride tank cars.


No fatalities or injuries were officially reported from the derailment, and up to 2,000 residents were evacuated. That fact should not be used to shrink the impact. Residents faced disruption, uncertainty about exposure, property concerns, business losses, and a lasting trust deficit. The community became the operating environment for a decision made with incomplete and distorted perception.


The critical lesson is uncomfortable. Under pressure, more information does not automatically create better perception. If dissent cannot reach the decision owner with its meaning intact, urgency becomes a filter. The organization can be surrounded by expertise and still act as though only one version of reality exists.


6. CrowdStrike: when a small technical change carries global consequence


On July 19, 2024, a faulty CrowdStrike content update caused Windows systems to crash around the world. Microsoft estimated that 8.5 million Windows devices were affected. That represented less than one percent of Windows machines, yet the consequences spread through airlines, hospitals, banks, emergency services, retailers, manufacturers, and government operations. Parametrix estimated approximately $5.4 billion in direct losses for United States Fortune 500 companies, excluding Microsoft.


The number of affected devices can make the event look statistically small. The dependency map makes it look entirely different. A narrow release path touched organizations whose systems carried essential services. Scale was not the count of machines. Scale was the concentration of consequence behind those machines.


This case exposes a modern perception problem. Organizations routinely inventory technology by asset, vendor, or application. They often fail to perceive the full operational dependency behind each component. A software update is therefore classified as a technical change when it is actually a distributed business event with human, financial, and societal exposure.


The balance sheet records only the easiest part


Across these six cases, the financial figures reach tens of billions of dollars. They include penalties, compensation, settlements, remediation, bankruptcy costs, business interruption, constrained growth, insurance loss, and recovery expense. Those are the costs organizations can count.


The larger cost structure is harder to close:


  • Financial impact. Direct loss compounds into financing cost, insurance pressure, delayed growth, diverted capital, executive turnover, regulatory oversight, customer attrition, and years of remediation. The original failure consumes resources long after the initiating event ends.

  • Human impact. Deaths are the most irreversible outcome, but harm also includes injury, trauma, displacement, job pressure, moral injury, damaged credit, lost housing, interrupted care, and the exhaustion of people forced to repair an institution's mistake.

  • Community and economic impact. A catastrophic failure can erase homes, interrupt transportation, close local businesses, reduce property values, burden public agencies, destabilize labor markets, and destroy trust in institutions. The organization recognizes an incident. The community inherits a new reality.


This is why a narrow return on investment calculation is inadequate. The cost of inaccurate organizational perception is not simply the loss attached to the event. It is the total value destroyed while the organization continues operating from a reality that is no longer true.


Reality does not disappear when an organization fails to recognize it. It moves downstream, compounds, and returns as consequence.

What the cases reveal before catastrophe


Different industries produced the same operating signatures.


  • Confidence substituted for verification. Leaders treated prior success, certification, reporting, or routine process as proof that the current system remained safe.

  • Metrics compressed reality. A target, status, incident rate, asset record, or device count became the accepted picture even when the lived system was more complex.

  • Bad news lost force as it traveled. Warnings were delayed, localized, reframed, or disconnected from decision authority.

  • Ownership was fragmented. Many parties controlled pieces of the system, while nobody owned the combined consequence.

  • The organization measured activity instead of exposure. Inspections, approvals, tests, sales, releases, and reviews were counted without proving that the underlying risk had changed.

  • Correction began after public consequence. External investigators, regulators, courts, customers, and communities forced the organization to acknowledge a reality its own systems had not resolved.


The executive question is not whether the dashboard is accurate


A dashboard can be numerically accurate and organizationally false. It can report every selected metric correctly while excluding the relationships, delays, pressure, dissent, and downstream effects that determine what those metrics mean.


The better questions are more demanding:


  • What reality can frontline teams see that senior leaders cannot?

  • Where does information lose urgency, context, or ownership as it moves upward?

  • Which metric currently allows us to feel safer than the system actually is?

  • What consequence sits outside the boundary of the team making the decision?

  • Which dissenting view has not been disproven, only overruled?

  • What would have to be true for our current confidence to be wrong?


These questions do not eliminate risk. They expose the architecture through which risk becomes invisible.


Organizational perception is an operating requirement


The lesson from the last decade is not that leaders should predict every catastrophe. That is impossible. The requirement is that an organization must be able to recognize when its internal picture is diverging from operating reality, especially when the people closest to the consequence are already signaling the gap.


That requires more than transparency as a value statement. It requires decision systems that preserve context, connect functions, elevate dissent, trace downstream impact, and test whether reported completion changed the underlying condition. It requires leaders who do not confuse confidence with control.


An organization begins paying for inaccurate perception long before the invoice arrives. It pays through ignored maintenance, normalized workarounds, employee silence, customer friction, accumulated exposure, false assurance, and decisions made inside boundaries that consequence will not respect.


By the time the cost appears in a court filing, an earnings report, a casualty count, or a destroyed community, the organization is not discovering the failure. Everyone else is discovering how long the organization failed to see it.


Organizations cannot intentionally improve realities they do not accurately perceive.

The work, then, is not to make every leader omniscient. It is to design an organization in which reality has a reliable path to authority before consequence becomes the messenger.


Sources and notes
















Method note: Cases were selected from events occurring or becoming publicly consequential between August 2016 and August 2026. Financial values are not additive because they represent different categories, periods, and estimation methods. The organizational perception analysis is OPSLEAD AI's synthesis of the cited public findings.


 
 
 

Recent Posts

See All

Comments


bottom of page