FAQ / Better questions, clearer briefs
Questions at the gate
Practical answers for teams translating game logic into public physical experiences.
What makes an attraction a physical game?
Visitors act within understandable rules, and the environment responds in ways connected to those actions. Technology alone does not make a space a game. A mechanical puzzle or coordinated physical task can be more game-like than a room full of screens. Start with the role, action and consequence.
Does every gaming attraction need a score?
No. A shared transformation, discovery or collective decision can provide a satisfying outcome without ranking participants. Choose scoring only when it reinforces the intended experience and visitors understand what the score represents. Competition can undermine a premise built around cooperation.
Should a concept begin with technology?
Begin with the player role and intended experience. Select technology when it serves a clear interaction and can be operated and maintained responsibly. A promising device is still only one component of a visitor journey that includes explanation, movement, feedback and recovery.
When should operations join the design process?
At the premise stage. Briefing, staffing, reset, maintenance and recovery assumptions can reshape the concept before major commitments. Operators should help define what the attraction promises, not simply inherit a finished scenic design.
How can a team estimate throughput?
Map the full operating cycle and measure variation. A simple batch-capacity model is only a starting estimate, not safe occupancy or guaranteed performance. Include admission, assistance, exit and reset, and examine bottlenecks rather than assuming every cycle matches the fastest rehearsal. Read the operations guide for the distinction.
What does equivalent participation mean?
Different ways of participating should preserve meaningful agency. An alternative route should not automatically reduce someone to observing other players. Involve disabled participants and access specialists early, and provide clear information before arrival. No single design feature guarantees an accessible experience.
What should the first prototype test?
Test the highest-risk unresolved assumption with the smallest credible setup. This may be role comprehension, control discovery or feedback visibility. Match prototype fidelity to the question, record its limits and avoid using a polished appearance as evidence that the underlying system works.
Are the concept examples completed commissions?
No. They are explicitly editorial scenarios used to explain design decisions, not a portfolio of delivered installations or client work. References to real places, organisations, books or standards provide research context and do not imply endorsement or affiliation.
Does the journey tool submit or save my draft?
No. Drafts stay in the current page and are not submitted or saved by the website. Copy places text on your clipboard and Download creates a local text file. Reloading the page resets the fields. The contact message tool works locally too; you decide whether to send its output separately.
Can these guides validate an attraction for opening?
No. Project-specific engineering, risk assessment, accessibility review, legal compliance, inspections and operating approval require competent professionals and relevant authorities. The guides and tools support early design conversations; they are not certification, professional advice or permission to operate.
A question worth testing?
Turn it into a player-journey outline before turning it into a production commitment.