talehub

Chapter 21 - THE PRICE OF BEING THE FAVORITE

The following week, the conflict spread beyond the family.

Not through gossip or a dramatic announcement, but through the ordinary mechanisms of a company that could no longer pretend its leadership questions were private.

The department leads wanted to know who could approve purchases. Suppliers wanted confirmation of the upcoming transition. Patricia needed signed authority limits for the financial records. Denise needed to know whether she should train Ben under the current management structure or wait for a formal plan.

Dad answered some questions and avoided others.

Ben answered the questions he could.

I stayed outside the daily operation, responding only to the consulting request the company had formally approved. I completed the purchase-warning update and documented the changes. Denise tested the revised workflow with the department leads. The system now required an additional approval when a proposed order exceeded the agreed cash-exposure threshold.

The improvement worked.

It did not make the company invulnerable. It made a particular kind of mistake harder to repeat.

For the first time, the store's procedures no longer depended on my memory or my willingness to answer a late-night phone call.

That was progress.

It was also the source of Dad's growing frustration.

On Friday afternoon, he called me.

"I need you to come to the store."

"Is there a problem with the completed project?"

"No. This is a family matter."

"Then we can talk by phone."

"Luke, don't be difficult."

I closed my laptop.

"What's the matter?"

He exhaled sharply.

"Ben has told me he won't confirm the succession plan until the terms are revised."

I said nothing.

"He says he wants written authority over purchasing, a clear reporting structure, and a formal review of the company's financial position before any expansion is approved."

"Those are reasonable requests."

"Of course you think so."

"Would you prefer he accept a title without knowing what he is responsible for?"

"I would prefer my son to trust me."

I looked at the clock.

"Trust doesn't remove the need for a plan."

"You're putting ideas in his head."

"No. He's reading the reports and asking questions."

"You know what this is really about?"

I waited.

"He's afraid he can't do it without you."

The accusation struck close enough to be uncomfortable.

Ben had admitted his weaknesses. He had struggled with purchasing decisions and operational details. He had relied on my documentation more than he wanted to admit.

But fear of failing without me was not the same as refusing to learn.

"Then he needs to build his own competence," I said. "Not depend on me forever."

Dad was silent.

Then he said, "I need you to understand what this company means to me."

"I do."

"No, you don't. You see processes and numbers. You see the mistakes. You don't see what I put into this place."

I stood and walked to the window.

"I remember when the roof leaked over the paint aisle. I remember you working through Christmas because the supplier sent the wrong shipment. I remember the first contractor account that made enough money to keep the lights on. I remember you coming home exhausted and still sitting at the kitchen table to do the books."

He said nothing.

"I know what you built, Dad. That's why I helped save it when it needed rebuilding."

His breathing changed.

For a moment, I thought we might finally have an honest conversation.

Then he asked, "So why are you turning your back on it?"

I closed my eyes.

"I'm not turning my back on the business. I'm refusing to be the invisible person responsible for everything no one wants to manage."

He ended the call without saying goodbye.

I sat in the quiet for several minutes.

Part of me wanted to call him back. I wanted to explain it differently, find softer words, offer another compromise.

That impulse had kept me in the same cycle for four years.

I let the phone remain on the desk.

On Saturday, Ben came to my apartment again.

This time, he didn't bring the brass key.

He brought a folder.

"I need your opinion on something," he said.

"Is it a company project?"

"Not yet."

"Then I can't do the work for you."

"I'm not asking you to. I wrote a proposal for the transition plan. I want you to tell me whether I'm missing a major question."

I studied him.

"What happens if I say you're missing something?"

"I add it to the list."

"What happens if I say the entire plan is wrong?"

"I go back and rewrite it."

I gestured toward the table.

"Show me."

He opened the folder.

His proposal was three pages long. It wasn't polished, but it was thoughtful. He had separated the succession process into stages: financial review, authority clarification, department training, supplier communication, and a final evaluation before the presidency became effective.

He had included a section on what he did not yet know.

That impressed me more than the parts he did know.

He acknowledged that he needed further training in purchasing, inventory planning, and financial forecasting. He proposed that Denise lead the operational training and that Patricia review his financial assumptions each week.

He also included a section on my role.

I read it carefully.

It did not assume I would be available indefinitely. It proposed that any additional work from me be contracted separately, with clear deliverables and a fixed schedule.

I set the document down.

"This is a better starting point."

Ben's shoulders relaxed.

"But there are problems."

"Tell me."

"You've written the plan as if everyone agrees on the basic objective. Dad hasn't agreed to give up decision-making authority. You need to address what happens if he refuses."

Ben took notes.

"Anything else?"

"Your review process is too short. You can't prove you're ready to run the company by attending a few meetings. You need to demonstrate that you can make decisions, explain them, measure the results, and correct your mistakes."

He nodded.

"And you need a clear definition of what success means. Not just revenue. Cash flow, inventory turnover, supplier reliability, customer retention, staff stability."

He wrote faster.

I watched him work.

For years, I had imagined that if Ben understood the systems, he would eventually become competent. I had never considered that he might learn to lead in a way that was different from mine.

He was more comfortable with people. He remembered customers' names and noticed when an employee was struggling. He could turn a complaint into a conversation without making the customer feel dismissed.

Those were real strengths.

He did not need to become me.

He needed to understand the parts of the business he had been avoiding, and he needed to build a leadership team that could compensate for what he did not know.

When he finished taking notes, he looked at me.

"Can I ask you something that isn't about the proposal?"

"Go ahead."

"Did you ever feel like Dad was proud of me because I was easier to love?"

The question took me by surprise.

I leaned back.

"What do you mean?"

Ben stared at his hands.

"You always challenged him. You asked why things were done a certain way. You told him when a decision didn't make sense. I learned to make him laugh instead. I learned that if I could make him feel good about himself, he would tell me I was doing well."

He looked up.

"Sometimes I wondered whether you were the one who got criticized because you were willing to stand up to him, while I got praised because I wasn't."

I thought about it.

"I don't know if that's how he saw it."

"But is that how it felt to you?"

I considered giving him a comforting answer.

Instead, I told the truth.

"Sometimes."

Ben nodded, as though he had expected it.

"I think I took advantage of that without understanding what it cost you."

I didn't respond immediately.

He continued.

"When Dad announced me as president, part of me was happy. I won't pretend otherwise. But another part of me was relieved that he had chosen me instead of you, because I didn't have to find out whether I could ever compete with you on the things you were good at."

"Leadership isn't a competition between us."

"I know that now."

"Do you?"

He met my eyes.

"I'm trying to."

The silence between us was no longer hostile.

It was uncomfortable in a different way—the discomfort of two people finally admitting what they had spent years avoiding.

Ben closed the folder.

"I don't want to become the kind of man who needs you to fail so I can feel successful."

I looked at him.

"Then don't."

He stood and carried the folder toward the door.

Before leaving, he turned back.

"Would you be willing to attend the next management meeting as a paid consultant? Not to make decisions. Just to answer technical questions if they come up."

"If the company sends a written request with a defined scope, I'll consider it."

He nodded.

"I'll ask Denise to handle it."

After he left, I sat alone at the table.

I was not ready to forgive everything. Ben's apology did not erase the party, the brass key, or the months of assumptions that had led to them.

May you like

But I could see that he was beginning to understand the difference between being chosen and being prepared.

And I wondered whether Dad would ever be able to make that distinction himself.

Related Stories

Other posts