Introduction: Does Your Organisation Know What Happens Between “They Saw Us” and “They Came Back”?

A charity may know how many donors it has, the total amount raised, the number of campaigns launched, and perhaps even its repeat donation rate.

Yet a deeper question may remain unanswered:

What happens to a donor from the moment they first hear about the organisation until they become a sustained supporter?

A person may discover the organisation through a social media post, visit its website, browse one of its projects, hesitate, and then leave.

A few days later, a friend may send them another campaign from the same organisation. They return, search for more information, read a previous report, and eventually make their first contribution.

Afterwards, they wait for confirmation and acknowledgement, then want to know what happened to the project, and may return months later to support another cause.

The opposite may also happen: they donate once and never return.

Each of these moments forms part of the Donor Journey.

But simply knowing these stages does not mean the organisation has a Donor Journey Map.

A journey map seeks to understand, at every stage:

What is the donor trying to achieve? What are they doing? What are they thinking? What are they feeling? Where are they interacting with us? What is blocking them? What is the organisation doing in response? Who is responsible? And how do we know whether the experience is working?

This is where the journey moves from a sequence of events into a management tool for improving the donor experience.

The goal is not merely to move from asking:

“How much did they donate?”

to:

“What was their experience with us?”

but also to:

“Where is the relationship breaking down, why is it happening, and what should we change?”

---

1. The Donor Journey Is Not the Same as the Donor Journey Map

This distinction is fundamental.

Donor Journey

The Donor Journey is the pathway or set of stages a person moves through in their relationship with the organisation.

For example:

Awareness → Interest → Exploration → Decision → Donation → Post-Donation → Repeat Giving → Deeper Engagement

That is the journey.

By contrast:

Donor Journey Map

The Donor Journey Map is the tool used to analyse that journey.

It does not stop at asking:

What stage are they in?

It adds other layers:

Stage → Donor Goal → Action → Thought → Emotion → Touchpoint → Friction/Opportunity → Organisational Response → Owner/System → KPI

In other words:

Stage → Donor Goal → Behaviour → Thought → Emotion → Touchpoint → Barrier/Opportunity → Organisational Response → Owner/System → Indicator

Example

Saying:

“The donor entered the donation page.”

describes part of the Donor Journey.

The journey map goes further:

Goal: I want to know whether my contribution is going to a credible project.
Action: Reviews the page before completing the donation.
Thought: Can I trust this organisation?
Emotion: Hesitation.
Touchpoint: Project page / donation page.
Friction: The use of funds is not sufficiently clear.
Response: Provide a concise explanation of the project and how donations will be used.
Owner: Fundraising / technology / content team, depending on the organisational structure.
KPI: Progression from the project page to starting the donation process.

That is the difference between drawing the pathway and understanding the experience.

---

2. The Donor Journey Is Not Linear

For teaching purposes, it can be useful to represent the journey as:

Awareness → Interest → Exploration → Donation → Post-Donation → Repeat Giving

But people do not always move in this order.

One donor’s journey may look like:

Instagram → Website → Exit → Recommendation from a Friend → Search → Website → Donation

Another may arrive through:

Volunteer → Event → Relationship → Donation

A previous donor may see an emergency campaign and move directly to donating without passing through all the earlier stages.

A donor may also leave and return a year later.

Therefore:

A journey map is not a mandatory path that donors must be pushed through. It is a model that helps the organisation understand possible pathways and the transitions between them.

A donor may:

• Skip some stages.
• Return to an earlier stage.
• Move between different channels.
• Pause temporarily.
• Exit the journey.
• Re-enter it later.

This matters greatly when interpreting donor data.

---

3. Start With the Donor Goal, Not With What the Organisation Wants

One of the most common mistakes is to begin the journey map by asking:

What do we want from the donor?

A donation?
A monthly commitment?
A second gift?

Journey Mapping begins with a different question:

What is the donor trying to achieve at this moment?

When they see the campaign, their goal may be:

I want to understand the cause.

When they visit the organisation’s website:

I want to know who is behind this campaign.

When they open the project page:

I want to make sure the proposed solution makes sense.

When they reach the payment stage:

I want to complete my contribution safely and easily.

After donating:

I want to know that the transaction was completed and what happens next.

Later:

I want to know whether my contribution made a difference.

This distinction is fundamental.

The question:

“How do we make them donate?”

