Customer research workshop / 5 MIN READ
Map the handoff where the customer loses the thread
Follow one real task across teams instead of drawing a separate journey for each channel.
Original editorial learning framework
Editorial and source review: 6 November 2026
Customers carry a problem across search, sales, payment and support. A journey map is useful when it exposes what the person must repeat, reconstruct or wait for between those steps.
What you will leave with: A handoff map with one specific break, its owner and a testable repair.
Use this when
- Different teams report good performance while customers describe a difficult experience.
- People must repeat information after moving from marketing to sales or support.
This exercise does not turn a handful of accounts into a representative view of every customer.
Reconstruct an actual sequence
GOV.UK experience-research guidance recommends understanding what people did, thought and felt across an experience. The marketing application here focuses specifically on the boundaries between teams and channels.
Choose a concrete task and a recent episode, such as arranging a product demonstration for a branch office. Start before the first brand interaction and continue until the customer achieves the task or stops. Do not begin with the organization chart and ask the customer to fit it. Record uncertainty when the sequence cannot be recalled.
Name what must cross each boundary
At every transition, list the information, expectation or object the customer needs to carry forward. A promised price, appointment time, eligibility condition or completed document may matter more than the channel itself. Ask whether the next team can see it and whether the customer knows what happens next.
Separate a necessary verification from pointless repetition. Some checks protect the customer and should remain, but the reason can be explained. Avoid recommending broad data sharing merely to reduce friction. Carry the minimum authorized information required for the next step and define who can access it.
Locate the first broken promise
Mark the first place the next step differs materially from what the previous touchpoint implied. A landing page may promise a tailored consultation while the booking system offers only a generic group demonstration. A confirmation email may suggest completion while staff still need another form. These are specific inconsistencies, not a generic “awareness problem.”
Choose one boundary to repair rather than redesigning the entire journey at once. Agree which team owns the explanation, which owns delivery and who resolves exceptions. If neither team can fulfill the promise, change the promise before increasing the traffic.
Test continuity with a complete task
Run the repaired sequence from the customer’s starting point. Check whether they can identify the next action, what is already complete and whom to contact when something fails. Include a realistic exception, such as rescheduling or missing information, rather than testing only the smoothest path.
Report time, repeated effort and unresolved questions separately from satisfaction. A fast journey can still be wrong; a necessary longer step can still be clear. Use the findings to assign the next repair and document what remains uncertain. Keep the map current when processes change, rather than treating the poster as the deliverable.
Make the reasoning concrete.
A fictional equipment supplier advertises a site-specific consultation. After booking, the prospect receives a generic webinar link and must explain the site requirements again by email.
Diagnosis
The problem is a broken handoff between the advertising promise, booking category and sales intake. More reminders would reinforce the wrong expectation.
Create a distinct consultation booking route with a minimal authorized site brief and a clear confirmation. Test one complete rescheduling flow before sending more campaign traffic.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Episode
Whose task are you reconstructing, and when did it happen?
Boundary
Where does responsibility move to another team or system?
Carry-forward
What minimum information or expectation must survive?
Mismatch
Which next step contradicts the earlier promise?
Repair owner
Who changes the promise, delivery and exception handling?
Watch for the wrong conclusion.
- Drawing the map from internal departments rather than customer actions.
- Treating every repeated check as unnecessary.
- Fixing a confirmation message while leaving the delivery mismatch intact.
Your next action
Trace one recent customer task across two teams. Write down the first promise that the next step cannot reliably fulfill.
Sources & scope
The teaching, hypothetical exercises and recommended workflows are original editorial analysis. Linked sources support only the scoped facts identified beside them; they do not validate predicted results or endorse this framework.
- GOV.UK Service Manual: Researching user experiences →Primary public-service research guidance · Supports: Researching what people did, thought and felt over time to understand their experience; the marketing handoff audit is an original application.