Chapter 12 - The most dangerous phrase in Ethan’s company turned out to be “temporary workaround”
The integration bug had a simple explanation.
Vance Hospitality changed reservation platforms.
Executive and ownership travel reservations passed through a legacy channel.
New front-end system did not always display them immediately.
IT built a secondary queue.
Temporary.
Expected resolution:
Three weeks.
Six weeks later, still active.
Why?
Bigger projects.
Revenue systems.
Cybersecurity update.
Mobile check-in.
All higher priority.
No executive booking had caused major loss.
Staff knew workaround.
So risk remained.
Until Ethan stood at the desk with Lily.
Daniel said:
“I would have made the same prioritization decision if your reservation wasn’t involved.”
“That’s the problem.”
Daniel frowned.
“You think executive bookings deserve higher IT priority?”
“No.”
“I’m not following.”
“We classified failure by revenue impact, not human impact.”
A missing reservation can strand anyone.
Not only owners.
Third-party booking integration had similar bugs.
Those did generate guest complaints.
Still medium priority because refunds contained financial loss.
Containment became substitute for prevention.
Then Ethan asked IT:
“How many open temporary workarounds exist across guest-facing systems?”
Silence.
They counted.
Forty-three.
Some trivial.
Some concerning.
One required staff to manually transfer accessibility requests between systems.
Another required copying allergy notes for certain banquet bookings.
Another involved late-night shuttle requests.
Temporary workaround.
Potential human harm.
Ethan did not order all fixed tomorrow.
That would be performative.
He required risk reclassification including safety, dignity, and service consequences—not only direct revenue.
Then Daniel said:
“You’re turning one bad night into a company redesign.”
“Maybe.”
“Is that proportionate?”
Good question.
Ethan considered.
“No, if the only evidence were my night.”
“But it isn’t.”
Exactly.
Nora.
Lupita.
Andre.
Turnover.
Training.
Data.
System failures.
Enough.
Then Daniel admitted his own habit:
“I reward teams for closing tickets.”
“What’s wrong with that?”
“They close around the workaround.”
Metrics again.
Problem marked resolved because process exists, even though root issue remains.
Same as guest complaint settled with points.
Closed.
Not solved.
Then Ethan asked for a new dashboard category:
Resolved by workaround.
Those tickets remain visible until root fix.
Boring.
Powerful.
Then came the public question.
Media wanted interview.
Ethan resisted for weeks.
Eventually agreed to one business-journal interview focused on operational lessons.
No Lily.
No Sarah details beyond what already public.
He refused to name Patricia or Karla.
He did not present himself as victim-hero.
He said:
“The troubling part was not that staff failed to recognize the owner. It was that recognition changed the quality of service.”
That became headline.
Fine.
Then reporter asked:
“Did you fire the receptionist?”
Ethan answered:
“Personnel decisions are private.”
Good.
“Did the housekeeper get promoted?”
“She accepted a role she chose.”
Good.
“Would this have happened if you weren’t owner?”
“The investigation probably would not have happened this quickly. That is one of the failures we are correcting.”
Honest.
Then:
“Was this discrimination?”
Ethan paused.
“We found appearance-based assumptions, status bias, and a culture that sometimes treated some travelers as less worthy of verification. We are not going to claim motives we cannot prove for every incident.”
Precise.
Some viewers found that too cautious.
Others appreciated it.
Then he said:
“If the lesson becomes ‘be polite because the person might secretly be rich,’ we have learned nothing.”
That line traveled.
Lupita approved.
Barely.
Then another unexpected consequence.
Bookings increased after publicity.
People wanted to stay at “the hotel that changed.”
Marketing wanted to capitalize.
Ethan refused campaign built on incident.
No “Everyone Belongs” package.
No Lupita ads.
No roses branding.
The hotel did not deserve to monetize correction immediately.
Instead, some increased revenue happened anyway.
Board wanted to celebrate.
Ethan redirected a portion? Need be careful corporate governance. Could establish training budget with board approval.
They funded staff development and guest-recovery improvements through normal budget.
Not charity theater.
Then Nora Bennett received an invitation for complimentary stay.
She declined.
“I don’t want to recreate it.”
Fair.
The company reimbursed her documented out-of-pocket costs from prior incident and refunded original hotel amount already done. Offered compensation through guest relations.
She accepted only actual documented costs and a modest service-recovery credit for future use? Maybe she declines credit. Fine.
Then Nora said:
“I’d rather you fix the phone number.”
“What phone number?”
The support number she called routed third-party guests back to booking agencies with no hotel escalation.
Another process gap.
They fixed escalation.
Nora’s contribution mattered more than a free suite.
Then Ethan and Lily finally returned home.
The roses from Chicago traveled badly.
Only four survived.
Lily chose blue vase.
Sarah would have hated it.
They placed roses on kitchen table.
No hotel.
No cameras.
No anniversary itinerary.
Lily drew another picture.
Mommy.
Dad.
Lily.
Rabbit.
Blue vase.
Ethan realized this ritual felt lighter because it belonged to them, not a place.
Then she asked:
“Are you still mad at the hotel?”
He thought.
“No.”
“Are you mad at the ladies?”
“Not exactly.”
“Why?”
“Because being angry can tell you something went wrong. It doesn’t always tell you what to do next.”
Lily considered.
“That sounds like boss stuff.”
“Yes.”
“Boring.”
Very.
Then Sarah’s old email notification? Ethan might find another archived message. Could seed final reveal. He revisits old cloud backups and finds a message Sarah sent after last Regent stay. She had complimented a housekeeper by name? Perhaps Lupita! That could be poignant but maybe too coincidental. Need grounded. Sarah may have written guest feedback praising housekeeping team; if Lupita was there 17 years, possible but coincidence. Could be powerful if not overdone. Let's do not same person maybe Elena? Better no random.
Instead, he finds complaint Sarah made three years ago? Sarah noticed front desk classism? Too convenient. Avoid.
Maybe Sarah's email says "If you ever want to know how hotel works, ask person making bed, not person presenting dashboard." Could foreshadow Lupita but a little convenient. We can use general letter previously seeded. Perhaps not.
Then Daniel called.
The root cause review found one final uncomfortable statistic.
Corporate executive complaints were resolved on average in 1.8 days.
Ordinary guest complaints:
6.4 days.
High-tier loyalty guests:
2.3.
Third-party guests:
8.1.
Status changed speed at every level.
Not only front desk.
The company had encoded hierarchy into response times.
May you like
Luxury segmentation, once again, had crossed into dignity.
Cliffhanger: Even after the Grand Regent corrected its lobby culture, Ethan discovered the company still resolved complaints dramatically faster for executives and elite guests than for ordinary travelers—meaning status bias was embedded not only in attitudes, but in corporate service architecture.
Related Stories
