CEO Spent Millions On Jet Engine Repairs With No Results — Then a Single Dad Intern Questioned One Graph

Chapter 17

Theme:
Font Size:
24px

Daniel began to keep a second notebook, one that contained no proprietary records. In it he wrote down questions about how teams dealt with uncertainty, how supervisors invited disagreement, and how engineers learned from unsuccessful tests without humiliating the people who designed them. The notebook was not part of his job description. He hoped someday it might help him teach younger technicians. When he showed Sophie the cover, she wrote a title for him in purple marker: THINGS WE STILL NEED TO LEARN. He left the title there, even though he thought the lettering was too large.

One Friday afternoon a supplier informed Meridian that a specialized component needed for the next controlled comparison would not arrive on the scheduled date. The delay was not catastrophic, but it endangered the plan presented to the board. Victoria called procurement and asked whether another part could be substituted. The engineers said that a substitute might alter the very behavior they were trying to isolate, making a result difficult to interpret. She pushed for options, not shortcuts, and requested a written comparison of cost, schedule, and technical risk. When the report showed that waiting for the specified component was the responsible choice, she authorized the delay. She did not like the decision. That was part of why it mattered.

Daniel expected the postponement to be painful, and it was. A senior manager suggested running an informal test first and completing the paperwork later. Arthur refused, explaining that a useful result required a controlled configuration and documented authorization. The manager complained that the company was being buried in process. Luis replied that the only thing more expensive than an unsuccessful test was a successful-looking test that nobody could interpret. Victoria backed the engineering team and called the customer herself. She described the revised schedule without promising what she could not yet guarantee.

The customer's program director, Helen Cho, was not pleased. She had her own board, engineers, and delivery commitments. During the call she asked whether Meridian had finally identified a genuine root cause or was merely proposing another hypothesis. Victoria told her that the team had separated a test-installation influence from a distinct control-related transient and was preparing to validate the corrective action. Helen asked why that distinction had taken so long. Victoria answered that the company's earlier grouping of events had obscured the evidence. It was an uncomfortable admission, but it kept the discussion honest. Helen agreed to a revised review schedule provided Meridian supplied an independently verified technical report.

That evening Victoria stayed at the plant after most offices emptied. She walked through the quiet corridor of photographs showing engines, teams, and award ceremonies. Behind the glass of a display cabinet lay an old precision gauge her father had used at the stamping factory. She remembered him explaining that measurement instruments had limitations and that a good worker understood them instead of worshipping the number on the dial. She had managed companies for years without needing to know every technical detail. But leadership, she realized, still required understanding how an organization could confuse a number with the truth.

News in the same category

CEO Spent Millions On Jet Engine Repairs With No Results — Then a Single Dad Intern Questioned One Graph

30 Part