PART 10 – A Private Conversation Forced Me to Decide Whether the Manager’s Promises Deserved Trust or His Employees Needed Stronger Protection

The written account arrived in my inbox shortly after eight. I read it once, then a second time, paying close attention to the difference between what the employee had observed and what he believed the manager intended. The distinction was important. I did not want to turn an anxious interpretation into an established fact. According to the statement, the manager had approached the employee near the break room, asked whether he intended to participate in the review, and then wondered aloud whether some people might use the opportunity to damage his reputation. The employee had felt pressured, although no direct threat had been made.

I called Patricia and asked whether she had interviewed the employee personally.

"Yes," she said. "He was visibly uncomfortable. He also said the manager didn't raise his voice."

"Did anyone else witness the conversation?"

"One colleague was nearby but couldn't hear everything."

"Then let's gather what we can without making assumptions."

Patricia agreed. We arranged to speak with the manager later that morning and postponed any conclusions until we had heard his account. I closed the message and looked at the day's calendar. The schedule was already full, with project approvals, staffing discussions, and a meeting about the next quarter's budget. The department review had begun consuming more time than I anticipated, but the consequences of mishandling it would be much greater than a delayed administrative decision.

At ten, the manager arrived in my office. He had returned to wearing the expensive watch I remembered from the flight, and his shirt was immaculate. His expression was wary. He sat only after I invited him, then placed both hands on the arms of the chair.

"Is this about the review?" he asked.

"Yes. We received a concern about a conversation you had with an employee yesterday."

He looked immediately defensive. "I haven't threatened anyone."

"I haven't said you did."

"Then what's the problem?"

I opened the written account. "An employee reports that you asked whether he intended to say anything that might harm your reputation."

He stared at me. "That's what this is about?"

"I'd like you to tell me what happened."

He rubbed his forehead. For several seconds, he appeared ready to argue. Then he lowered his hand and looked at the floor.

"I saw him near the break room," he began. "He looked nervous. I knew the interviews were happening, and I asked whether he was all right."

"And then?"

"He said he didn't want to get caught in the middle of anything."

"What did you say?"

He shifted uncomfortably. "I told him I hoped people would be fair. That I didn't want the review turning into some kind of attack on my character."

"Did you ask what he planned to tell us?"

He hesitated.

"I may have asked whether he had concerns about me."

I let the silence settle. The answer was more significant than he seemed willing to admit. He had been told not to question employees about their participation, yet he had approached someone privately and directed the conversation toward what that person might say.

"You promised me you wouldn't do that," I said.

"I know."

"Why did you?"

He looked up sharply. "Because I was worried!"

The words came out louder than anything he had said since entering my office. He immediately glanced toward the door and lowered his voice.

"I've worked here for years. I've met my targets. I've taken difficult projects nobody else wanted. Now people are talking about me, and I don't even know what they're saying."

His frustration was genuine. I could see it in the tightness around his mouth and the way he gripped the chair. For the first time, I understood that the review had unsettled something central to his view of himself. He believed his professional worth rested on results. Being asked to examine his relationships with employees threatened an identity he had spent years building.

"I understand that uncertainty is uncomfortable," I said. "But employees have been living with a different kind of uncertainty. They don't know whether raising concerns will lead to criticism or consequences."

He looked away.

"When you question someone about what they might say, you reinforce exactly the fear we're trying to address."

"I didn't mean to intimidate him."

"I believe that may be true. But your intention doesn't erase the effect."

He stared at his watch, then slowly turned it around his wrist.

"What do you want me to do?"

"Stop discussing the review with employees except through the agreed communication. Let Patricia handle the interviews. If you're worried about the process, bring those concerns to me or human resources."

He nodded.

"And I need you to understand that this can't happen again."

His shoulders stiffened. "Am I being formally disciplined?"

I chose my words carefully. "We're documenting this conversation and consulting human resources about appropriate next steps. The employee's concern will be reviewed fairly, including your account. I won't make a disciplinary decision without following our procedures."

He seemed disappointed that I would not give him immediate reassurance.

"So my position is in danger."

"Your position depends on your continued ability to meet the requirements of your role. That includes how you treat employees."

He sat very still.

I closed the document. "There's something I want you to consider. On the airplane, you dismissed my concerns because you believed your need to stretch outweighed my need for space. Here, you're dismissing employees' concerns because your fear of criticism feels more important to you than their ability to speak freely."

He raised his eyes slowly.

"I thought we agreed the flight wasn't part of this review."

"It isn't evidence in the workplace review. I'm speaking to you now about the similarity in how you're explaining your choices. The employment decisions will be based on workplace facts."

He looked at me for a long moment. Then his expression changed. It was not agreement, exactly, but the first indication that he was considering the possibility that the two situations had something in common.

"I keep thinking people are against me," he said quietly.

I waited.

"When somebody complains, I assume they're trying to make me look bad. I start defending myself before I even understand what they're saying."

His admission surprised me because it contained no immediate excuse.

"That sounds exhausting," I said.

He gave a humorless laugh. "It is."

"It must also be exhausting for the people who work with you."

He nodded once.

