Trajectory deals with the big picture of the experience. The completed trajectory is highly detailed and offers a script for design & development. It outlines:
- the sequencing of events & interactions
- outcomes of participants interactions (as derived from nodes)
- a timeline for the experience
- back-end responses and actions
- resources required for interactions (as derived from nodes)
Much of the work in trajectory is taken up with linking & sequencing the nodes, pulling out the individual requirements from each and creating a detailed overview of the experience - it's about collation to start.
Working with Trajectory
The trajectory can be worked through by:
- using concept maps to build a linked map of nodes - based on their relationships
- pulling out tools information from the nodes to generate development requirements
- creating a timeline for the occurrence & dependence of interactions in the experience
- building scenarios of how participants might engage with the experience (walk-throughs)
Working through Nodes
When working through each node to pull out what you will need, act each one out to define what you will need:
- for participants
- for facilitators
- for resources
For example, one node might be that participants have to locate a poster & solve the riddle on it, SMS'ing the answer back in to the system for the next step. To split this up, you might split it up as in the diagram below:
- Blue sections are what the participant sees & does (acting out in stages what they do)
- Red is what the system needs to do in response - including storage of completed tasks
- Green are the contents & physical artefacts required for the node
- Not included below is, if you have facilitators, would they would do/see.
Mapping it out in this fashion can help you to build a clear idea of what needs to be done:
- at a participant level - what will they need to do/see
- at a facilitator level - what will they need to do/see
- at a system level (what it needs to do to respond to the participant & to track their progress through the experience where required)
- at a content level - what artefacts & resources you will need for each node
- at a dependency level - what needs to be done in what order (not only for experience sequencing, but for implementation)