Customer-journey stages, told in the past simple
A customer journey is the path from first hearing about a product to using it; teams map it to find where people slow down or give up. Tell it in the past simple, one stage per sentence.
Time phrases show order and speed, and speed is evidence: “within an hour” means in less than an hour, “that afternoon” later the same day.
- referral – “A colleague recommended the software.”
- comparison – “He compared two plans on the website.”
- demonstration (demo) – “He requested a demo.”
- trial – “After the demo, he started a trial.”
- setup – “The welcome email had no setup steps.”
- activation – “Support called within an hour, and he activated the account that afternoon.”
Naming the friction point
A friction point is where the journey slows down or stops. Name it with one exact fact: “Onboarding was confusing” gives the team nothing to fix; “The welcome email gave no setup steps” does.
“Lack” as a verb takes no “of”; “a lack of” is the noun. “Delay … until” shows how long a problem lasted and what ended it.
- “The welcome email lacked setup steps.” / “There was a lack of setup steps.”
- “The missing setup steps delayed activation until Support called.”
- “Without the steps, he couldn’t set up the account on his own.”
Agreeing the next step
Agree the key fact first, then the action. “Should” recommends and takes the base verb (“should add”). “From next week” means starting next week and continuing; “next week” alone means some time during that week.
Maya Which fact should guide our customer-journey map?
Owen The missing setup steps delayed activation until Support called.
Maya What should we do next?
Owen Support should add the setup guide to every welcome email and track activation time from next week.
Evidence or expectation? Keep them apart
One customer’s recovery shows the guide helped one person, not that it will speed up activation for everyone. So the team will measure activation time: how long new customers take from starting a trial to activation. Use the past simple for what you saw, and “expect” or “will” for what you hope to see.
For discussion: what else would show that the change works? Fewer setup calls is one option.
- Evidence: “After the call, the customer activated the account that afternoon.”
- Expectation: “We expect new customers to activate their accounts faster.”
- Too strong: “The guide solved our activation problem.” Better: “The guide helped one customer; we will check whether it helps others.”
A five-field journey map and a one-minute talk
A useful map fits on one page. Present its five fields in order in five or six sentences, then invite two questions: “Why does it matter?” and “What happens next?”
- Situation: “A new customer started a trial but couldn’t activate the account.”
- Evidence: “The welcome email had no setup steps. After a support call and a guide, he activated it that afternoon.”
- Decision: “Add the setup guide to every welcome email.”
- Owner and start date: “Support, from next week.”
- Expected result: “Faster activation. We will review activation time after four weeks.”
Common mistakes
These weaken a journey report:
- “The email lacked of setup steps.” No “of” after the verb: “The email lacked setup steps.”
- “He couldn’t setup the account.” The verb is two words: “set up the account”; “setup” is the noun.
- “He has activated the account yesterday.” With a finished time, use the past simple: “He activated the account yesterday.”
- “The guide reduced activation time.” Say this only after you measure it. Before that: “We expect the guide to reduce activation time.”
A 10-minute daily practice routine
Goal: present one customer journey from your own work in one minute.
- 2 minutes: say the six stages aloud with their verbs.
- 3 minutes: tell a real customer journey from your work in the past simple, with two time phrases.
- 2 minutes: name its friction point with “lacked” or “delayed … until”.
- 3 minutes: repeat the conversation above line by line, then answer its two questions for your case.
What comes next
Next, use the same evidence, owner and date with customer complaints, or arrange a supplier meeting around a flight arrival. At B1, decision emails add a status, an owner, a date and a clarifying question.


