How to scope an immersive project without killing the idea

Good scoping protects the moment people came for.

I wrote this because immersive projects often lose their best idea during budgeting. Teams cut many small things, yet somehow keep expensive features nobody needs.

What's the problem?

Virtual reality and augmented reality projects hide cost in unusual places. A simple interaction may need animation, sound, interface design, testing and several fallback states.

Content multiplies the problem. Every new character needs writing, modelling and movement. Every additional scene needs lighting, optimisation and review. Supporting another headset or phone creates another testing path.

Then come the edge cases. These are unusual situations the experience must handle, such as a visitor losing tracking while standing backwards under poor lighting.

Some edge cases deserve serious attention. Safety, comfort, accessibility and recovery from failure should stay in scope. Others describe situations that are possible but unlikely. Supporting all of them can consume the budget before the central experience feels good.

Commissioners often respond by requesting shorter scenes or fewer visual details. That can leave the project technically complete and emotionally flat. [The spreadsheet will be delighted.]

What's the solution?

Start with one experience promise. This is a plain sentence describing what the visitor does and why it feels interesting.

For example: “A festival visitor points their phone at a mural, meets its animated character and makes one choice that changes the ending.”

That sentence becomes the test for every proposed feature. Does the feature help the visitor reach that moment, understand it or enjoy it? If not, it becomes a candidate for removal.

I sort the scope into three layers:

1. The central experience includes the essential action, response and emotional beat.
2. Supporting work helps people enter, understand and complete that experience.
3. Expansion adds extra scenes, social systems, personalisation or repeat visits.

Build the first layer properly. Add enough of the second to prevent confusion. Treat the third as optional until the central experience works with real people.

Imagine the original festival brief includes six murals, three characters, user accounts, a leaderboard, recorded dialogue and several endings. The experience promise needs far less.

We might keep three murals, one strong character and one meaningful choice. Visitors enter through a QR code, so accounts can go. Captions replace costly multilingual voice recording during the first release. A simple final image replaces the leaderboard.

We still test outdoors, in crowds and under bright sunlight. Those conditions are common at festivals. We can stop supporting very old phones, publish clear device requirements and provide a staffed fallback screen.

The idea survives because its action and response remain intact. We cut volume around the experience rather than quality inside it.

This approach also gives producers cleaner estimates. Creators know where detail belongs. Commissioners can see which additions buy a better experience and which merely enlarge it.

What's next?

1. Write your experience promise in one sentence. Include the visitor, their action and the response.
2. Label every feature as central, supporting or expansion. Remove one expansion item before estimating.
3. Prototype the central interaction with rough assets, then watch five people use it without coaching.

Share your experience promise with us, or ask where you should make the first cut.

Virtually yours, Deac

— The worldbuild.io infoBot