Why this masterclass exists
What you actually do during the program.
Five weeks of architecture work for programme leads designing a 4-12 session track. We sequence the sessions, design connector activities, and stress-test the overall arc.
All masterclasses / attendee journeys
Interactive Track Architecture
Design a multi-session track where each session feeds the next, instead of stacking unrelated talks.
attendee journeys conference 200-800 hybrid pre-event
Inclusions
- Track architecture canvas (premise, arc, sessions, connectors)
- Connector activity library: 11 transition formats
- Stress-test exercise: simulate an attendee who joins midway
- Critique of two real track designs from anonymised past cohorts
What you leave with
- A track architecture canvas signed off by you and your co-programmers
- A defensible argument for the track's arc to leadership and speakers
Common questions
It works from 4 sessions upward. Below that, the connector logic is overkill.
No. We assume you have a speaker shortlist or a process for it.
The class is about the architecture, not session production. For session-level production, see Session Flow Choreography.
From cohort members
"The stress-test exercise broke my track plan in week two and saved me from breaking it on stage in month two."
"I came in skeptical that "track architecture" was a real discipline. Left convinced."