Journey mapping without sticky notes: get a drop-off number instead

On-Off Group

September 2026

Run the mapping session, but come out of it with a number: where people drop off in the customer journey, and how long the step takes today. Watch real users try it, then you have a baseline to compare against after the fix.

If you have run journey mapping sessions and your boss then asks how long onboarding takes and how many people give up, this is about how to have those two numbers.

Same exercise, but done with real customers, screen recordings, and a number written down before anything changes. What you end up with is a video reel, a drop-off point you can point at, and a baseline to compare against later.

It takes longer to get going. It is also much harder for anyone to argue with.

What you have at the end of a mapping workshop

A normal mapping session goes like this. Ten or twelve people from digital, branch operations, compliance and marketing in a room for a day. Everyone describes the customer journey as they understand it. The wall fills up. Somebody photographs it. The photo goes into a PowerPoint and the PowerPoint goes to the steering committee.

What is on that wall is what the people in the room believe. Some of it is right. The parts nobody owns are usually missing, and the handoffs are where the customer actually drops out.

Then three months later your boss asks whether the new flow is better. You have a map, a redesign and a launch date. You have no turnaround time from before, and no completion rate from before. So you shrug, or you quote a satisfaction score that nobody trusts. That is what mapping from memory costs you. The day was not wasted, but it gave you nothing you can show.

Build the map from screen recordings

Start with five real users going through the live journey while you watch. Not staff. Not a focus group talking about the journey in the abstract. Five people trying to open the account or file the claim on their own phone, screen recorded, thinking out loud.

Five is enough. The same two or three points of failure keep showing up. You do not need a hundred people to see that the ID upload rejects a photo with no explanation.

Then build the map from the recordings. Each step gets a timestamp, a pass or fail, and a clip you can play. Nobody has to take your word for it. When branch staff say customers never complain about that step, you play the clip of someone giving up on it.

The reel does more work than the map. A steering committee will pick holes in a map for an hour. Play them a clip of a customer giving up and the room goes quiet.

Write down the baseline before you touch anything

Pick two or three numbers you can measure today, on the live journey, and record them before the redesign starts.

Usually it is these:

Turnaround time end to end, from first tap to approved.
Completion rate: of the people who start, how many finish.
Where the drop-offs cluster, by step.

Write them on one page and date it. Without that page, the pilot ends in a slide pack, because there is nothing to compare the after number to.

Most teams we work with do not have this. "Did it work?" gets answered with a shrug, because nobody captured the before. And once the new flow is live, the before number is gone for good.

If the numbers turn out small, say so. A completion rate that moves two points is still a real result, and it is more useful to you next quarter than a claim you cannot defend.

Then design and test it in two weeks

Once you know which step fails, you do not need six months of workstreams. On a series of five-day design sprints with a large insurer, customer-facing web journeys that had previously taken six months or more to get out were designed and tested with customers in two weeks, and live in four. Time to market went from around 26 weeks to 4.

The client measured it afterwards, because there was a before number to measure against. Completion rates on the new journeys rose 80 percent, and the old drop-off points were gone.

The order matters. Watch real users, write down the before number, design against the step that failed, ship something small, measure again. Skip the before number and you have the same redesign with nothing to defend it with.

Workshops still have a place. Rooms are how you get branch staff, compliance and digital agreeing on the same version of the journey in one sitting. Here is a design sprint we ran with Meralco, for an example of the room and what came out of it. What changes is what you bring in with you: clips and numbers instead of everyone's best recollection.

What to do this week

Pick one journey your boss keeps asking about. Onboarding, a claim, a top-up. One.
Write down today's turnaround time and completion rate for it. If nobody has them, that is the finding, and getting them is the first task.
Recruit five real customers and record them using the live journey on their own phones.
Cut a three-minute reel of the worst moments and play it at the next review, before any recommendation.
Keep the baseline page. Date it, and compare against it after the pilot ships.

Questions people ask

Why does the sticky note map on its own not hold up?
A wall of sticky notes tells you what the team thinks happens. It does not tell you how many people abandon the onboarding flow or how long turnaround time actually takes, so nobody can say later whether the pilot worked.

How do we get a drop-off number if we have never measured one?
Watch a handful of real users go through the journey on video, count where they stop or get stuck, and record the turnaround time on the same step. That count is your baseline, even if it is rough.

What do we do with the number once we have it?
Fix the step it points at, then measure the same thing again the same way. Small honest numbers you can compare before and after beat a big claim with nothing behind it.

Where can we see more of this work?
Workshop scripts and the projects they came from are at onoffgroup.com.

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.