White Billionaire Family Mocked the Black CEO at Party — Then He Bought Their Entire Company

Chapter 35

Theme:
Font Size:
24px

“Some were.”

“Then discomfort may be part of the process.”

Charles gave a tired smile.

“I used to believe a good chairman kept the room calm.”

“A good chairman should make sure the room is useful.”

Charles considered that.

“I suppose those aren't always the same thing.”

“No,” David said. “They aren't.”

Nathan's First Real Assignment

Two days later, Nathan received a new assignment.

He was not being asked to lead a major acquisition or represent the company at a public event. Instead, he was assigned to work with an operational team reviewing supplier-performance procedures.

The team was led by Karen Douglas, the experienced operations executive David had met on the night of the gala.

Nathan read the assignment twice.

He was expected to attend working sessions, review the team's recommendations, and contribute where his experience was relevant. Karen would evaluate his performance against clearly defined criteria.

He would have no special authority over the team.

When he entered the conference room, Karen greeted him politely.

“Mr. Whitmore.”

“Karen.”

“Before we begin, I want to make the responsibilities clear. I am accountable for the review. You are here to contribute analysis and learn the process. If you disagree with a recommendation, explain why and provide evidence.”

Nathan nodded.

“Understood.”

Karen opened the first document.

The team was examining a supplier agreement that had generated repeated delays and additional costs. The contract had been approved under the previous management structure, and the records contained several unresolved questions about how the final supplier had been selected.

Nathan recognized the supplier's name.

He had attended one of the meetings in which the contract was discussed.

“I remember this,” he said. “The supplier had a strong relationship with the company.”

Karen looked at him.

“What did that relationship contribute to the decision?”

Nathan paused.

“I don't know. I assumed they were reliable.”

“Was there evidence supporting that assumption?”

“I don't remember seeing a formal comparison.”

Karen nodded.

“Then we should establish what was known at the time. We shouldn't assume the decision was wrong simply because it produced a bad result, but we shouldn't defend it simply because someone trusted the supplier.”

Nathan felt the familiar urge to explain that he had not made the final decision.

It was true.

He had not approved the contract.

But he had attended the meeting, expressed confidence in the supplier, and encouraged the team to proceed without asking for the missing comparison.

He had influenced the decision without accepting responsibility for it.

“I supported the recommendation,” he said.

Karen looked up.

“Why?”

“Because I believed the relationship made the supplier a safe choice.”

“Did you review the performance data?”

“No.”

“Did you ask whether the price was competitive?”

“No.”

“Did you check the delivery history?”

Nathan shook his head.

Karen closed the file.

“Then this is an opportunity to learn what you should have asked.”

The words were not insulting.

They were not even particularly harsh.

Yet Nathan felt the weight of them.

He had spent years in meetings where his comments were treated as valuable because he was a Whitmore. People had assumed that he understood more than he did. He had rarely been required to explain the reasoning behind his opinions.

Now someone was asking him to distinguish between what he knew and what he merely believed.

The distinction was uncomfortable.

It was also necessary.

Nathan spent the next three hours examining supplier records with the team. He learned how delivery reliability was measured, how price comparisons were adjusted for service quality, and how procurement decisions could be distorted by informal relationships.

At the end of the session, Karen asked him to summarize what he had learned.

Nathan looked at his notes.

“I thought the main problem was that the supplier failed to deliver,” he said. “But the records suggest that we didn't establish whether they were the right supplier in the first place.”

Karen nodded.

“That's part of it.”

“We relied on confidence in the relationship instead of verifying the evidence.”

“Yes.”

Nathan closed his notebook.

“I contributed to that.”

Karen studied him.

“Do you understand how?”

“I encouraged the decision because it seemed familiar and convenient. I didn't ask whether the supplier had earned the confidence we placed in them.”

For the first time since the gala, Nathan was not talking about his intentions.

He was describing his actions.

Karen gathered the documents.

“That's a useful starting point. Now we need to see whether your next decisions reflect it.”

Nathan nodded.

He knew the sentence was not a promise of promotion.

It was a standard he would have to meet repeatedly.

For the first time, he began to understand that leadership was not the ability to make people follow a decision.

It was the discipline to make sure the decision deserved to be followed.

News in the same category

White Billionaire Family Mocked the Black CEO at Party — Then He Bought Their Entire Company

45 Part