Programme architecture
Event audience journey
The programme describes what happens on stage, and nobody has written down what a first-time participant experiences from invitation to the following week.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
An audience journey follows a typical participant through each step: invitation, registration, joining instructions, arrival, orientation, sessions, breaks, departure and follow-up. At each step it records what they need, what they will do and who is responsible.
The journey turns programme decisions into the experience, and it shows where a gap in one team's work lands on the participant.
Choose two or three journeys, not everyone
Pick participant types whose day differs: a first-time member, a speaker, a sponsor representative, or a delegate who arrives from another state. A different journey will show a different gap. Keep the list short enough to finish.
Stages to map
| Stage | What the participant needs | Who is responsible | Pain point to look for |
|---|---|---|---|
| Invitation and registration | Clear date, place, cost and what the day contains | Secretariat | Unclear fee or deadline |
| Joining instructions | How to reach the venue, when to arrive, what to bring | Secretariat / project lead | Instructions arrive too late |
| Arrival and orientation | Where to register, where to go, who to ask | Registration team, venue | No signage, long queue |
| Sessions | Where each is, what is expected of them | Moderators, venue | Room changes without notice |
| Breaks and networking | Refreshments, quiet space, prayer space, people to meet | Venue, hosts | No place to sit, see networking structure |
| Departure | Clear end and what to do next | Moderator | Unclear closing, rush for parking |
| Follow-up | Slides, notes, contact and next date | Secretariat | Nothing arrives, or arrives months later |
How to walk the journey
- Write the participant's goal in one sentence, from the session objective map.
- Walk the stages in order and note what the participant sees, hears and must do.
- Mark each moment as clear, uncertain or a gap.
- Assign each gap to an owner and a date.
- Update the programme or the joining instructions, then check the pace in the fatigue review.
Include the first and last ten minutes
The opening sequence and the close are the points most participants remember. Decide who greets, how people find their seat, and what happens as they leave.
Common mistakes
- Mapping the stage experience only.
- Assuming everyone has attended before.
- Writing the journey from the organiser's side rather than from what the participant sees.
- Finding gaps and leaving them without an owner.
Worked example · Fictional example
Mapping a first-time member's journey
Fictional organisation and figures, for illustration only.
A fictional professional institute with 300 expected delegates maps a first-time member's day. The map shows that joining instructions arrive two days before, that signage for the registration desk is missing at the lift lobby, and that follow-up slides are not promised in any message.
The secretariat moves the instructions to two weeks before, asks the venue about signage, and adds a line in the closing remarks about when materials will be shared.
Use this yourself
Audience journey table
Copy one table per participant type.
| Stage | What they see or do | Need | Owner | Clear / uncertain / gap | Action and date |
|---|---|---|---|---|---|
| Invitation and registration | |||||
| Joining instructions | |||||
| Arrival and orientation | |||||
| Sessions | |||||
| Breaks and networking | |||||
| Departure | |||||
| Follow-up |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Two or three participant types and one venue.
- A small team that can walk through the venue together.
- Joining instructions and follow-up are already planned.
Outside planning help earns its fee when
- Multiple venues, tracks or audiences with different needs.
- Several teams own parts of the journey with no one holding it overall.
- The event has previously produced participant complaints without a clear cause.
Plan the day from the participant's side
If you want someone to hold the participant's journey from invitation to follow-up, an Event Blueprint can document the stages, responsibilities and gaps with owners. A project lead would coordinate the teams and the venue so each handover is covered, while the programme and its messages stay yours.
Questions organisers ask
How many journeys should I map?
Two or three, chosen because the participants' days differ. More than that and the exercise stalls.
Who should walk the journey?
A person who did not plan the event, ideally someone like the participant. Walking the venue helps find signage and queue problems.
Does a journey replace the run-of-show?
No. The journey shows the experience, while a run-of-show lists the cues and tasks behind it. Use both.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.