"An arrogant flight attendant summoned security to put me in handcuffs at seat 14A because I looked poor

Chapter 20

Theme:
Font Size:
24px

“What do you think?”

“I think they're worried about their jobs.”

I nodded.

“That's understandable.”

He looked at me.

“Can I ask you something?”

“Of course.”

“Do you really want people telling you when something's wrong?”

I met his eyes.

“Yes.”

“Even when it costs money?”

I thought about the acquisition.

The difficult board meetings.

The years of reforms.

The complaints that had been hidden because they made the numbers look worse.

“Especially then,” I said.

Thomas studied me for a moment.

Then he nodded.

“Good.”

The review concluded that no evidence had been found of technicians intentionally bypassing required safety procedures in the examined cases.

But it also confirmed that management communications had created unnecessary pressure and that some performance measures were poorly designed.

Northstar revised those measures.

Supervisors received additional training.

The safety office began conducting periodic reviews of how operational targets affected maintenance work.

Thomas returned to his ordinary routine.

He didn't become a television personality.

He didn't appear in advertisements.

He didn't want a promotion.

He simply wanted to finish his career knowing that the company had listened.

Six months later, he retired.

Andrea sent me a photograph from his small retirement gathering.

Thomas stood beside a cake decorated with a tiny airplane.

His coworkers surrounded him.

He looked embarrassed by the attention.

On the back of the photograph, someone had written:

Thirty-two years of keeping people moving.

I placed it beside the photograph of Emily Carter, the young maintenance apprentice I'd met in Chicago.

One employee beginning her career.

Another completing his.

Both had reminded me that leadership depended on listening to people who understood work I could never perform myself.

The following winter, Northstar faced its most difficult financial quarter since the acquisition.

Fuel prices had risen.

A series of severe storms disrupted schedules.

Several competitors had reduced fares on major routes.

Our costs increased faster than revenue.

At a board meeting in February, the chief financial officer presented a plan to reduce spending.

Some proposals were sensible.

Others concerned me.

One recommendation involved reducing staffing in several customer-support departments.

Another proposed delaying investment in the complaint-management system.

A third suggested postponing portions of the employee training program.

I studied the figures.

“How much would these reductions save?”

The chief financial officer gave me the projected amount.

“And what would they do to response times?”

He hesitated.

“We expect some temporary deterioration.”

“How much?”

“We're modeling several scenarios.”

I looked at Andrea.

She was sitting two seats away.

“What do you think?”

She opened her folder.

“I think we can reduce costs without dismantling the systems we've spent years improving.”

The CFO frowned.

“That will require savings elsewhere.”

“Yes.”

“Where?”

Andrea slid a document across the table.

“Administrative duplication, outdated software contracts, and several underused office leases.”

He examined the proposal.

“These savings won't all arrive immediately.”

“No,” she said. “But cutting frontline support creates costs too. They just don't always appear in the same quarter.”

I looked at the board.

“Then we should compare the full costs before deciding.”

One director sighed.

“Vanessa, investors expect discipline.”

“I agree.”

He leaned forward.

“Sometimes discipline requires difficult cuts.”

“Yes.”

I paused.

“But difficult doesn't automatically mean wise.”

The room became quiet.

I continued.

“We acquired this company because we believed it had long-term value. We cannot manage it as though the only goal is to make next quarter's report look better.”

Eleanor nodded.

“Let's review Andrea's alternatives.”

The board spent another three hours examining the options.

In the end, we approved a revised plan.

It reduced spending.

It delayed some nonessential projects.

But it preserved the core complaint-review and safety programs.

The decision was not universally popular.

Some investors wanted faster cost reductions.

A financial commentator accused Pinnacle of allowing reputational concerns to interfere with profitability.

I read the article.

Then I closed it.

I had learned that criticism was not always evidence of a mistake.

Sometimes it was simply the price of making a decision that required patience.

In March, I received an unexpected invitation from the National Transportation Leadership Forum.

The organizers wanted me to deliver a keynote address about corporate accountability.

I declined at first.

I had already spoken publicly about Flight 218 more times than I cared to remember.

But the organizer called again.

“We don't want another speech about the incident,” she said.

“Then what do you want?”

“We want you to talk about what happened afterward.”

I considered that.

She continued.

“Most companies apologize when something goes wrong. Far fewer explain how they changed the systems that allowed it.”

That was a fair point.

I agreed.

The forum took place in Washington, D.C., in a large conference center filled with transportation executives, regulators, labor representatives, researchers, and journalists.

I arrived early.

As I waited backstage, I reviewed my notes.

The speech was not about revenge.

It was about incentives.

News in the same category

"An arrogant flight attendant summoned security to put me in handcuffs at seat 14A because I looked poor

45 Part