centres the organisation’s objective.

Whereas:

“What are they trying to achieve right now?”

centres the person’s experience.

A good journey map seeks to align the two without compromising donor autonomy or interest.

---

4. Do Not Build Personas From Imagination — Start With Evidence-Based Segments

Not all donors are the same.

But that does not mean the organisation should invent detailed fictional profiles that are not supported by evidence.

A better starting point is what the organisation actually knows.

For example:

• First-Time Donors.
• Repeat Donors.
• Recurring Donors.
• Lapsed Donors.
• Referral Donors.
• Event-Acquired Donors.
• Major Donors.
• Institutional Donors.
• Seasonal Donors.
• Supporters who first engaged as volunteers.

The organisation can then use:

• CRM data.
• Interviews.
• Surveys.
• Engagement history.
• Giving behaviour.
• Acquisition channels.

to understand the real differences between these groups.

Build the segment from evidence, not imagination.

Do not attempt to place all donor segments into one journey map.

Begin with one clearly defined journey, such as:

The journey of a new individual donor from first awareness through to the post-donation stage.

Then build additional maps as needed.

---

5. Current-State Journey — What Is Actually Happening Now?

Before designing an ideal journey, map reality.

This is the:

Current-State Journey

In other words:

What is the donor actually experiencing today?

You may discover that the current journey looks like this:

Advertisement

↓

Project Page

↓

Donation

↓

Automated Receipt

↓

Three Months of Silence

↓

Another Donation Request

The organisation may be so accustomed to this process that it no longer sees anything wrong with it.

But once the same process is viewed from the donor’s perspective, the gap becomes clear.

Journey Mapping should therefore not begin with:

What journey do we want?

It should begin with:

What journey already exists?

And that requires evidence rather than assumptions.

---

6. What Layers Should the Journey Map Include?

A standard framework can be used.

1. Stage

Where is the donor in the relationship?

2. Donor Goal

What are they trying to achieve at this moment?

3. Action

What are they doing?

4. Thought

What question is going through their mind?

5. Emotion

Do they feel curiosity, empathy, trust, hesitation, anxiety, or satisfaction?

6. Touchpoint

Where is the interaction happening?

Website?
WhatsApp?
Email?
Event?
Payment page?

7. Friction / Opportunity

What is getting in the way? What opportunity exists to improve the experience?

8. Organisational Response

What should the organisation do?

9. Owner / System

Who is responsible? Where is the process or data managed?

10. KPI

How do we know that this stage is working?

These layers make the map actionable.

---

7. Touchpoint, Moment of Truth, and Pain Point Are Not the Same Thing

It is important to distinguish between three different concepts.

Touchpoint

A Touchpoint is any moment in which the donor interacts with the organisation.

For example:

• Advertisement.
• Website.
• WhatsApp.
• Email.
• Phone call.
• Donation page.
• Impact report.
• Event.
• Donor support.

Moment of Truth

Not every Touchpoint is a Moment of Truth.

A Moment of Truth is a point whose influence is disproportionately important for trust, decision-making, or continuation of the relationship.

Examples include:

• The first visit to the website.
• The payment moment.
• The first message after donating.
• The first problem or complaint.
• The first project update.
• The first request for another donation.

This distinction matters because an organisation cannot improve everything at once.

Ask:

Which few moments, if improved, would significantly change the overall experience?

Pain Point

A Pain Point is a moment where the donor experiences:

• Hesitation.
• Complexity.
• Delay.
• Ambiguity.
• Error.
• Unnecessary repetition.
• An unsuitable experience.

But a journey map should not look only for problems.

It should also identify:

Improvement / Delight Opportunities

These are opportunities to make the experience more valuable.

For example, after a donation there may be nothing technically wrong with sending:

“Thank you for your donation.”

But there is an opportunity to improve it:

Confirmation + Appreciation + What Happens Next + When to Expect the Next Update

Therefore:

Journey Mapping is not only about finding what is broken. It is also about identifying what could become better.

---

8. Frontstage and Backstage — What the Donor Sees and What They Do Not See

There is another important distinction.

Frontstage

These are the elements visible to the donor:

• Advertisement.
• Website.
• Project page.
• Donation form.
• Payment process.
• Thank-you message.
• Email.
• Impact report.
• Donor support.

Behind all of these sits:

Backstage

Such as:

