what you'll need to build it, run it

back to experience itself

Here you focus what was discovered in the foundation resources section, and so far detailed for nodes, to define the particular tools that you'll need for the experience.

It may seem a little rude, but consider also the people who will be involved as facilitators & as designer/developers as tools in the creation of your experience.


The origin of the tools you need will determine what you are able to do with them (the level of control you'll have):

Working with Tools

Work through each node, act it out, to define what it is you will need for each interaction. The diagram shows the process of working through a node to pick out what tools are required.

It may seem a complex way of going about it, but it can reveal assumptions that you may not have previously considered that impact how participants engage with the experience.

Things to Consider


Another thing to consider when deciding on resources for the experience, is the level to which the experience system will be automated or monitored.

A fully automated system will require a greater investment in development time leading up to the deployment of the experience. But will run with minimum intervention.

A non-automated system will require greater investment in human resources as you will need people in the 'control room' for the duration of the experience responding to participant actions. However you will have more of a feel for the progress of the experience, and opportunity to be flexible in the response and to intervene when participants become lost.