BC-0057 · CORE GUIDE
Editorial review 2026-09-26
How to Improve a Build Game Tutorial
Improve a tutorial by connecting a short instruction to an immediate action and visible result. Observe what a new player tries without coaching, then fix the point of confusion before adding more explanatory text.
Objective
Teach the opening interaction through timely instructions and observable feedback.
Before you start
- Choose the immediate action the tutorial should teach.
- Make sure that action and its feedback can actually be inspected.
- Find someone unfamiliar with the intended sequence when possible.
Steps
- Remove instructions that are not needed for the opening decision.
- Connect the remaining instruction to an available object or control.
- Observe an uncoached opening attempt.
- Record the exact point where interpretation diverges from the intended action.
- Revise the cue, layout or feedback responsible for that gap.
- Repeat the opening and an early-failure recovery path.
Verification
- The tester can identify an immediate goal without narration.
- The relevant action is possible while its instruction is shown.
- Feedback explains successful progress to the next step.
- Obsolete instructions do not contradict the current state.
- Early failure leads to a useful recoverable instruction.
Limitations
- A small informal test does not measure platform retention or every player's comprehension.
- Familiar creators cannot fully substitute for fresh-player observation.
- The sequence is proposed guidance, not a claim that these tutorial features have been generated successfully.
Working notes
Choose what the player must understand to begin. They usually need a near-term goal, a usable control and feedback showing that the action mattered. Future systems, backstory and advanced strategies can wait until the player has a reason to care about them. An opening panel that explains everything can make the essential action harder to find.
Place the instruction near the action it explains. A message about delivering a parcel should coincide with a visible parcel and an understandable destination. If the player must remember the message through a long unrelated passage, the layout may be working against the explanation.
Observe without filling the gaps yourself. Ask the tester to begin, then record where they hesitate, what they select and what they think happened. If you point at the correct object, the resulting success no longer tells you whether the interface communicated the action. Keep coached and uncoached observations separate. A repeat with the same person is also a familiar-player retest, even without coaching; use a new uncoached tester for another first-use observation when possible.
Make recovery part of onboarding. A missed action or early failure should leave the player with a useful next step. Check whether instructions reappear when needed, disappear when obsolete and avoid repeating over active controls. A tutorial that only works on a perfect opening run can abandon the players who most need it.
Examples
- Opening sequence: show a nearby parcel and the instruction 'Carry the parcel to the marked depot.' After pickup, visibly show carrying state and emphasize the depot. After delivery, explain the next implemented choice rather than presenting an unrelated menu.
- Refinement brief: 'Replace the opening lore panel with a brief delivery objective beside the first parcel. Update the instruction after pickup and clear it after completion. Keep movement and delivery rules unchanged, and show a useful retry instruction after failure.'
- Observation sheet: first action attempted—record; misunderstood object—record; instruction noticed—record; explanation supplied by tester—record. If the tester requires verbal help, write down the help rather than classifying the attempt as independently understood.