Chapter 8
The hardest project of my career had nothing to do with hidden reports.
It was a hotel expansion on the lakefront.
Three hundred new rooms.
conference center.
parking structure.
pedestrian bridge.
Publicly visible.
Politically sensitive.
Expensive.
I was fifty-one and responsible for owner-side operations integration.
Not engineering.
Not construction.
Still:
every department eventually brought problems to me.
The first major one:
foundation settlement.
Monitoring points showed:
one corner of the new conference center had settled more than predicted during early construction.
Not dramatic.
Millimeters.
Engineers noticed:
trend.
They issued:
monitoring hold on adding certain heavy interior finishes in one zone.
No one panicked.
Then developer representative said:
“Can we keep non-structural interior work moving?”
Engineer:
“Some.”
There.
Scope.
Affected:
stone flooring,
heavy partitions,
large mechanical equipment placement.
Allowed:
painting,
light electrical,
some ceiling work,
work elsewhere.
The project did not freeze.
Then geotechnical review found:
one old buried utility trench had softer backfill than historical drawings showed.
No fraud.
No secret.
Old city records incomplete.
Solution:
localized underpinning and soil improvement.
Cost:
$1.8 million.
Delay:
three weeks.
The developer asked:
“Can we avoid telling the conference client until schedule impact confirmed?”
I felt old instinct.
We had a client with:
opening-month booking.
Contract required notice if:
material delay likely.
At that moment:
not likely yet.
So:
do not alarm prematurely.
But document internally.
Then weekly model showed:
opening date still achievable through resequencing.
No client notice required.
Good.
Transparency is not:
tell everyone everything instantly.
It is:
tell the right party when threshold is met.
Then another issue.
A subcontractor claimed underpinning work was unnecessary because its own consultant said settlement would stabilize.
Two professional opinions.
We did not choose:
the one that preserved schedule.
We commissioned:
independent peer review.
Peer reviewer agreed:
localized reinforcement prudent.
Not because first engineer automatically right.
Because evidence.
Then subcontractor accepted:
reservation of rights on cost.
Work proceeded.
No one needed to admit:
“wrong”
before safety action.
That mattered.
Then a union crew member reported:
supervisor had told workers to continue in an area marked monitoring hold.
I froze.
The pattern felt familiar.
We investigated.
The “hold” sign had:
yellow border.
It said:
MATERIAL STORAGE HOLD
NO PALLETS OVER 1,000 LB
Workers were:
installing light conduit.
Allowed.
The employee had interpreted:
no work.
Supervisor had said:
“keep working.”
Technically correct.
But signage ambiguous.
We changed:
hold signs list prohibited activity.
Not just:
HOLD.
Words need scope.
That came straight from my earlier overreaction.
Then the big mistake.
Mine.
The project had:
weekly executive dashboard.
Schedule.
budget.
safety.
quality.
design changes.
One metric:
OPEN TECHNICAL HOLDS.
Executives hated seeing:
five,
six,
seven.
They asked:
“Why so many?”
Project team started closing minor holds faster.
That looked good at first.
Then I noticed:
one hold closed because:
“work package completed.”
Not because:
engineer released.
I asked.
Project coordinator said:
“The affected work is over.”
That is not release.
If underlying issue still matters for later operations, closeout needs:
resolution,
not disappearance of task.
We audited:
all technical holds.
Two were administratively closed too early.
No unsafe work.
Still:
bad data.
I realized:
the metric itself was pushing closure.
Again.
So dashboard changed:
OPEN HOLDS
OVERDUE ACTIONS
UNRESOLVED TECHNICAL QUESTIONS
No target:
zero.
Because zero is not always good during active construction.
Sometimes zero means:
nothing reported.
Then owner asked:
“What is the right number?”
No universal answer.
That frustrated him.
Useful metrics often resist:
one clean target.
Then project opened:
two weeks late.
Not because foundation issue alone.
Weather.
late kitchen equipment.
fire-alarm programming.
Multiple.
Press blamed:
“structural problem.”
Wrong.
We published:
final engineering certification.
occupancy approval.
project summary.
There was no value in arguing with every headline.
Then during first month:
one elevator stopped repeatedly.
Guests complained.
Internet:
NEW HOTEL FALLING APART.
No.
Elevator door sensor alignment.
Fixed.
People love structural metaphors.
Operations learns humility.
Then one year later:
building performed well.
Foundation monitoring stable.
No settlement progression.
The problem had been:
real,
managed,
not apocalyptic.
That became my favorite example of mature risk.
Not:
nothing happened.
Something happened.
People saw it early.
Paused specific work.
Checked.
Fixed.
Recorded.
Moved on.
No blood.
No envelope.
That was success.
Then Luca called.
Not often.
He said:
“I heard your hotel had foundation trouble.”
“Minor localized settlement during construction.”
“So not sinking into lake?”
“No.”
“Disappointing.”
“You’re terrible.”
Then:
“South River had a roof leak.”
I laughed.
“See?”
“Buildings age.”
He said:
“Apparently engineers refuse to guarantee immortality.”
“Scam.”
Then he became serious.
“Claire says I still interrupt people when I think I know the answer.”
“That sounds plausible.”
“She says I should ask more questions.”
“Also plausible.”
Then:
“Did I interrupt you that night?”
I remembered:
plates,
floor,
envelope.
“No.”
“Why not?”
“You were too confused.”
He laughed.
Then:
“Maybe confusion helps.”
Sometimes.
Certainty is useful when earned.
Dangerous when borrowed.
Then Vanessa reentered public attention.
Bellini Hospitality Studio won:
design contract for a civic arts center.
A critic brought up:
South River.
Asked:
“Why should someone with a safety scandal be trusted on public project?”
That framing was inaccurate.
Her misconduct touched:
schedule pressure and workplace conduct.
She had not designed bolts.
She answered:
“The South River material defect was not caused by me.”
“My conduct during that incident was still wrong.”
“I interfered with a technical hold I had no authority to influence.”
Specific.
Then:
“The public project has independent engineering, procurement, and oversight.”
“My role is interior design.”
Good.
The arts center hired her.
I had no formal role to object, and I probably would not have objected anyway.
People should not be permanently disqualified from unrelated work if risks can be controlled.
Then I received:
an invitation
to a construction-governance conference.
Panel title:
WHEN IMPORTANT PEOPLE GIVE UNOFFICIAL ORDERS.
I laughed.
I joined.
Speakers:
me,
Aaron Mills,
project lawyer,
union safety representative.
No Vanessa.
We discussed:
owners,
donors,
family members,
politicians,
celebrity clients,
executives.
The problem was not rich fiancées.
The problem was:
organizations allowing status to substitute for role.
Union representative said:
“Workers need one sentence they can use.”
He proposed:
“Who is the authorized release person?”
Excellent.
No confrontation.
No:
you’re not my boss.
Ask:
“Who is the authorized release person?”
Then the lawyer added:
“If nobody can answer, the hold stays.”
Simple.
We put it on slide.
Then Aaron told South River story without names.
He said:
“A person with no project authority sent a schedule message.”
“Formal managers treated confidence as clearance.”
“That was the governance failure.”
Then I said:
“And in the household, an employee was asked to carry a hidden document because another person believed employment insecurity would keep her quiet.”
Silence.
Then:
“Those are different systems.”
“Same informal power problem.”
The room understood.
Then one attendee asked:
“How do you prevent it completely?”
You do not.
You:
clarify roles,
preserve records,
allow challenge,
separate technical release,
protect reporting,
audit exceptions.
Then people still make mistakes.
No perfect design.
Then my hotel group adopted:
Unofficial Direction Log
for major projects.
I hated the name.
But useful.
If anyone outside formal project authority requests:
schedule change,
scope change,
hold release,
workaround
the recipient logs:
request,
requester,
formal decision.
Not to shame.
To prevent:
“we thought they approved.”
The first month:
thirty-two entries.
Most harmless.
Owner asked:
change paint.
Chef asked:
move outlet.
Marketing asked:
open terrace sooner.
Formal teams decided.
By month three:
fewer ambiguous instructions.
People learned.
Then one billionaire guest told contractor:
“Move that wall six feet.”
Contractor smiled.
“Happy to price it through the project team.”
Perfect.
The guest laughed.
No offense.
Good systems can be polite.
Then I realized something.
For years, I had remembered Vanessa’s power as:
threatening.
But much of power is not threat.
It is the expectation:
people will comply before anyone asks whether they should.
The best controls do not require confronting powerful people.
They make compliance with the wrong request harder than routing it correctly.
That was the kind of system I wanted to leave behind.
One benefit of the unofficial-direction log appeared during the lakefront expansion.
A donor to the hotel foundation asked the landscape contractor to replace:
native plantings
with imported ornamentals before a gala.
The contractor logged the request.
Landscape architect reviewed:
imported species would require irrigation changes and violated part of the approved sustainability plan.
The donor was told no.
He complained.
Then read the original commitment and backed down.
No one had to say:
“You have no authority.”
The log transformed a social request into a technical decision.
That is what good process often does.
It lets people save face while still preserving the boundary.
The unofficial-direction log also protected executives from false memory.
Months later, a senior donor insisted:
“I never asked them to change the garden plan.”
The log showed his exact request:
“Could we explore replacing the native bed near the entrance?”
That was not an order.
The contractor had correctly routed it as a request.
The donor read the entry and laughed.
“You’re right.”
“I asked.”
“I didn’t approve.”
May you like
No conflict.
Without the log, everyone might have remembered the conversation differently and turned a harmless question into a dispute.
