Mapping a journey that takes two years from first contact

4 days ago
3 min read

Updated: 2 days ago

Introduction

Short journeys can be observed. Somebody enquires on Tuesday and buys on Friday, and the whole sequence sits in one email thread. A journey running over two years cannot be watched, spans several people, and is recalled rather than recorded, which makes mapping it a different exercise using different sources.

It is also the case where mapping is most valuable. Long journeys contain the most invisible activity, the most opportunities to disappear, and the largest gap between what the business believes happens and what actually does. The businesses that lose most to a two-year cycle are usually the ones treating it as a six-week one.

1. Mapping a journey that takes two years relies on recall, not observation

The methodological difference.

Nobody watched it happen. The map is assembled from what customers remember and what your records happen to have captured, and both are partial. Accepting the partiality is better than pretending to a precision the sources cannot support.

2. Interview customers who took the longest

The right sample.

Not the quickest wins. The customers who took eighteen months are the ones whose journey you need to understand, and they remember it because it was protracted. Six of these produce a clearer picture than twenty fast ones.

3. Expect several distinct episodes

The structural finding.

Long journeys are not continuous. They consist of bursts of activity separated by months of nothing, and the map should show the episodes rather than a smooth line. Drawing it as a continuous progression hides where the opportunity actually sat.

4. Find out what triggered each episode

The most useful question.

Something restarted it each time: a budget cycle, a failure, a new person, a deadline. These triggers are what you can plan around, and they are invisible without asking. Knowing the trigger tells you when to be in contact.

5. Expect the people to change

The organisational reality.

Over two years contacts leave, roles change and decision-makers are replaced. A map assuming one buyer throughout describes a situation that rarely persists. Capturing more than one contact is a practical consequence of this.

6. Record what kept you in consideration

The competitive question.

Between episodes, why were you still on the list? Usually one thing: a periodic message, a piece of material, a relationship. Identifying it tells you what to sustain. It is frequently something small that nobody thought mattered.

7. Map the deferrals as a stage

The structural addition.

"Not now" is a state buyers occupy for months and it belongs on the map with its own entry and exit conditions. Treating it as an absence is why these opportunities are forgotten. Give it a status in your records as well.

8. Use cohorts to measure it

The measurement approach.

Enquiries grouped by arrival month and followed forward. Calendar-month conversion is meaningless when the cycle exceeds the reporting period. Check each cohort at six, twelve and twenty-four months.

9. Keep the map for longer than you think

The maintenance point.

A map of a two-year journey needs to remain stable for at least that long to be tested against reality. Rewriting it annually means it is never validated.

Be careful about record-keeping over this period. Contact details, notes and consent all have to survive two years and remain accurate, and retention obligations apply to information held that long — which is worth checking rather than assuming.

Conclusion

Build it from recall and records, because a two-year journey cannot be observed.

Interview the customers who took longest rather than the quickest, expect several distinct episodes separated by months of nothing, establish what triggered each restart, allow for the contacts changing over the period, identify what kept you in consideration between episodes, treat deferral as a stage with entry and exit conditions, measure by cohort rather than by calendar month, and keep the map stable long enough to test it.