Map the experience people actually have
A customer’s experience starts before the service itself. It may begin with a search result, a phone call or an appointment message, then continue through the visit, payment and the next interaction. In Experience Engineering, Vance Morris asks teams to put those moments on one journey map before deciding what to improve.
Start with a familiar service and follow it from the customer’s perspective. Record each interaction, the question it should answer and the person responsible for it. Include the quiet gaps: waiting for a reply, finding the entrance or wondering whether a request was received. Those moments can shape the experience as much as the main event.
The map gives improvement work a sequence. Choose a touchpoint where a modest change could remove friction or make someone feel better prepared. Assign an owner and a review date so the idea becomes part of the service rather than a one-time flourish.
In the recording · 03:00 ↗Give an ordinary touchpoint a useful purpose
Vance’s virtual-coffee example connects a physical item to a shared activity. The cup and coffee arrive with instructions that explain why they were sent and how to use them at the meeting. The detail matters because the object helps someone participate.
Apply that question to a welcome message, event reminder or resource packet. What can the recipient do with it? A clear arrival instruction may be more valuable than another branded item. If the material accompanies an event, connect it to something that will actually happen there.
A physical gesture also brings practical work: timing, delivery, recipient preferences and cost. Compare it with a simpler option before committing to a repeatable pattern. The useful part of the example is the connection between the touchpoint and the experience it supports.
In the recording · 06:07 ↗Make the personal detail maintainable
Dependable service needs a system behind it. Vance describes starting with handwritten thank-you notes and later arranging help when the weekly volume grew. The gesture remained recognizable while the delivery process changed.
Choose the moment that should trigger a thank-you, the information needed to make it specific and the person who checks that it happened. Work out how staff handle an incomplete record or a service problem that remains unresolved. A cheerful follow-up sent too early can undermine the care it was meant to show.
Document the routine without scripting every human response. Give staff a clear purpose, a workable handoff and room to address the actual situation. Review the effort as volume changes, including whether the team can sustain the quality of attention it has promised.
In the recording · 12:05 ↗Give retention its own place in the numbers
The conversation then turns from memorable encounters to the economics of keeping relationships. Vance contrasts the effort of acquiring a new customer with the work of staying useful to an existing one. His business examples prompt a practical question: how much attention and budget already go to the people who have chosen the service?
Use your own definitions and time periods when answering. Acquisition cost per new customer and retention spending over a year describe different things. Put those measures beside repeat use, service quality and the cost of fulfilling the work before drawing a conclusion.
Select one measure the team can review consistently. A stronger retention effort should have an identifiable owner and a visible purpose. Improving the experience may help a relationship continue, but a story about a delighted customer does not establish what caused a later purchase.
In the recording · 16:33 ↗Give relationship messages and offers clear jobs
Vance separates the work of an entertaining newsletter, a promotional postcard and an email that draws on existing material. The broader design question is whether every contact asks for something or whether some contacts are useful and enjoyable on their own.
Audit a short run of messages from the recipient’s perspective. Mark what each one offers, what it asks and how it connects to the service. Look for repetition, unclear timing and missed opportunities to answer a common question.
Choose a cadence the audience and team can support. Reusing an idea across channels can reduce production work, provided each version fits the channel and respects the recipient’s communication preferences. Keep a record of what people respond to and what staff have difficulty maintaining.
In the recording · 20:01 ↗Keep improving one part of the journey
Bring the map back to a short review meeting. Ask what customers still find confusing, which handoff creates unnecessary work and what staff have learned since the last change. Vance recommends returning to these touchpoints periodically rather than treating the first design as permanent.
Choose one adjustment, name the person responsible and decide what evidence would show whether it helped. A clearer confirmation, a reliable follow-up or a better explanation can become a dependable part of the experience. Repeating that process gives the next improvement somewhere concrete to begin.
In the recording · 04:57 ↗