Black CEO Mistaken for a Janitor — Told to Clean, Then She Fired Everyone

Chapter 20

Theme:
Font Size:
24px

The auditor nodded.

“That's what we'll request.”

Marcy felt her shoulders loosen slightly.

For the first time in months, someone had asked her a technical question and accepted a technical answer without accusing her of being difficult.

She continued through the records.

Some discrepancies were explained by duplicate entries.

Others involved project-code changes.

A few required further investigation.

The review team did not treat the results as proof of a conspiracy. Instead, it created a case list, preserved the original data, and identified the people who had authorized each adjustment.

By the end of the morning, the team had established that the process was not sufficiently transparent.

They had not yet established why.

That distinction mattered.

At 11:20 a.m., Richard Keller was asked to provide his response to several specific complaints.

He entered the interview room carrying a notebook and a printed copy of the company's management policy.

Evelyn sat at one end of the table. Susan Bell sat beside her. Two members of the independent review team occupied the opposite side.

Richard took his seat.

“I understand we're reviewing historical complaints.”

“Yes,” Evelyn said.

“I want to cooperate.”

“Thank you.”

Richard opened his notebook.

“I also want to make clear that the East Division operates under considerable pressure. Our clients have strict deadlines. Our competitors are aggressive. If we miss a delivery window, we can lose a contract worth millions.”

The external specialist nodded.

“We understand that operational demands can be significant.”

“Then I hope the review will consider that context.”

“It will.”

Richard seemed relieved.

He described the division's performance targets, the difficulty of staffing certain projects, and the expectations placed on managers. He explained that employees were often required to adapt quickly and that some found the environment challenging.

Much of what he said was true.

Pinnacle's clients did operate in demanding industries. Deadlines could be expensive to miss. Technical projects sometimes required urgent work, and managers had legitimate responsibilities to coordinate resources.

But the interviewers were not asking whether the work was demanding.

They were asking how Richard had responded when employees raised concerns.

One complaint described a meeting in which he had allegedly called an analyst useless.

Richard frowned.

“I don't remember using that exact word.”

“Do you remember criticizing the employee in front of the team?”

“I remember a performance discussion.”

“Was it scheduled as a formal performance meeting?”

“No.”

“Was the employee given an opportunity to respond?”

“I'm sure they could have responded.”

“Is there a record?”

“Not that I know of.”

The interviewer made a note.

Another complaint described a threat to lower an employee's performance rating after the employee questioned a schedule.

Richard leaned back.

“I would never threaten someone for asking a question.”

“Did you tell an employee that continued resistance would affect their future at Pinnacle?”

Richard's expression tightened.

“I may have said that people who refused to cooperate would have difficulty advancing.”

“Can you explain what you meant?”

“I meant that teamwork matters.”

“Was the employee refusing to cooperate, or were they questioning a schedule?”

Richard looked at the document.

“I don't remember the exact circumstances.”

The interviewer placed another record on the table.

It contained an email Richard had sent to a department manager several months earlier.

We need to make it clear that repeated challenges to operational decisions will be reflected in performance assessments. The team cannot afford endless debate.

Richard read the message.

“I was referring to a particular project.”

“Did the employee's performance review mention the disagreement?”

“I would have to check.”

“Was the review based on documented performance criteria?”

“Yes.”

“Can you provide those criteria?”

“Of course.”

The interviewer nodded.

“Please do.”

The interview continued for another hour.

Richard answered some questions confidently. Others required him to consult his records. On several occasions, he insisted that he had been misunderstood. On others, he acknowledged that his language might have been too harsh.

The investigators did not tell him what conclusions they were reaching.

They simply recorded his responses and requested supporting documentation.

When the interview ended, Richard closed his notebook.

“I hope we're not turning every management disagreement into misconduct.”

Evelyn met his gaze.

“We are not. We are examining specific allegations and the evidence associated with them.”

“Because I have always believed in high standards.”

“High standards are not the issue.”

Richard stood.

“What is?”

“Whether the standards were applied fairly, whether employees were treated appropriately, and whether the company's procedures were followed.”

He left without answering.

For the first time, he was beginning to understand that he could not define the investigation simply by declaring himself a demanding manager.

The company was examining the difference between demanding performance and demanding submission.

And Richard had spent years pretending those were the same thing.

At 2:40 p.m., Victoria met privately with Daniel Brooks.

The meeting took place in a small office beside the compliance department. Daniel had agreed to speak after receiving a written explanation of the review process and a contact for raising concerns about retaliation.

He looked exhausted.

Victoria did not begin by asking him about Richard.

News in the same category

Black CEO Mistaken for a Janitor — Told to Clean, Then She Fired Everyone

45 Part