The engine would start normally, run for several minutes, and then trigger an emergency shutdown. The diagnostic system repeatedly reported a harmonic disruption, but the data did not point to a single obvious cause.
The engineers replaced components.
They adjusted the cooling system.
They recalibrated the control software.
They ran diagnostic tests under different loads.
Nothing worked.
The engine continued to fail after fourteen minutes and thirty-seven seconds.
Every time.
The first team attributed the problem to an unstable temperature sensor.
The second suspected the cooling regulator.
The third focused on the software that monitored electromagnetic fluctuations.
All three teams were highly qualified.
Two of the lead engineers held doctorates from major research universities. Another had spent more than a decade developing propulsion systems for industrial applications.
They were not careless or unintelligent.
But each team inherited the assumptions of the team before it.
The sensor had been identified as a potential problem, so engineers concentrated on sensor readings.
The cooling regulator had been flagged in the next report, so the following group focused on the regulator.
The software had generated the error message, so the third team concentrated on the control architecture.
The investigation grew more complicated with every unsuccessful attempt.
New variables were introduced.
Additional components were replaced.
The diagnostic logs became longer.
And the original question—why did the engine fail at the same moment under apparently different conditions?—became buried beneath dozens of narrower questions.
By the fourth week, the atmosphere in the engineering department had changed.
Conversations that had once been collaborative became defensive.
Meetings lasted longer.
Emails became more formal.
People began documenting every decision in anticipation of a future investigation into who had made the wrong call.
Victoria responded by increasing the pressure.
She called emergency meetings twice a day. She demanded progress reports every four hours. She asked the engineers to estimate the probability that each proposed fix would succeed, then criticized them when their estimates changed after new evidence appeared.
During one particularly tense meeting, she stood at the head of the conference table and looked directly at Daniel Reeves.
“Are you telling me that your team cannot fix its own engine?”
Daniel kept his hands folded in front of him.
“We have not yet isolated the cause.”
“That is not what I asked.”
“We have identified several contributing possibilities, but the test data remains inconsistent.”
“The data is not inconsistent. The engine fails at the same time.”
“The shutdown interval is consistent, yes. The conditions leading to it are more complicated.”
Victoria leaned forward.
“Then simplify them.”
Daniel looked at her.
“Engineering does not become simpler because we want it to.”
The room went silent.
Victoria stared at him for several seconds.
Then she smiled without warmth.
“Careful, Daniel. I hired you because you were supposed to solve problems, not explain why they were difficult.”
The meeting ended twenty minutes later, with another deadline and no new diagnosis.
By the fifth week, the company had begun to feel the financial consequences.
A major logistics partner delayed signing its contract until the engine passed validation. Another requested additional performance guarantees. A third warned that it would consider a competing supplier if Tech Vanguard failed to demonstrate a working prototype by the end of the month.
The total value of the contracts at risk exceeded fifty million dollars.
Victoria began sleeping in her office.
She arrived before sunrise, left after midnight, and carried the tension of the crisis into every conversation.
Employees learned to recognize the sound of her heels approaching.
If she walked quickly, someone had made a mistake.
If she walked slowly, she was usually preparing to tell someone that their work was not good enough.
If she entered a room without speaking, everyone immediately wondered what she had heard.
Her reputation had been built on results.
She had joined Tech Vanguard nine years earlier, when the company was a promising startup with a few successful products and a large appetite for expansion. At thirty, she had been the youngest executive on the leadership team.
She was brilliant at identifying market opportunities, aggressive in negotiations, and exceptionally skilled at persuading investors to support ambitious projects.
She could read a room quickly.
She understood how to frame a product as an opportunity before competitors recognized its potential.
She knew when to make a demand, when to offer a concession, and when to leave a negotiation silent long enough for the other person to fill the space.
Under her leadership, Tech Vanguard expanded into new markets and acquired several smaller technology firms.
Revenue grew.
The company's valuation rose.
Her name began appearing in business magazines.
People described her as a visionary.
Some called her ruthless.
Victoria considered both descriptions evidence that she was doing something right.
She had little patience for people who needed reassurance, and even less for those who admitted uncertainty without immediately presenting a solution.
In her mind, leadership meant making decisions while everyone else was still debating the options.
Hesitation cost money.
Emotion clouded judgment.
And failure was acceptable only when it produced a measurable improvement.
The engine crisis threatened all three beliefs.
It had consumed money without producing a solution. It had forced her to delay promises made to investors. And it had placed her in a position where she could not simply make a decision and expect the problem to disappear.
She responded by trying to control everything around it.
That included the people.
Especially the people.
On the morning of the seventh failed test, Victoria summoned the engineering team to the executive boardroom.
The machine was rolled into the room on a reinforced platform, its casing partly removed so that the executives could inspect the components.
The diagnostic monitor displayed the same error.
HARMONIC DISRUPTION DETECTED.
Victoria stood beside the machine.
“Tell me why it failed.”
Daniel looked at the test report.
“The temperature increased beyond the system's safety threshold. The controller detected an abnormal harmonic pattern and initiated shutdown.”
“I know what the report says. I want to know why.”
“We believe the cooling system is not responding to the actual operating conditions.”
“Then replace it.”
“We have already replaced the regulator.”
“Replace it again.”
Daniel's expression tightened.
“We need to establish whether the regulator is the cause before authorizing another replacement.”