A team can leave a customer experience session with a rewritten step, a named owner and a sketch everyone liked, and still have no way to tell, a month on, whether the person using the service was better off. The room did the work. The service absorbed it. If you are about to book the day, the missing line is the one that says how you will know the change had the effect you expected.
Point 10 of the UK government Service Standard asks a service team to define what success looks like and publish performance data. The point says to work out what success looks like, and to identify metrics that show what is working and what can be improved, combined with user research. The reason it gives is plain. With the right measure, you know whether the service is solving the problem it is meant to solve. When you change the service, you can tell whether the change had the effect you expected. For services funded by public money, the same point asks the team to publish the figures. A company can keep its measure inside the building. The test travels either way.
The measure that belongs to the fix
The path, the person on it and the interviews are the subject of the notes on what the workshop should fix and on the agenda to read before you pay. This note is the line those days still drop. Once the experience is named, write the measure that belongs to it, before the facilitator arrives. A claims step people abandon needs a count of people who now finish that step, not a company-wide satisfaction average. A handoff that drops the story needs a count of people who had to tell it twice. The standard is explicit that the numbers sit with what you learn from users, so a dashboard with no conversation is not the booking either.
A target such as churn, with no moment attached, gives the room a score and no place to stand. Attach the number to the moment. Write the baseline from the last period you already trust, the owner who can read the same number after the change, and the date you will look. If nobody owns the read, the fix will be declared a success because the workshop felt serious.
What a poster cannot answer
Ask the proposal where the baseline will be read from, and what movement would count as the effect you expected. A weak answer talks about alignment, a heat map and a readout. A useful answer names the experience, the figure, the source of the figure and the person who will bring it back. Ideas generated, dots on a wall and a promise to socialise the map are activity. The Service Standard's test is whether the service got better at the problem, and whether you would notice if it had not.
Agree the measure while the people who dispute it are still in the room. A product owner and a frontline lead will not share a definition of finished unless they say it aloud. Write their sentence down. If the figure can be improved by changing the count, without changing the experience, it is the wrong figure. Pick one a customer would recognise if you described it back to them. Look again on the date you named. If the figure has not moved, and the experience is unchanged, adjust the fix or retire it.
Collective Campus is building high-performance culture and teams for the AI world. The customer experience workshop is for a team that can name the experience, the person in it, and the measure that will show whether the fix worked. A feature that shipped before anyone asked is the subject of the feature the customer never asked for.
What to bring
Bring the experience, the baseline and the name of the person who will read the same figure after the change. If you cannot say what would count as the effect you expected, you are not ready to book the day.