The conversation lasted another half hour. I explained the process again, including how findings would be evaluated and how he could respond to concerns without confronting employees individually. He agreed to follow the boundaries. I asked Patricia to document the discussion, and we confirmed that the employee who had reported the incident would receive appropriate support and protection from retaliation.

When he left, I did not feel triumphant. The exchange had revealed a man who was frightened of losing control and who responded to that fear by trying to control other people. Understanding the pattern did not excuse it. But it offered a possible explanation for why repeated training and earlier conversations had failed to produce lasting change.

The next several days brought a mixture of discouraging and encouraging developments. Patricia completed the remaining interviews, including conversations with two employees who had originally withdrawn. The accounts remained consistent. Some staff admired the manager's ability to solve technical problems, but many described avoiding difficult conversations with him. Several wanted him to remain because they valued his knowledge, provided the department's culture could improve.

One afternoon, Sarah returned for a brief follow-up. She sat across from me with her notebook open this time, a small but noticeable change from our first meeting.

"I heard he's been told not to ask about the interviews," she said.

"All managers are expected to respect the process," I replied.

She nodded. "I appreciate that."

"Has anything changed in the department?"

"It's quieter, but not in the old way."

I asked what she meant.

"He seems to be thinking before he speaks. Yesterday someone brought him a problem with a report. Usually he'd interrupt after the first sentence. This time he asked the person to explain what had happened."

"How did the conversation end?"

"He gave them time to fix it."

Sarah looked almost embarrassed to describe such an ordinary interaction as noteworthy. I understood why. In a healthy workplace, allowing someone to finish a sentence should not be remarkable. In her department, it had become an event worth reporting.

Still, I was careful not to mistake one improved interaction for lasting change. People sometimes modified their behavior temporarily when they knew they were being observed. The real test would come after the review ended and the pressure of immediate scrutiny diminished.

Patricia and I spent Friday morning comparing the interview findings with performance data. The department's technical strengths were clear. So were the management concerns. We prepared a development plan with measurable expectations: respectful communication, consistent feedback procedures, documented follow-up on employee concerns, and regular check-ins involving human resources. We also recommended additional leadership coaching, not as a substitute for accountability but as support for specific behavioral changes.

The plan included consequences if the manager failed to improve. I insisted on clarity. A vague promise to behave better would serve neither him nor his team.

Late that afternoon, I called him to discuss the proposed approach. He arrived looking tired, but less defensive than before. I explained the findings without naming confidential sources and invited him to respond.

He listened quietly.

When I finished, he said, "I didn't realize so many people felt that way."

"Some have been trying to tell you for a long time."

"I know that now."

He examined the written plan. "You're not removing me?"

"Not at this stage. We're setting clear expectations and a review period. Your technical performance matters, but so does your ability to lead people."

He read the document carefully. "And if I don't improve?"

"Then we'll need to consider further action."

He nodded.

For several minutes, he remained silent, turning pages and making small notes in the margins. I watched him without interrupting. He was capable of understanding complex requirements, and this document presented a challenge that was less technical but no less important.

Finally, he looked up. "I want to do this properly."

"Then you'll need to listen to feedback that may be uncomfortable."

"I understand."

"And you'll need to accept that employees can disagree with you without attacking you."

He considered that.

"That's going to be harder."

"I expect it will."

He gave a brief, rueful smile. "At least you're not pretending otherwise."

We scheduled the first coaching session and agreed on the reporting procedures. As he prepared to leave, he paused by the door, much as he had during our earlier conversation.

"Rebecca, can I ask you something that has nothing to do with the review?"

"Go ahead."

"Did your daughter ever find out what happened to her polish?"

I smiled despite myself. "Yes. She found it hilarious."

He shook his head.

"I still can't believe I walked through an airplane with those rings on my toes."

"Neither can I."

He laughed quietly, then became thoughtful.

"I was furious because everyone was looking at me. I didn't stop to think that you'd spent nearly an hour being uncomfortable because of me."

I looked at him.

"That was the part I wanted you to understand," I said.

"I think I finally do."

He left without another word.

That evening, I drove home beneath a sky heavy with rain clouds. Traffic moved slowly, and the windshield wipers began their steady rhythm as the first drops fell. I thought about the department, the employees who had taken risks by speaking honestly, and the manager who was struggling to confront habits he had defended for years.

At home, Megan was arranging her Barbie rings along the edge of the coffee table. She had separated them by color and was instructing Daniel to choose one for an imaginary royal ceremony. When she saw me, she lifted the pink gemstone ring.

"Mom, this one is still my favorite."

I sat beside her. "It's certainly memorable."

She placed it on my finger and examined the result.

"Do you think the airplane man learned his lesson?"

I looked at the bright plastic jewel, remembering the man standing in the aisle while strangers laughed at his painted feet.

"I think he's beginning to," I said.

Megan nodded with the certainty of a child who believed important lessons should be followed by immediate improvement.

But I knew the coming weeks would reveal whether embarrassment had merely changed his behavior for a few days or whether he was finally willing to treat other people differently when there was nothing to gain by doing so.


Click here to continue reading: PART 11: Weeks After the Flight, a Difficult Workplace Test Showed Whether the Man Had Truly Changed or Was Merely Protecting Himself