PART 11 – Weeks After the Flight, a Difficult Workplace Test Showed Whether the Man Had Truly Changed or Was Merely Protecting Himself

The first meaningful test of the manager's progress arrived on a Wednesday morning, three weeks after the department review began. A major client report contained an error in its supporting figures, and the mistake was discovered less than an hour before the presentation. Under ordinary circumstances, the department would have corrected the numbers, documented the cause, and informed the appropriate people. The technical problem was manageable. What made the situation significant was the person who found it: a junior analyst who had joined the team only a few months earlier and had already heard enough about the manager's temper to fear delivering bad news.

I learned about the incident from Patricia during our scheduled check-in. She arrived with a folder and a thoughtful expression, then sat opposite my desk.

"Something happened this morning that I think you'll want to hear about," she said.

I looked up from the staffing report. "A problem?"

"Yes. But possibly a useful one."

She explained that the analyst had discovered the error while preparing final materials. The figures had been drawn from an outdated spreadsheet, and several people had worked from the same version without noticing the discrepancy. The analyst had gone directly to the manager, expecting an angry response.

"What happened?" I asked.

"He listened."

I waited, assuming there was more.

"He asked how the error had occurred, confirmed which figures were affected, and brought two team members together to correct the report. According to the analyst, he didn't raise his voice or blame anyone."

"Did they finish in time?"

"Yes. The corrected figures were distributed before the presentation."

I leaned back. It was encouraging, though the circumstances did not yet prove a complete transformation. A manager could behave well when the problem was straightforward and the stakes were manageable. What mattered was whether the improvement would survive repeated pressure.

"Did he acknowledge the team's work?" I asked.

Patricia smiled faintly. "Apparently he thanked the analyst for catching the mistake."

That detail interested me more than the successful correction. In the earlier interviews, employees had described a department where admitting uncertainty or identifying a problem could invite criticism. Thanking someone for bringing forward an error was a small but important reversal.

"How did the analyst respond?"

"She told Sarah she was surprised."

I made a note. "Let's include it in the progress review, but continue gathering examples."

Patricia nodded. "That's what I thought."

After she left, I returned to my work, but the conversation stayed with me. I thought about the manager's first reaction when I asked him to move his foot. He had treated the request as an unreasonable intrusion on his comfort. Now, when someone interrupted his preparations with unwelcome information, he had apparently made room to listen.

The difference was encouraging precisely because it was ordinary. Nobody had applauded. No public confrontation had forced him to behave differently. He had simply responded to a colleague with patience when irritation would once have been his first instinct.

Later that afternoon, I met with Sarah to discuss the department's revised reporting procedures. She brought a carefully organized set of recommendations, including clearer approval stages and a shared system for recording corrections.

"These are practical suggestions," I told her. "Have you discussed them with your manager?"

"Yes."

"And?"

"He asked me to explain how they'd work."

"Did he agree with everything?"

"No," she said, and smiled slightly. "We disagreed about one part."

"What happened?"

"We talked about it."

She seemed almost amused by the simplicity of her own answer.

"He thought the approval process would create delays. I showed him how we could avoid that. He still wanted one change, but we reached an agreement."

I looked at her. "How did that feel?"

Sarah considered the question for a moment. "Normal. Which is strange, because it hasn't felt normal here for a long time."

Her answer reminded me that workplace improvement often appeared less dramatic than people expected. It was not necessarily a grand announcement or an emotional apology. Sometimes it was the absence of something that had made ordinary days difficult: raised voices, dismissive remarks, interruptions, or the need to rehearse every sentence before speaking.

Still, I knew better than to assume the department had fully recovered. Years of habits could not be erased in a few weeks. Employees needed repeated experiences of fair treatment before they could trust that the changes would last.

The manager continued attending coaching sessions and submitted brief reflections after each one. Some were awkwardly written, as though he disliked the exercise. Others showed growing awareness of his behavior. In one, he admitted that he often interpreted questions as challenges to his authority. In another, he recognized that employees sometimes offered solutions he had overlooked because he interrupted before they finished speaking.

I appreciated the candor but wanted to see it reflected in daily interactions.

The next test came sooner than expected.

A senior client called to complain about a missed deadline. The delay had resulted from several factors, including an unexpected technical issue and a scheduling decision approved by the manager himself. The client was unhappy, and the department faced pressure to deliver a revised plan immediately.

I attended the emergency meeting because the account involved several teams. The manager sat at the far end of the conference table, surrounded by reports and timelines. His expression was tense, and I could see the familiar signs of frustration gathering around his mouth.

Marcus began explaining the technical problem.

Halfway through his first sentence, the manager interrupted.

"That isn't the real issue. The problem is that—"

He stopped.

The room became quiet.

Marcus looked at him, uncertain whether to continue.

The manager drew a breath, then leaned back.

"Sorry. Go ahead and finish."

I kept my eyes on my notes, unwilling to turn the moment into a spectacle. But I heard the change in his tone, and I saw Marcus relax slightly.

Marcus completed his explanation. The manager listened, asked two questions, and then acknowledged that the scheduling decision had contributed to the delay.

"That part was mine," he said. "I approved the timeline. We should have built in more room for the technical review."

No one responded immediately. The admission was simple, but several people exchanged brief looks.

The meeting continued. We developed a revised schedule, assigned responsibilities, and prepared an explanation for the client. The manager remained visibly stressed, yet he did not return to the defensive tone that had nearly taken over the conversation.

Afterward, he approached me near the conference room door.

