Systems Detective The Iceberg Method™

Sample Boundary Map

Anonymized example — your map would be tailored to your operation.

A 5-star European hotel group

A 12-property luxury hospitality brand operating across European cities, competing on a human-led promise: presence, anticipation, and judgment at every guest touchpoint. The engagement examined the guest experience function end-to-end — pre-arrival, in-stay, and post-departure — where the boundary question between human craft and automation had become operationally urgent.

What the client originally said

Guest satisfaction scores were stable in the dashboards, but post-stay reviews had started mentioning that the experience “feels less personal than it used to.” Front desk staff were escalating more decisions upward, and team leads couldn’t name a single process that had changed. Operations wanted to automate concierge requests for speed and consistency; the brand team was blocking the move without being able to articulate why. The C-suite framed it as a front-of-house problem.

What the work actually revealed

The friction was not where guests encountered automation. It was where automation had quietly absorbed micro-decisions that used to require human taste — room assignment for repeat guests, gift personalisation, complaint routing, and the small choices that once moved through a duty manager’s judgment. The brand promise lived inside those decisions, and the team had migrated them out of human hands without noticing. The guest felt the absence long before the metrics did.

Front desk wasn’t the problem. The back-of-house decision migration was.

Three zones — guest experience function

Each item carries a “what changed” annotation: the specific boundary call we made during synthesis, and why it produced a better outcome than the existing setup.

Zone A — Human-led

Trust, taste, and presence

Work that must stay in human hands because the brand promise lives inside the decision itself.

Zone B — Agent-assisted

Agents prepare, humans decide

Work where agents do the preparation and a human still makes the final call before the guest sees anything.

Zone C — Automation

Runs autonomously, anomaly review only

Work where repetition, low consequence, and clear rules make automation safe — with sampled human review for drift.