validate

Chapter 8 - The Board Asked Whether Maya Should Have Known Sooner

The board review turned toward Maya.

She had requested it.

That did not make the questions easier.

Helen Park led the session.

No press team.

No executive assistants.

No loyal subordinates.

Just independent directors, outside counsel, and Maya.

The first question was simple.

“What did you know about passenger-treatment complaints before Flight 417?”

Maya answered.

Aggregate numbers.

Top categories.

Net promoter trends.

Compensation costs.

Serious safety events.

She did not know about the private crew chat.

She did not know ethics complaints had described an unofficial blacklist.

She did not know Caroline’s office had closed one complaint after receiving a screenshot.

“What should you have known?”

That was harder.

Maya looked at the packet in front of her.

“We reported complaint volume without reporting complaint character.”

“Meaning?”

“We treated all closed cases as operationally similar once compensation was issued.”

A director asked, “Did the board receive discrimination data?”

“Not separately.”

“Why?”

“Because we did not build the reporting structure.”

“Who was responsible?”

Maya did not say HR.

Customer care.

Caroline.

She said, “I was.”

The room stayed quiet.

Responsibility did not mean personal knowledge.

It meant leadership ownership.

Another director asked whether Maya’s anonymous flying program had been properly governed.

That surprised her.

She had quietly flown without executive treatment several times a year to observe service.

No secret cameras.

No entrapment.

No fake complaints.

Still, was it wise for a CEO to conduct informal audits without a documented framework?

Maybe not.

“You were gathering information outside normal channels,” Helen said.

“Yes.”

“Could that encourage decisions based on anecdote?”

“Yes.”

“Did you ever discipline employees based on those trips?”

“No.”

“Did you give positive feedback?”

“Yes.”

“Through whose chain?”

“Operations.”

The review later recommended formalizing executive observation.

Randomized.

Documented.

No individual discipline based solely on one executive’s hidden experience.

Maya supported it.

She felt strangely relieved.

Systems should constrain powerful people too.

Especially powerful people.

Then the board asked about the grounding.

Was holding the aircraft proportionate?

Maya explained the sequence.

She called Operations to stop pushback after an unresolved crew-passenger conflict involving identity and seat assignment.

She then asked station leadership to take control.

The captain retained operational authority.

The later cancellation resulted from crew availability and timing limits, not a direct order from Maya.

The board reviewed recordings.

No misconduct found.

But one recommendation followed:

Future executive involvement in live operational incidents should transfer to designated command staff as quickly as possible.

Fair.

Maya approved.

When the session ended, Helen walked her to the elevator.

“You look offended.”

“I’m tired.”

“You’re offended.”

“A little.”

“Good.”

Maya looked at her.

Helen smiled.

“You built a company where the board can tell you no. That’s the point.”

Maya laughed despite herself.

At home, Daniel poured coffee.

“How was judgment day?”

“I remain employed.”

“Congratulations.”

“The board criticized my secret-shopper flights.”

“I criticized those three years ago.”

“You called them weird.”

“They are weird.”

“They’re useful.”

“Useful things can be weird.”

Naomi entered wearing headphones.

“Are you both fighting?”

“No,” Maya said.

“Yes,” Daniel said.

Naomi left.

Normal life had become precious.

Then another story broke.

A former flight attendant posted that she had been removed from premium service two years earlier after objecting to the crew watchlist.

Her name was Allison Greene.

Outside counsel contacted her.

Her personnel file said performance issues.

Attendance.

Passenger complaints.

Team conflict.

Allison claimed those reasons were exaggerated after she reported discriminatory comments in the group.

This was more serious.

Not only failure to investigate.

Possible retaliation.

Caroline’s name appeared again.

Allison produced an email to Caroline:

I’m concerned the group is profiling Black passengers and people who “look poor.” I don’t want to be part of it.

Caroline replied:

Please discuss concerns through your base supervisor. Do not circulate screenshots of private employee conversations.

Two months later, Allison was transferred out of premium cabin service.

Was that retaliation?

The file contained performance concerns predating her complaint.

Mixed evidence.

Outside counsel refused to jump.

Good.

Maya wanted rigor even when it delayed outrage.

Allison’s supervisor, now retired, agreed to an interview.

He said Caroline had never told him to punish Allison.

He also admitted Caroline called him after Allison’s email and said:

“She is becoming disruptive about this chat issue. Manage the team.”

Manage the team.

Corporate language again.

Soft enough to deny.

Sharp enough to shape behavior.

The investigation found no single order.

It found a pattern of incentives.

Do not write it down.

Keep it off systems.

Handle complainers locally.

Avoid creating discoverable records.

The effect was predictable.

People who objected felt risky.

People who participated felt protected.

When the board received the interim findings, Helen asked Maya what she thought.

Maya looked at the phrase on the screen.

CULTURAL RISK THROUGH INFORMAL SUPPRESSION.

“I think we trained people to fear documentation more than misconduct.”

That sentence became the next problem to fix.

May you like

Not with slogans.

With protection for the person who wrote the uncomfortable email before the CEO ever sat in 2A.

Related Stories

Other posts