"I nearly did it again," he said.

"I noticed."

He gave a small, embarrassed laugh. "You probably noticed before I did."

"Perhaps."

He looked toward the empty room. "I heard myself interrupting Marcus. It was exactly what people had described."

"What made you stop?"

He considered the question. "I realized I wasn't listening. I was already preparing to defend the department before he finished explaining."

I nodded. "And what happened when you let him finish?"

"We found the actual problem faster."

The answer pleased me because he had identified a practical reason to change. Respectful behavior was important in itself, but he was also beginning to understand that listening could improve the quality of decisions.

"That's worth remembering," I said.

He smiled faintly. "I'm trying."

"I can see that."

As he walked away, I thought about how different this interaction was from our first encounter. On the airplane, he had treated every request as an obstacle to his comfort. Now he was beginning to recognize that discomfort could be useful when it forced him to examine his assumptions.

At the end of the fourth week, Patricia and I reviewed the evidence. Employee feedback had improved, though some staff remained cautious. The department's work continued to meet its targets, and there were early signs of better communication. We agreed that the manager had made meaningful progress but that the formal monitoring period should continue.

When I informed him, he looked disappointed for a moment.

"I thought things were going well."

"They are improving," I said. "But sustained change takes time."

He nodded slowly. "I understand."

"Do you?"

He looked at me with a slight smile. "You're not going to let me answer too quickly anymore, are you?"

"Not if you haven't thought about the question."

He laughed.

"No. I understand. People need to see that I'm going to keep behaving differently after the review ends."

"Exactly."

He sat quietly for a moment, then said, "I've been thinking about the airplane."

I raised an eyebrow. "Again?"

"Unfortunately."

I smiled despite myself.

"I keep remembering how angry I was when I saw those rings. I thought everyone was laughing at me because you were trying to make me look foolish."

"That was part of the prank," I admitted.

"I know. But I didn't consider that I'd already been making you uncomfortable for quite a while. I wanted you to respect my dignity while I was ignoring yours."

I looked at him carefully. It was the clearest acknowledgment he had made of the contradiction between his behavior and his expectations.

"That's an important distinction," I said.

He nodded. "I suppose I've done something similar at work. I expect people to respect my decisions, but sometimes I don't give their concerns the same consideration."

I did not rush to reassure him. The realization deserved room.

Finally, I said, "Recognizing that gives you a chance to change it."

He looked down at his hands. "I wish I'd understood it earlier."

"So do the people who work with you."

He accepted the remark without argument.

That evening, I arrived home later than usual. Daniel had prepared dinner, and Megan was sitting at the table completing a school assignment. Her hair was pulled into a crooked ponytail, and several colored pencils lay scattered beside her notebook.

"Mom," she announced, "we learned about apologies today."

"Did you?"

"Yes. Our teacher said saying sorry is good, but you also have to stop doing the thing."

Daniel looked at me over the stove with an expression of amusement.

"That sounds familiar," he said.

I sat beside Megan. "Your teacher is right."

She continued coloring for a moment, then asked, "Did the airplane man stop being rude?"

I considered everything that had happened during the past month: the employee interviews, the defensive conversations, the apology, the coaching sessions, and the small but meaningful changes.

"He's working on it," I said.

Megan nodded thoughtfully. "That's better than not trying."

"Yes. It is."

She held up her assignment, which featured a carefully drawn picture of two children sharing a toy.

"Sometimes people forget how to be nice," she said.

I looked at her drawing, then at the small pink ring resting beside her pencils.

"Sometimes they do."

Later, after Megan went to bed, Daniel and I sat together in the living room. He asked whether the department review was progressing, and I told him that the manager was showing genuine improvement. I also admitted that I remained cautious.

"Do you think you're being harder on him because of the flight?" Daniel asked.

I thought about the question.

"I've tried not to be. I've followed the same standards I would use for anyone."

"Then that's what matters."

I leaned back against the couch. "The strange part is that the whole thing started with something so small. An armrest. A bare foot. A man who didn't want to move."

Daniel smiled. "And a woman who happened to have Barbie nail polish."

I shook my head, laughing quietly.

"It still sounds ridiculous when you say it."

"It was ridiculous."

"Completely."

Yet beneath the absurdity, the consequences had become real. Employees were beginning to speak more openly, a manager was confronting habits he had long defended, and I was learning something about my own responsibility as a leader. I had been justified in wanting my boundaries respected, but I had not been justified in ignoring his consent in return.

The lesson belonged to both of us.

The following morning, Lauren placed an envelope on my desk. It had been delivered internally, without a formal cover note.

"Who sent this?" I asked.

"The department manager."

I opened it.

Inside was a short handwritten message thanking me for giving him a fair opportunity to improve. He acknowledged that the review had been uncomfortable and that he had initially seen it as a threat. He wrote that he now understood why employees needed to be heard and promised to continue working on the expectations we had established.

At the bottom, he had added one final line.

He hoped, he wrote, that the next time we traveled on the same airplane, both of us would remember to keep our hands and feet to ourselves.

I read the sentence twice.

Then I laughed.

For the first time since our encounter began, the memory of the airplane felt less like an unresolved humiliation and more like a lesson we could both acknowledge without anger.

But the final decision about his future remained ahead, and I knew the most important question had not yet been answered.

Would he continue treating people with respect when the formal review was over and nobody was watching closely?


Click here to continue reading: PART 12: The Last Review, a Handwritten Note, and the Unexpected Lesson That Turned an Awful Flight Into a Lasting Change