• CRM.
• Payment gateway.
• Financial system.
• Donor database.
• Programme teams.
• MEAL.
• Internal approvals.
• Automations.
• Customer support.
• Content management.

For example, the donor sees:

A confirmation message arriving within seconds.

But behind that experience there may be:

Payment Gateway → Donation Record → CRM → Automation → Email

This reveals an important distinction:

A problem that appears in the Frontstage may have its real cause in the Backstage.

A donor may receive an irrelevant message.

But the problem may not be the wording itself. The CRM may have failed to record which project they supported.

A donation receipt may be delayed because the integration between the payment gateway and the financial system is incomplete.

For this reason, an advanced Donor Journey Map may develop into something similar to a Service Blueprint, connecting donor experience with the internal processes that create it.

---

9. The Donor Funnel Is Not the Donor Journey Map

There is another important difference.

Donor Funnel

The Donor Funnel answers:

Where did we lose people?

For example:

1,000 saw the campaign.

↓

400 visited the project page.

↓

150 reached the donation page.

↓

80 started payment.

↓

50 completed the donation.

The funnel is excellent at showing the volume of movement and drop-off.

But it does not, by itself, explain why those changes happened.

The:

Donor Journey Map

tries to understand:

Why did the movement or drop-off occur?

Possible reasons may include:

• Lack of trust.
• Insufficient information.
• An unsuitable payment method.
• A technical error.
• Too many requested data fields.
• Poor mobile experience.
• Lack of project clarity.
• Or simply the fact that the person chose not to donate.

Therefore:

The funnel tells us where we lost people; the journey map helps us understand why we lost them.

The two tools complement each other. They are not substitutes.

---

10. Data Tells You What Happened — Donors Help You Understand Why

A journey map should not be based on assumptions.

It requires two types of evidence.

Quantitative Data

Such as:

• Reach.
• Engagement.
• Website Visits.
• Conversion Rate.
• Donation Completion Rate.
• Payment Failures.
• Repeat Donation Rate.
• Retention Rate.
• Email Engagement.

These tell us:

What happened?

But we also need:

Qualitative Data

Such as:

• Donor interviews.
• Surveys.
• Complaints.
• Support messages.
• Donor service feedback.
• Reasons donors themselves give for stopping.

These help us understand:

Why did it happen?

This leads to an important principle:

Data tells you what happened; the donor helps you understand why it happened.

---

11. Do Not Measure Only the Final Outcome — Track Journey Events

If the organisation has the appropriate technical infrastructure, it can be useful to track transitions within the donor journey.

For example:

Campaign Viewed

↓

Project Visited

↓

Donation Started

↓

Payment Attempted

↓

Donation Completed

↓

Confirmation Sent

↓

Project Update Opened

↓

Second Donation

The goal is not to collect as much data as possible.

It is:

To collect the data that helps the organisation understand important transitions in the donor journey.

This allows the organisation to determine whether the problem lies before payment, during payment, or after the donation has been completed.

---

12. Post-Donation Is Part of the Journey — Not the End of the Map

One of the most common mistakes is ending the Journey Map at:

Donation Completed

For the donor, however, a new stage begins at that point.

After donating, they may ask:

Was the transaction successful?

Then:

What happens now?

Then:

What happened to the project?

Then:

Did my contribution have value?

And perhaps later:

Do I want to support this organisation again?

The journey should therefore include:

Confirmation → Appreciation → Updates → Impact → Relationship → Possible Repeat Giving

There is no need here to design every detail of the first 30 days after giving; that deserves separate treatment.

The important Journey Mapping principle is:

The map should not end at the moment the organisation receives the money.

---

13. Not Every Successful Journey Ends in Loyalty or a Larger Donation

It is a mistake to assume that the ideal donor always moves through a ladder such as:

Donation → Larger Donation → Partnership

A person may instead become:

• A Recurring Donor.
• A Volunteer.
• An Advocate.
• A Referrer.
• An Event Participant.
• A Major Donor.
• A Community Ambassador.
• A Corporate Connector.

They may also remain a small but regular donor for years, which can be a highly valuable relationship.

A broader final stage is therefore:

Deeper Engagement

rather than assuming the same outcome for everyone.

The question becomes:

What meaningful form of relationship does this person want, and what type of relationship can the organisation build with them?

---

14. Exit, Lapse, and Re-entry Are Also Part of the Journey

