KEY TAKEAWAYS
Start here.
- A prototype tests uncertainty; a slice demonstrates quality.
- Define content and pipeline dependencies.
- Agree on playable acceptance and handoff.
Choose the milestone's purpose
A prototype tests a mechanic or core loop, often with temporary assets. A vertical slice demonstrates a representative portion of the intended game's quality and production pipeline. Choose the decision the build should support before setting acceptance criteria.
Write a core-loop brief
Describe player actions, feedback, repetition, and content boundaries. 'A playable level' leaves too much undefined.
| Area | What to define |
|---|---|
| Goal | Learning or production question |
| Target | Engine version, platform, input, hardware |
| Core loop | Actions, feedback, progression, completion |
| Content | Scenes, assets, UI, audio, temporary content |
| Dependencies | Tools, services, access, suppliers, decision owners |
| Acceptance | Playable checks, technical criteria, review |
| Handoff | Repository, build steps, licenses, remaining work |
Example: test one interaction loop
A small movement prototype might include a controller, one interaction, temporary prompts, and reset behavior. Final art, networking, progression, and publishing can be excluded to protect the learning goal.
A vertical slice needs a different brief: representative art, audio, feedback, interface states, and pipeline quality. Use examples and review points to define what 'polished' means.
Confirm dependencies and handoff
Name who supplies models, animation, textures, audio, and UI. Confirm formats, licenses, deadlines, and acceptable temporary assets. Production and integration are separate responsibilities. Accounts, multiplayer, and remote data require their own defined behavior and test access.
Document who reviews builds and how acceptance is recorded. A learning prototype can be successful even if it suggests changing the concept. A production slice should also demonstrate the agreed content pipeline and quality expectations.
- Confirm engine, repository, and build setup.
- Name required asset suppliers and owners.
- Agree on hardware and performance checks.
- Mark services as real, mocked, or excluded.
- Review playable builds against specific criteria.
Finish with a decision
Record findings, unknowns, and next-stage changes. Prototype architecture may need replacement for production. Handoff includes source, build instructions, asset licenses, and known issues. Unanimous can scope Unity or web-game work once platforms, content, and responsibilities are confirmed.