Guide · Production / Pre-production
The one-page pre-production check
The page is not a miniature design bible. It is a decision sheet: what are we making, what proves it works, and what could stop us?
The seven boxes
- Audience and intended experience
- One-sentence core interaction
- Minimum playable outcome
- Must-have assets and systems
- Biggest technical or production risk
- First test and who will run it
- What gets cut first if time slips
Make uncertainty visible
If a learner writes ‘multiplayer, inventory and procedural world’ as if they are simple features, ask which has already been proved and which needs a prototype before the plan is trusted.
Revisit it
After the first test, update the page. Pre-production is useful when it changes decisions, not when it becomes a document submitted once and ignored.
Use a generated client brief, complete the seven boxes, then swap plans and challenge the proposed minimum outcome.
Keep moving
Useful next steps.
Choose an engine for the learning job
Compare engines against the task, machines, teaching time and intended progression rather than arguing for one universal winner.
GitHub Skills: Introduction to GitHub
A short official exercise introducing repositories, branches, commits and pull requests.
Pro Git: About Version Control
A free online explanation of local, centralised and distributed version control and the problems each approach addresses.