Margaret, seated near the back, wrote down the comment.
It was exactly the kind of practical lesson the new policy was meant to reinforce.
The airline could not eliminate every conflict.
But it could reduce the number of employees who felt they had to decide, alone and under pressure, whether a powerful passenger was more important than the rules.
Months passed.
The damaged laptop was repaired, and the recovered files were transferred to a new device. Brianna replaced the old computer eventually, but she kept it in a storage cabinet rather than throwing it away.
It reminded her that the most consequential events were not always the ones that appeared on an agenda.
Sometimes, a single moment exposed a weakness that years of reports had failed to make visible.
Garrett paid the documented costs.
He complied with the travel restriction.
He did not receive the commercial agreement he had hoped to secure with Skylark. The procurement process continued independently, but Coleman Meridian’s proposal did not advance. The airline did not make a public announcement about the decision, and it did not attribute the outcome solely to the flight incident.
There were broader commercial considerations, and the proposed agreement had never been finalized.
Still, the experience affected Garrett.
At first, he treated the consequences as an injustice.
He told colleagues that Skylark had become too sensitive. He complained that people no longer understood humor. He argued that powerful companies were increasingly afraid of public criticism.
Some people agreed with him.
Others quietly distanced themselves.
Martin insisted on the management review and began changing how the partnership handled complaints and employee feedback. Garrett resisted the changes, then gradually participated because he did not want to lose his role in the company.
The process was uncomfortable.
He had to listen to employees describe meetings in which they felt humiliated. He had to review complaints he had previously dismissed. He had to confront the possibility that some of his most admired qualities—confidence, speed, forcefulness—had become excuses for refusing to hear criticism.
During one session, an employee named Laura Bennett described a meeting in which Garrett had interrupted her several times before telling the room that her proposal was “not worth the paper it was printed on.”
Garrett remembered the meeting.
He had been frustrated with the proposal. It had contained several errors, and the team had been under pressure to finalize a recommendation before a deadline.
At the time, he had considered his response efficient.
Now, as Laura described how the comment had affected her, he began to understand the difference between criticizing the work and humiliating the person who produced it.
“You could have told me the figures were wrong,” Laura said. “You could have explained what needed to be corrected. Instead, you made it sound as though my presence in the room was a mistake.”
Garrett felt defensive.
He wanted to explain the deadline, the financial risk, and the fact that her proposal had required substantial revision.
But Martin had asked everyone in the room to let the employee finish before responding.
So Garrett remained silent.
Laura continued.
“I didn't stop making mistakes after that meeting. I stopped volunteering ideas. I stopped asking questions when I wasn't sure. I thought it was safer to stay quiet.”
That was not the result Garrett had intended.
He had wanted better work.
Instead, he had created an environment in which a capable employee became reluctant to contribute.
He found that realization uncomfortable.
He also found it difficult to dismiss.
The review continued for several weeks.
Garrett did not transform overnight.
There were moments when he reverted to old habits. There were meetings in which he interrupted people, and there were disagreements he initially treated as personal challenges.
But now someone occasionally asked him to stop and explain his reasoning.
Sometimes, he became angry.
Sometimes, he listened.
The first genuine change came several months after the flight, during a meeting with a junior analyst named Peter Wallace.
Peter had prepared a financial model for a property acquisition. Garrett reviewed the spreadsheet and found an error in one of the assumptions.
“This is basic,” he said. “How did you miss something like this?”
Peter’s face reddened.
The room became quiet.
Garrett felt the familiar satisfaction of taking control of a meeting. He had identified a mistake, and everyone now knew that he had seen it. The atmosphere had shifted in his favor.
He could have continued.
He could have listed every weakness in the presentation and made Peter defend each decision under the scrutiny of the room.
Instead, something stopped him.
He remembered the investigation interview.
What point were you trying to make?
He remembered how difficult it had been to answer that question honestly.
He looked again at the spreadsheet.
“The assumption in this section is wrong,” he said.
Peter nodded quickly.
“Yes, sir. I see it.”
“Can you explain how you arrived at it?”
Peter opened the source file and walked through the calculations.
The error came from an outdated figure in the reference material. Peter had failed to update the source when he revised the model. The mistake was real, and it affected the projected return.
Garrett could have dismissed him.
Instead, he asked Peter to correct the assumption and run the model again.
“Check whether the change affects the acquisition recommendation,” Garrett said. “Then bring me the revised version.”
Peter nodded.
“I will.”