Experience Flow
Diagram the guest journey — logically, before any hardware is chosen.
What Flow is for
The Flow tab is a separate diagram from Routing: it maps the guest or user journey and the logic behind it, not the physical wiring. It has no ports and no signal types — just steps, connected in the order they happen.
A Flow node can be a:
- Step
- Station
- Trigger
- Decision
- System
- Software
- Output
- Location
A worked example
A simple interactive check-in experience, as a Flow diagram:
- 1Check-in
- 2Assign NFC basket
- 3Station
- 4Scan
- 5Trigger media
- 6Checkout
Each arrow is a logical connection — "this leads to that" — not a cable. The Routing diagram is where you decide what device actually plays the media the Trigger step calls for.
Why keep it separate from Routing
Designing the experience before the hardware means the guest journey survives an equipment substitution. If the projector in Routing gets swapped for an LED wall, the Flow diagram — and the story it tells — doesn't need to change.