Not everyone continues.

A journey may become:

Donation → Communication → Silence → Lapse

But it may not end there.

Months later:

Relevant Campaign → Reactivation → Return

The map should therefore ask:

Exit

Where did the donor leave?

Why

Why did they leave?

Re-entry

What might appropriately bring them back?

This becomes important later when examining:

• Donor Retention.
• Lapsed Donors.
• Reactivation.

However, the organisation should not assume that every donor who leaves must be pursued until they return.

Sometimes leaving is a natural decision that should be respected.

---

15. Future-State Journey — What Experience Do We Want to Build?

Once the Current State is understood, the organisation can move to the:

Future-State Journey

In other words:

What do we want the experience to become?

For example:

Current State

Donation
↓
Receipt
↓
Silence
↓
Another Ask

Future State

Donation
↓
Confirmation and Appreciation
↓
Explanation of What Happens Next
↓
Relevant Update
↓
Outcome or Impact
↓
Non-Financial Engagement
↓
A New Opportunity to Support, When Relevant

This reveals the improvement gap:

Current State → Gap → Future State → Improvement

This is one of the most important purposes of Journey Mapping.

The map does not simply describe reality.

It helps the organisation design a better experience.

---

16. Who Owns the Donor Journey?

The donor journey does not belong to the fundraising team alone.

For example:

Marketing may own acquisition.

Communications may own messaging.

Technology may own the digital experience.

Finance may own the transaction and receipts.

Programmes may own delivery.

MEAL may own evidence and results.

Donor Relations may own the relationship.

But this raises a problem:

If everyone owns one part of the journey, who owns the whole journey?

It can therefore be useful to define a:

Journey Owner

A person or role with an End-to-End view of the donor experience.

This does not mean that they personally execute every part of the journey.

Their role is to ensure that the parts work together.

Each important Touchpoint should also have:

Owner + System + KPI

so that no important stage remains without clear ownership.

---

17. Journey Mapping Must Protect Donor Agency

Mapping the journey does not mean building a machine that pushes people step by step until they donate.

There is a difference between:

Facilitating the decision

and:

Manipulating the decision

The donor must retain:

Donor Agency

meaning their ability to:

• Understand.
• Choose.
• Step back.
• Change preferences.
• Decide how they wish to be contacted.
• Make decisions without misleading pressure.

At every Touchpoint, the organisation should therefore ask:

Does this point help the donor make a better decision, or does it simply increase the likelihood that they will do what the organisation wants?

Simplifying a donation form helps the donor.

Explaining impact helps the donor.

Presenting options clearly helps the donor.

False urgency, hidden choices, or making opt-out difficult do not represent ethical journey improvement.

---

18. Do Not Try to Fix Everything at Once

After mapping the journey, the organisation may identify dozens of problems and opportunities.

Resources, however, are limited.

Improvements therefore need to be prioritised.

A simple model is:

Impact × Frequency × Ease of Improvement

Impact

How much does the issue affect the donor experience?

Frequency

How many people are affected?

Ease of Improvement

How easy or costly is it to fix?

For example:

If 30% of donors fail to complete payment because of a technical issue, that is a high-priority problem.

Changing a minor visual detail that has little effect on behaviour or understanding may be a lower priority.

The journey map should not produce a wish list.

It should produce:

A prioritised and actionable improvement plan.

---

19. Test the Journey — Mystery Donor Test

One of the best ways to understand the journey is to have someone experience it without prior knowledge of the system.

This can be done through a:

Mystery Donor Test

in which a person goes through:

Discover → Explore → Donate → Ask a Question → Receive Follow-up

They then record:

• Where did they understand the process?
• Where were they confused?
• Where did they hesitate?
• Where did they feel trust?
• Where did they encounter a problem?
• What did they expect but fail to find?
• Were the messages consistent?
• What happened after the donation?

An internal staff member who already understands the system may overlook important problems because they already know where information is located and how the process works.

Testing is therefore often more useful when carried out by someone approaching the experience with fresh eyes.

---

20. Review the Journey Periodically and When Significant Changes Occur

A Journey Map is not a document to be drawn once and then stored away.

The journey changes as the following change:

• Technology.
• Donor expectations.
• Communication channels.
• Payment methods.
• CRM systems.
• The website.
• Donor segments.
• Fundraising strategy.

