Technology, fintech and B2B software
Turning a technical programme into an attendee journey
Your programme has many tracks, levels and formats, and a delegate has to decide in minutes which sessions are for them.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Define two to four attendee paths from what people want to leave with, label each session by level and prerequisite, and show the paths in the programme and the app. A delegate should be able to pick a path before arrival and follow it without reading every abstract.
Technical accuracy of session content stays with the speakers and the programme committee. The organiser makes the programme readable.
Start from attendee outcomes
List the kinds of people who attend, such as engineers, architects, team leads and buyers, and write what each should leave with. Different people use the same session for different reasons.
A path is a suggested set of sessions that fits one outcome. It is a guide, not a restriction.
Label every session the same way
| Label | Meaning | Example wording |
|---|---|---|
| Level | Introductory, intermediate or advanced. | Intermediate: assumes you have used the product. |
| Prerequisite | What the delegate should know or bring. | Bring a laptop with the tools installed. |
| Format | Talk, workshop, panel, lab or demonstration. | Hands-on lab, limited seats. |
| Path tag | Which path the session belongs to. | Path B: platform team. |
Design tracks that do not trap people
- Avoid putting two sessions for the same path in the same slot.
- Mark sessions that repeat so people who miss one have a second chance.
- Place limited-seat workshops in rooms that match registration, and decide how seats are claimed.
- Leave transition time and a clear route between rooms that are far apart.
Sequence for the organiser
- Collect session abstracts and ask each speaker for level, prerequisites and format.
- Agree the paths with the programme committee and write one line for each.
- Build the grid with path tags and check for clashes within each path.
- Show the paths in the programme page, the app and the printed guide in the same words.
- Test the journey with a few real delegates and revise the labels.
Worked example · Fictional example
A fictional platform engineering conference
Fictional organisation and figures, for illustration only.
A fictional developer association runs a two-day conference with four tracks and 36 sessions. The committee defines three paths: Getting started, Platform team and Security and compliance.
The first draft puts two Platform team sessions in the same slot. Moving one to the next slot adds a repeat on day two. Each session gets a level and prerequisite line, and a test with five volunteers shows that the word advanced meant different things to different people, so the committee adds a sentence explaining each level.
Use this yourself
Attendee journey planning table
Copy this table, one row per path, and check each row against the programme grid.
| Path name | Who it is for | Outcome | Sessions in order | Prerequisites | Clash check done |
|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- The programme has one or two tracks and a clear audience.
- Speakers already supply level and prerequisite information.
- The committee can test the paths with a few delegates.
Outside planning help earns its fee when
- Many tracks, mixed audiences and limited-seat workshops.
- Speaker content arrives late and in different formats.
- The programme must read the same in the website, app and printed guide.
Need the programme made easier to follow?
A conference project lead can collect session information from speakers, build the path and label scheme with your committee, check clashes across tracks and keep the programme consistent across website, app and print. Technical content and speaker accuracy stay with the speakers and the committee. Send your track list and the audiences you want to guide.
Questions organisers ask
How many paths are enough?
Two to four is usually easy to explain. More paths tend to confuse rather than help.
Should paths be shown before registration?
Yes if you want delegates to choose workshops or sessions with limited seats. Decide with the committee.
Do we need level labels on every session?
Labels help most where the audience is mixed. Agree wording and use it consistently.
How do we handle late speaker changes?
Keep one owner for programme changes and update the website, app and print from the same source.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.