Central Guest Journey & Multi-Venue Coordination

01OBSERVE

Customers experienced one arrival point, but the operation behind it was divided across independently managed venues with different reservation rules, service timings, products, capacity decisions and management ownership. An incomplete update, delayed handover or incorrect decision from one operation could therefore become an immediate arrival or service problem for the same shared frontline environment.

02UNDERSTAND

The main issue was fragmented ownership inside what the customer perceived as one experience. The operations legitimately needed different rules, but shared parts of the journey — arrival information, access, customer status, timing, handover and escalation — could not depend on each venue communicating differently or on frontline employees knowing who to chase during live service. The solution did not require making the operations identical. It required defining where coordination had to be common and where operational differences had to remain visible.

03IMPROVE

The complete arrival journey was mapped around customer states, access dependencies, information ownership, decision rights, venue handovers and escalation. Shared coordination rules were introduced for the points where one operation could affect another, while venue-specific requirements remained separately controlled. Frontline guidance and management communication were structured so the team could understand both the common journey and the exceptions belonging to each operation.

04ADVANCE

The coordination model moved into daily procedures, management expectations, communication routines and training. Recurring arrival issues and venue changes continued to test the model, allowing handovers, escalation and information responsibilities to be adjusted around what actually happened during service. The operations consequently gained a shared coordination layer without requiring independently managed venues to surrender the differences necessary for their own delivery.