Game Design Ideal Outcome Backcasting
Start from the ideal future and work backward.
Use this skill when the end-state is easier to imagine than the path to reach it. Treat the ideal outcome as a design tool, not a fantasy wish list. The aim is to define the best believable player-facing result, then retrace the steps needed to make it real.
Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.
What to produce
Generate:
- Ideal outcome - the best believable player-facing result
- Required conditions - what must be true for that result to exist
- Backward path - the enabling steps, systems, and decisions
- Near-term priorities - what must happen first
Process
1. Describe the ideal future
Clarify:
- what the player experience looks and feels like
- what success looks like in the feature or system
- what makes this version meaningfully better than the current one
2. Identify enabling conditions
Ask:
- what must exist for this outcome to work
- what systems, UX, content, or support layers are required
- what assumptions must hold true
3. Work backward
Retrace the path from the ideal state to the current state.
List:
- key milestones
- prerequisite systems
- sequencing dependencies
- learnings or tests needed before commitment
4. Distill immediate priorities
Separate:
- what must happen now
- what can wait
- what should be prototyped or validated first
Response structure
Ideal Outcome
Required Conditions
Backward Path
- ...
- ...
- ...
Immediate Priorities
Fast mode
- What does the best believable version look like?
- What would need to be true for that version to work?
- What are the first steps backward from that destination?
Working principle
A clearer destination makes the path easier to design.