Chapter 6
At thirty-eight, I went back to work for Russo Hospitality.
Not the estate.
Not Dante directly.
Marwick House had been sold to a national chain.
My role changed.
Benefits worsened.
Corporate management wanted banquet managers doing three jobs.
A director position opened at Russo Hotels:
Employee Operations and Event Standards.
I applied.
Then almost withdrew.
History.
Everyone would assume:
Dante gave it to me.
The recruiter said:
“He is not on the hiring panel.”
Good.
Finalists:
four.
Interview:
labor planning.
guest conflict.
vendor oversight.
staff safety.
case exercise.
I got it.
Before accepting, I asked:
“Does Dante approve this role?”
Recruiter laughed.
“The board approved it.”
Better answer.
Then first week, I told Sophie.
She was seventeen.
“You’re working for them again?”
“For the hotel company.”
“Does Mr. Russo know?”
“Probably.”
She stared.
Then:
“Are you sure you’re not emotionally addicted to complicated employers?”
Teenagers.
I threw a pillow.
Then role.
I managed:
event staffing standards.
training.
family/VIP request boundaries.
overtime audits.
vendor worker complaints.
Not:
employee investigations alone.
Not:
legal determinations.
Not:
Dante’s household.
That separation mattered.
Then I saw Dante in headquarters hallway.
“Emma.”
“Mr. Russo.”
He sighed.
“You’re a director.”
“Yes.”
“You can call me Dante.”
“No.”
We both smiled.
Then:
“I had nothing to do with your hire.”
“I know.”
“Good.”
Then he left.
That was all.
Then my first major project:
VIP authority.
At hotels, powerful guests constantly said:
“Dante said.”
“Ownership wants.”
“Family requested.”
Sometimes true.
Often:
half true.
We built:
request verification channel.
If owner/family wants operational change:
documented through authorized contact.
No more:
cousin says move employee.
friend says comp suite.
fiancée says fire server.
Then staff feared:
this will annoy VIPs.
Yes.
One investor called me:
“Do I really need to email to move a dinner table?”
“No.”
“You can ask banquet staff.”
“What requires authorization?”
Schedule changes.
staff discipline.
security access.
private employee information.
financial commitments.
rule exceptions.
Good.
Not bureaucracy for chairs.
Then one case tested.
Dante’s cousin Marco complained that a bartender was “rude.”
He wanted:
bartender removed from future family events.
Manager nearly complied.
New process:
document complaint.
interview bartender.
Bartender said Marco demanded:
double pours after bar cutoff.
Bartender refused.
Witnesses confirmed.
Outcome:
no discipline.
Marco reminded:
family complaints do not control staffing.
Dante heard.
Called Marco, not bartender.
Good.
Then bartender asked:
“Am I blacklisted by family now?”
“No.”
We showed:
future scheduling based on manager.
If any retaliation:
report.
No promise:
family will like you.
Just:
job not controlled by liking.
Then vendor labor.
Russo hotels used:
floral.
AV.
security.
temp banquet agencies.
One temp agency billed:
twenty workers.
Workers reported:
eighteen present.
Audit:
ghost billing?
Not exactly.
Agency had billed minimum twenty under contract.
Legal.
But workers believed hotel was “paying for” two absent people and blamed agency.
Communication.
Then another issue:
temp workers received lower meal benefit than direct staff.
Policy allowed.
Was it fair?
Not necessarily.
We standardized staff meal access during events regardless employer.
Small.
Then one security vendor asked for:
employee home addresses for “risk screening.”
No.
Identity verification could occur through employer.
Home addresses unnecessary.
I had learned from other failures:
security can expand because fear makes every data request sound reasonable.
Then Sophie turned eighteen.
She asked for:
summer internship at Russo corporate archive.
My body screamed:
absolutely not.
Then facts.
She was studying:
history and information science.
Archive role:
paid.
open application.
independent university partnership.
No reporting to me.
No access to her own family’s restricted employment records.
Could she apply?
Yes.
Conflict:
my director role.
I disclosed.
Recused.
Did not write recommendation.
She applied.
Did not get it.
She was furious.
“Did you sabotage me?”
“No.”
“Did Dante?”
“No.”
Then archive manager feedback:
strong writing.
insufficient catalog software experience.
Good.
She took internship at city museum.
Better for everyone.
Then next year, she applied again.
Got it.
I panicked again.
She said:
“Mom.”
“It’s a job.”
Right.
Then archive orientation included:
Rose Reed file restricted.
Employees cannot access records about self/family without formal request.
Sophie followed.
She never opened grandmother’s file.
That mattered.
Curiosity is not authority.
Then she found something unrelated.
A set of old household training manuals.
One from 2001 said:
Staff family assistance may be reconsidered if employee standing becomes unsatisfactory.
There.
The retaliatory instinct had been written into policy.
Not just Evelyn.
That changed history again.
The fund’s design itself allowed:
good standing
as benefit condition.
Vague.
Evelyn abused it, but she had not invented every lever.
Lucia approved manual.
Dante’s mother.
Sophie reported find to supervisor.
Not me.
Archive team reviewed.
Then Dante received historical memo.
He called me.
“Mom signed the policy.”
“Yes.”
“You knew?”
“No.”
Then:
“So Evelyn wasn’t acting alone.”
“Not entirely.”
This mattered.
The family had been tempted to place all bad history on Evelyn.
Convenient.
Now:
Lucia’s governance had formally allowed benefits to depend on employee standing.
Did that authorize self-dealing?
No.
Did it make scholarship retaliation easier?
Yes.
Then corrected narrative:
Original fund combined generosity with discretionary eligibility tied to employment status, creating structural risk of retaliation. Evelyn Bellini later used that discretion in documented conflicts and punitive decisions.
Better.
Then Marcus Bellini read update.
He called Dante.
“I appreciate that.”
Not:
my mother innocent.
Just:
shared system.
Then Bianca?
She heard through Marcus.
No contact.
Good.
Then archive committee asked Sophie if she wanted credit for finding manual.
She said:
“Intern team.”
Correct.
No child hero becomes adult hero sequel.
Then the staff benefit training changed.
Old lesson:
Evelyn retaliated.
New lesson:
discretionary benefits tied to manager favor create retaliation risk even before an abusive manager appears.
That was stronger.
Then I made another management mistake.
One of my hotel managers, Theo Grant, had excellent guest scores.
Also:
high turnover.
Exit surveys:
too demanding.
texts after hours.
favorites.
public criticism.
I liked Theo.
He was efficient.
Funny.
Always helped me during crises.
I minimized.
“Banquet work is intense.”
Then HR analyst showed:
turnover on his team double company average.
I still said:
“Some managers are stricter.”
There.
Familiar.
A person I trusted.
A pattern I did not want to see.
Then a supervisor filed complaint:
Theo cut hours after she challenged unpaid prep tasks.
Audit:
true.
Not huge:
four employees.
total unpaid:
thirty-one hours.
But retaliation.
I felt sick.
We investigated independently.
Theo admitted:
he considered them “not team players.”
Same language.
Useful.
loyal.
difficult.
Old system in new clothes.
Outcome:
Theo removed from management after documented retaliation and prior coaching.
Could he remain employee?
He accepted non-supervisory operations role at another property after review.
Not exile.
Back wages paid.
hours restored.
managers retrained.
Then my own review.
HR asked:
“Did you receive warning signs?”
“Yes.”
“Did you respond adequately?”
“No.”
Formal performance note.
Bonus reduction.
Again.
I told Dante nothing.
He was not my boss.
Good.
Then Sophie, home from college, found me angry at kitchen table.
“What?”
“I missed something at work.”
She listened.
Then:
“Are you going to quit?”
“No.”
“Good.”
I stared.
“Why good?”
“Because you always think consequences mean disappearing.”
That sounded like someone else.
Maybe me.
Then:
“Fix it.”
Teenager became adult.
No dramatic wisdom beyond that.
Fix it.
So I did.
The Theo investigation produced another reform I had not expected.
Several employees admitted they had never used the complaint channel because Theo was popular with executives.
They assumed:
if leadership liked him, reporting would only make them look difficult.
That was exactly how informal power reproduced itself without anyone ordering retaliation.
So we changed complaint acknowledgments.
When an employee reported a manager with senior relationships, the intake note explicitly stated:
the complaint would be reviewed by someone outside that manager’s direct reporting chain.
Not:
we promise you will win.
Not:
the executive relationship does not exist.
Just:
the person being reported does not control the review.
Then we audited whether people who complained lost:
hours,
premium shifts,
training,
promotion interviews.
If changes occurred, managers had to document a legitimate reason.
That did not make every schedule adjustment retaliation.
It made invisible retaliation harder.
Six months later, one audit caught a supervisor cutting a complainant’s weekend shifts.
He claimed:
performance.
The dates showed the cuts began two days after complaint.
Independent review found no prior performance record.
Hours restored.
Supervisor disciplined.
The system worked once.
That did not make it perfect.
It made it real.
One more thing changed after Theo.
Senior leaders stopped receiving informal “favorite manager” lists before promotion rounds.
Not because liking someone was forbidden.
Because praise without evidence can become invisible sponsorship.
Promotion packets now included:
turnover,
complaints,
attendance corrections,
staff-development records,
guest results,
financial performance.
No single metric decided.
A manager could be demanding and excellent.
Popular and harmful.
Unpopular and fair.
The point was to look wider than executive comfort.
I hated that this rule existed partly because I had trusted Theo.
Good.
A policy born from embarrassment can still be useful if it is designed for everyone, not just for the person who caused the embarrassment.
Before I left that role, we changed one more practice.
Executives stopped approving “emergency” schedule changes for favored teams by text message.
Any recurring exception had to be visible in the scheduling system with a reason code.
Not because text messages were evil.
Because invisible exceptions create two workplaces:
the one written in policy,
and the one available to people who know whom to ask.
May you like
That small change reduced complaints more than another round of manager training.
People can tolerate rules they dislike better than rules they cannot see.
