What a journey mapping workshop costs and how long it runs

On-Off Group

October 2026

A journey mapping workshop is priced by length and how much preparation goes in beforehand, and usually runs from half a day to two days with the people who actually handle the journey. It gives you a shared map and agreed next steps, not customer evidence, so budget separately for research if you need a before number.

If you are choosing between a journey mapping workshop and a round of user testing, here is what each one gets you. Length, cost drivers and the gaps in both are below.

We have run these sessions for Philippine banks and insurers since 2015. What follows is what the money actually buys, how long the session runs, what you have to bring, and where a workshop will let you down.

We do not publish a single price because the figure moves with the length and the number of people. Length and the number of people in the room move the figure more than anything else, and the custom workshop pricing and preparation page covers the cost.

What you get for the money

A journey mapping workshop puts the people who handle one journey in the same room for a fixed time. Branch staff, the ops person who fixes the exceptions, someone from compliance, the developer who built the form. On a normal working day those people rarely walk through one customer's steps in order together.

So the cost is mostly time. A facilitator, the preparation before, the write-up after, and the hours of your own people that you take off other work. That last one usually gets left out of the business case.

What comes out is a map of the real steps, the points where the customer waits, and an agreed list of what to fix first. No customer evidence though. Nobody in that room is a customer.

Half a day, one day, or two

Half a day covers one journey, start to end, with about eight to twelve people. You will get the map and the obvious problems. You will not get to solutions.

A full day gets you the map plus the three or four steps that cause most of the pain, with a rough fix sketched next to each one. That is usually the size worth booking.

Two days is for when the journey crosses departments and you need the handover arguments settled in the room rather than by email afterwards. Account opening at a bank usually needs the two days, because branch, ops and compliance all hold part of it. Claims at an insurer, too.

Anything longer stops being a workshop. A five-day design sprint is a different thing: you map, you build and you test with customers inside the week. On a series of those with a large insurer, web journeys that used to take six months or more were designed, tested with customers and live in four weeks. The client measured completion rates on the new journeys rising 80 per cent against the old ones, and the previous drop-off points disappeared.

A workshop will not give you a before number

The most common failure is having nothing to compare against afterwards. You run the session, everyone leaves happy, work starts. Six months later your boss asks whether it worked, and you have nothing to compare against because nobody wrote down the turnaround time before the change.

So pull the numbers before the workshop, not after. Current turnaround time on the journey you are mapping, end to end. Drop-off at each step, if your analytics can see it. Volume of calls about that step. Even rough figures from the ops team are better than none, as long as you write down how you got them.

Bring those numbers into the session and work out what they mean. A long map and a wall of sticky notes are easy to produce and easy to forget. There is a longer piece on how to get a drop-off number out of a journey mapping session.

When a research project is the better spend

A workshop tells you what your own staff think happens. Putting five real users on video tells you what customers actually do.

If your team already agrees where the problem is and you need proof, spend the money on watching real users. Five people on video going through your onboarding flow will show you the step where they stop, and you will have a baseline number to measure against later.

If your team does not agree, or two departments each blame the other, the workshop is the cheaper first move. Research will not settle an argument about who owns the step.

What tends to work: half a day to map and agree, two weeks of user testing on the worst step, then a short session to decide the fix. Roughly the same spend as one long workshop, and you end up with a number you can quote.

What you need to bring

When these sessions go badly, it is usually one of four things.

No real journey. "Our customer experience" is not a journey. "Opening a savings account in a branch in Cebu" is.

Wrong people. Heads of department mapping a process they have not done themselves produces a tidy map that nobody in operations recognises. Bring two or three people who touch the journey daily.

No decision maker. If nobody in the room can approve the next step, nothing happens to the map afterwards.

No data. Even one number, like average turnaround time last month, changes the conversation.

And be clear about what happens after. If the fix turns out to be software, that is a separate piece of work with its own timeline, which we cover in what building an AI feature with us involves and how long it takes.

What to do this week

Write down the one journey by name, with a start point and an end point.
Ask your analytics or ops team for current turnaround time and drop-off on that journey. Take whatever they can give you.
List the six to ten people who actually touch it, including branch staff, and check who can approve work in the room.
Decide which you need first, agreement between departments or evidence from customers, and spend on that one.
Book the session for a length that matches the scope. Half a day for one journey, two days if it crosses departments.

Questions people ask

How long does a journey mapping workshop take?
Most run from half a day to two days. Half a day gets one journey on the wall with the people who work on it. Two days lets you map, cut the map down to the worst steps and leave with owners and dates.

What drives the cost of a journey mapping workshop?
Length, how many people are in the room, and how much preparation happens before the session, including pulling drop-off and turnaround time data and briefing branch staff.

Will a workshop prove the journey improved?
No. A workshop produces agreement and a plan. Proof needs a measurement before you change anything and the same measurement after, plus customer research if you want to see where people actually get stuck.

What should we bring to the session?
One named journey, whatever numbers already exist on it, two or three people who handle it daily, and a decision maker who can approve the next step in the room.

On-Off Group trains teams, tests products with real customers, finds where a transformation has stalled and builds what gets it moving, for banks, insurers and enterprises in the Philippines, since 2015. How we help with customer journey mapping.