What is a Prototype?

A Prototype is a fast, focused experiment. It’s a stripped-down version of a game, feature, or system — built not to impress, but to learn.

A prototype doesn’t ask: “Is this good?”

It asks: “Is this worth building?”

1️⃣ Definition

A prototype is a temporary, simplified implementation of a mechanic, system, or idea — built to test functionality, player experience, or design assumptions before full production.

📍A good prototype is disposable. Its value lies in what it teaches — not whether it ships.

2️⃣ Why Prototyping Matters

Purpose	What It Enables	Example
Validate ideas	Prove what works (or doesn’t)	Baba Is You started as a 7-day prototype
Reduce risk	Catch flaws before investment	Hades prototyped narrative integration in combat
Explore variations	Test multiple versions quickly	Into the Breach map sizes, unit tools
Communicate vision	Show playfeel, not just GDD text	Portal evolved from Narbacular Drop
Fail early	Kill bad ideas fast and safely	A failed stamina system after 1 day is a win

📍Prototype to learn. If you're just building — you're already too late.

3️⃣ Types of Prototypes

Type	Focus	Example
Mechanic Prototype	Single verb or feature	Grapple hook, stealth kill
System Prototype	Loop-level simulation	XP → level → unlock test
Level Prototype	Navigation, pacing, enemy placement	Graybox arena with enemy spawns
Narrative Prototype	Dialogue, emotion timing, branching	Twine or Ink scene tests
UX/UI Prototype	Menus, onboarding, HUD flow	Figma or Unity mockups
Paper Prototype	Physical simulation of logic or systems	Cards, tokens, dice = battle loop test
Visual Prototype	Shaders, motion, style mockups	Stylized VFX test in shader graph

📍Don’t mix too many goals. One prototype = one question.

4️⃣ Prototyping Workflow

Ask a clear question

→ “Is stamina-based combat tense or just slow?”

Strip to essentials

→ Ignore UI, ignore art. Just test feel.

Build fast

→ Placeholder assets, debug tools, hardcoded values = welcome.

Playtest early

→ Solo or internal is fine. Watch how people act, not just what they say.

Decide

→ Keep and polish? Refactor? Or kill and move on?

📍The longer a prototype lives, the more dangerous it becomes. Don’t fall in love with it.

5️⃣ Prototype vs Vertical Slice

Prototype	Vertical Slice
Exploratory	Proof of vision
Fast, dirty, temporary	Polished, permanent
Tests ideas	Tests execution
Fails safely	Must be shippable
Often discarded	Often becomes production base

📍A prototype is a question. A slice is an answer.

✅ Prototype Design Checklist

Does it test only one core thing?

Is it scoped to 1–3 days of work?

Can it be tested immediately, without final art or UI?

Will it produce a clear yes/no/try again result?

Is it safe to throw away?

📍If a prototype can’t fail — it’s not a prototype. It’s just early production.

Summary

Term	Prototype
What it is	A disposable, focused build made to test a mechanic or system
Why it matters	Validates ideas, reduces risk, supports iteration
How it works	Through minimal implementation, testing, and fast feedback
Design goal	Learn quickly. Fail safely. Decide with confidence.

📍A prototype is a design lab. It’s where ideas live — or die — before they cost real time.