The organisation can therefore combine:

Periodic Review

A regular review schedule appropriate to the organisation.

with:

Trigger-Based Review

A review triggered by a major change, such as:

• Launching a new website.
• Changing the payment gateway.
• Entering a new donor segment.
• Running a major campaign.
• Increased Drop-off.
• Declining Retention.
• Increased complaints.
• Changing the CRM.
• Adding a new communication channel.

The map is a continuous learning tool, not a static document.

---

21. A Complete Practical Donor Journey Map Template

An organisation can begin with the following model:

Element	Key Question
Stage	What stage is the donor currently in?
Donor Goal	What are they trying to achieve?
Action	What are they doing?
Thought	What are they thinking or asking?
Emotion	What are they feeling?
Touchpoint	Where is the interaction happening?
Friction	What is getting in the way?
Opportunity	How could the experience be improved?
Organisational Response	What should the organisation do?
Owner	Who is responsible?
System/Data	Where is the process or data managed?
KPI	How do we measure success?

Then add an improvement layer:

Current State	Gap	Future State	Improvement	Priority
What happens now?	What is the problem?	What do we want instead?	What will we change?	How urgent is it?

Simplified Example

Dimension	Example
Stage	Exploration
Donor Goal	To verify the credibility of the organisation and project
Action	Visits the project page and looks for more information
Thought	Can I trust this organisation?
Emotion	Interest with some hesitation
Touchpoint	Website / Project Page
Friction	Difficulty finding previous results
Opportunity	Make relevant evidence and results easier to access
Organisational Response	Improve the page and connect it to relevant reports and outcomes
Owner	Content / Programmes / Technology, depending on the structure
System/Data	CMS + Analytics
KPI	Progression from project page to starting the donation process

In this form, the Journey Map becomes more than an attractive diagram.

It becomes a tool connecting:

Donor Experience + Operations + Data + Ownership + Improvement

---

22. From Journey Map to Improvement Plan

Once the map is completed, the result should not simply be:

“We now have a Journey Map.”

The question is:

What will we do because of what the map revealed?

If people reach the donation page but do not complete the process:

Review the Transaction Experience.

If the first donation goes well but the relationship disappears afterwards:

Review the Post-Donation Journey.

If complaints repeatedly arise around the same issue:

Investigate the problem in both the Frontstage and Backstage.

If donors read the project page but do not move towards donating:

Review:

Trust + Clarity + Evidence + Relevance

If previous donors are not returning:

Do not immediately begin with a Reactivation campaign.

First understand:

Where did they leave the journey, and why?

---

Conclusion: The Donation Is a Moment; the Journey Is the Relationship

Every advertisement, every page, every phone call, every payment process, every thank-you message, every update, and every impact report adds something to the donor experience.

It may add:

Trust.

Or:

Hesitation.

It may remove:

A barrier.

Or create:

A new one.

For this reason, donor relationship management cannot begin and end with measuring:

“How much did we raise?”

The organisation also needs to understand:

How did people reach us?

What were they trying to achieve at each stage?

What did they experience with us?

Where did they trust us?

Where did they hesitate?

Where did they exit?

Why did some return?

What should we change?

The distinctions are therefore essential:

Donor Journey describes the pathway the donor experiences.

Donor Journey Map helps the organisation understand and analyse that pathway.

Donor Funnel shows where movement or drop-off happened numerically.

Journey Map helps explain why it happened.

Current-State Journey reveals the experience that exists today.

Future-State Journey describes the experience the organisation wants to build.

Frontstage is what the donor sees.

Backstage is what the organisation’s teams and systems do behind the scenes to create that experience.

When these elements are connected, the journey map becomes more than a marketing tool.

It becomes a management tool that connects marketing, technology, finance, programmes, MEAL, and donor relations around one coherent experience.

The objective is not to design a path that forces the donor to move wherever the organisation wants.

It is to:

Understand the path the donor is actually experiencing, remove unnecessary barriers, protect their ability to choose, and design an experience that is clearer, more respectful, and more valuable.

A mature organisation does not only know who donated.

It also understands how they arrived, what they were looking for, what built trust, what happened after the donation, and where the relationship can be improved.

That is when the Donor Journey Map becomes a tool for understanding, managing, and developing the relationship, rather than simply a diagram of the donation process.

Because the donation is a moment, but the journey is the relationship.