I keep seeing the same wall in corporate rooms. A long row of boxes, one for each department, with a smile at the start and a tick at the end. The people who drew it worked hard. The customer who rang yesterday still has to tell the story again before anyone can help.
If you're about to pay for a day on this, read the agenda before you read the method names. Look for one named experience and one moment the team will change before they leave. If the session ends on a poster and a promise to share it later, you've paid for a picture.
The experience you bring
The best days I run start from an experience the business is already worried about. A claims path customers abandon. An onboarding sequence that generates the same complaints every month. A renewal conversation the sales team dreads. A made-up persona lets everyone be polite, and polite people learn very little they can use on Tuesday.
Pick one experience that matters to revenue, cost or trust. Write it as something a person is trying to get done, with a start and a finish. A target such as reducing churn gives the room no sequence to follow. A small business owner trying to change a plan, and giving up partway through, gives the room a sequence it can map. I push back on the target version before we lock a date. The day exists to find the moment that's costing you, and a target hides the moment.
Bring what you already have. Complaint logs, drop-off points, call notes and the last round of survey comments help the team choose where to look. They don't replace a conversation with someone who lived the experience. Use them to decide who to invite, then let that person correct the file.
One actor on the map
The Nielsen Norman Group describes a journey map as a picture of the process a person goes through to reach a goal, and argues for one point of view on each map. A student and a lecturer at the same university don't move through the same sequence, and a single map that tries to hold both of them becomes a blur. The useful map names one scenario and the expectations that come with it. It shows the phases and what the person does and feels. It also names who owns the change that follows.
Buyers skip that last piece. Mapping forces a shared picture, because success metrics usually sit inside separate teams and nobody is responsible for the whole experience from the user's side. I've watched that play out. Marketing owns awareness. Operations owns the queue. Product owns the screen. Each team can hit its number while the customer is still stuck between them.
Ask the facilitator whether the day will hold one actor or a collage of them. A good answer names the person and the goal. A vague answer about customers in general tells you the map will describe the company. If you need both a buyer and a user, you need two maps. Merge them and you'll lose both.
See it from the outside
In our customer experience workshop the team picks that one experience, then builds the picture from interviews, artefacts and frontline stories. The failure mode we design against is a map that follows the org chart. The customer moves through a different sequence, and the day has to show that sequence. Surveys that get reported while the broken moment stays broken belong in the same pile as the org-chart map.
Someone on your side has to recruit the customers or the frontline staff before the day. When nobody owns the recruiting, the interviews quietly become a panel of colleagues. Colleagues know where the pain sits. They also built the current process, and they will defend it when they're asked to play the customer. Frontline staff are different. They hear the story every day. Put them in the room as witnesses, and put a real customer in a slot if you can.
On a half day we work from evidence you already hold, plus a small number of live conversations. On a full day there is room to map the steps, the emotions and the handoffs, and to test one change before people go home. Both formats run in person or remote. The remote version needs shorter blocks. A long stretch of silent sticker work on a webcam wears the room out before the useful argument starts. The customer conversations still work well over video, provided someone has booked them.
Where this sits next to design
This day aims at an experience a customer already has with you. The longer note on getting users into the work, when you're still designing the service, sits in how to design a service with its users. If the brief is still a solution looking for a problem, read what a corporate design thinking workshop should cover before you book a journey day. Solve the right problem is the note I send when a sponsor has already chosen the feature and wants the room to decorate it.
Buyers sometimes ask me to run both in one afternoon. The muscles overlap, and the outputs don't. A design day can end with a new problem statement. A customer experience day should end with one moment on an existing journey that the team has already tried to change. If you need both, book them as two sessions with a shared sponsor, so the evidence from the first can set the brief for the second.
Friction and one fix
Once the sequence is on the wall, the team has to choose. Every step will have a grievance. The day earns its cost when the room ranks the few moments that create the most friction and commits to one change a customer could actually feel. A wall of ideas with dots on them feels democratic and leaves the backlog untouched.
I want the new moment in a form someone outside the team can react to on the same day. A rewritten letter, a role-played call, a paper screen or a changed handoff between two teams will all do. The test can be rough. It has to be real enough that a customer or a frontline person can tell you where it still fails. A ranked list of concepts stops one step too early.
Give that fix an owner before anyone leaves, and put the next check in the calendar while the room is still there. Ask who owns the change and how you'll know it worked. If nobody in the room can answer, you've got a diagram and no fix.
Who should attend
Bring the people who touch the journey, and keep them together. Service teams, product and operations each hold a slice. The friction between them is the point. A room of only service staff will draw a careful map and then discover that the team who can change the system wasn't invited.
Keep a sponsor for the moment you choose the fix and for the readout. A sponsor who opens the day and leaves before the evidence arrives will overrule the team later from a slide they didn't see built. The room needs the people who serve customers, and the evidence you already collect. A separate research department is optional.
Leaders who want customer focus to show up in decisions should stay through the choice. That's the uncomfortable part. The map will often implicate a handoff their own function created. If they're absent, the team will sand the edges off the finding before it travels upstairs, and you will have paid to confirm what the intranet already says.
What to read in the proposal
Some warning signs show up before you sign. The agenda lists a stack of canvases and no customers. The pack promises a mindset shift and never names an output. The facilitator offers a generic case from another industry so the team can practise without touching a live complaint. Any one of these means the day will feel busy and the service will look the same next month.
Another sign shows up in the room. People present to each other, cluster sticky notes and never sit with someone who uses the service. The energy is real. The customer is absent. You will leave with a tidier version of the assumptions you walked in with.
What to ask before you book
- Will the day run on one live experience we name, with one actor and one goal?
- Who recruits the customers or frontline staff, and will the team actually hear them?
- What will we hold at the end, and will a person outside the team have seen the fix?
- Who owns the change on Monday, and when will we check whether the customer can feel it?
The last question separates a workshop from a wall. If the answer is a steering committee with no date, you're buying a diagram. Ask it on the call, while changing supplier is still cheap.
After the workshop
Leave with the fix, the owner and the date. If the mapping shows that you have been solving the wrong problem, that's a useful day, and the next booking should take the problem you just found. If the fix holds and turns into a bet about what customers will adopt, test that bet with evidence before the business case gets thicker.
Regulated teams can do this work as well. The interviews and the rough test have to stay inside the rules you already live with. A role-play and a rewritten notice can teach you a lot without putting a customer or a licence at risk. The constraint belongs in the brief, so the room designs a test that can actually run.
If you want to book the day, send me the experience the way a customer would describe it, and the names of a few people who live with it. We will shape the workshop around that experience and plan the conversations with you.
