Build a Ninety-Day Experience Plan Around One Customer Occasion

A customer-experience plan can expand until it includes almost every problem in the business. Booking, service, technology, training and communications all appear on the list. The ambition is understandable, but the breadth can prevent the team from completing a coherent improvement anywhere.

One way to make the work manageable is to choose a specific customer occasion and follow it from beginning to end. A family lunch, a short business stay or a celebration package provides a practical boundary without pretending that departments operate independently.

Establish the baseline in the first month

Define the occasion precisely enough that the team knows which visits belong in the review. Explain why it matters commercially and what the customer is trying to achieve. Avoid choosing a segment solely because it is easy to measure.

Observe the current journey, review relevant feedback and examine the operating evidence already available. Record where the customer encounters uncertainty, where staff must improvise and where the promise differs from delivery. Include successful visits so the plan protects what works.

At the end of this stage, select the most consequential issue that the business can realistically influence. State the evidence, the working explanation and what remains unknown. That discipline prevents a familiar solution from being attached to an unrelated problem.

Use the second month to test a connected change

Design an intervention that reaches the cause. If booking information creates the wrong expectation, changing a service script alone will not resolve it. If staff lack authority, another reminder to respond promptly will not help them decide.

Keep the trial bounded enough to learn from. Define who is involved, what changes and what evidence will be reviewed. Include the effect on employees and adjacent services, rather than measuring only the most flattering customer outcome.

Explain the purpose to the team and provide a route for reporting unexpected consequences. A trial is not a promise that the first version is correct. It is a structured way to discover whether the proposed change improves the occasion under real conditions.

Decide in the third month

Review the evidence and choose whether to retain, adapt or stop the intervention. Compare like with like where possible and acknowledge limitations such as changes in demand or staffing. A small pilot may justify a next step without proving a universal result.

If the change works, update the relevant instructions, information and ownership so it becomes normal practice. If it fails, preserve the learning and revise the explanation. Do not declare success merely because the project reached its final meeting.

The ninety-day period is a planning device, not a guarantee that every issue can be solved in that time. Some decisions need investment or specialist work. The useful outcome may be a well-supported case for that next stage, with the immediate operating response made clearer.

FUSION keeps Brand, People and Operations attached to the same customer occasion. It prevents each function from completing its own activity while the overall experience remains unchanged.

Q Branch helps leaders turn broad ambitions into decisions that can be tested. Start with one occasion, improve it coherently and use the evidence to choose where the next cycle should begin.