Start on paper before opening a tool
Give teams a small brief: choose one action, one goal, one failure rule, and one restart behavior. Each person predicts where a first-time player may hesitate. This lets the class discuss whether a concept is testable before anyone spends time on visual detail or account setup.
Use a short prototype cycle
Example exercise: “Design a one-screen maze where a player moves a marker to a visible exit. One blocked square forces a route choice. Hitting a wall stops movement; reaching the exit completes the attempt; Restart returns the marker to the start.” Have one participant read the prompt and another describe what they expect. If the school permits a public prototype tool, one student can generate and test a version while others record observed behavior without entering identifying information.
Set boundaries before sharing
Before anyone opens a service, confirm age, device, account, and public-sharing requirements with the institution. Keep student names and personal information out of prompts and titles. If any rule prevents public publication, do not work around it: use a paper mockup or an approved private tool.
For the playtest, ask neutral questions: “What did you think would happen?” and “What happened instead?” Compare the answer with the written rule. A single session can identify wording or feedback to improve, but it does not establish educational effectiveness.
Questions about classroom game prototypes for teens
How can a class review a prototype?
Have one student explain the written rule while another tries it, then compare expectation with the visible outcome. Use the school's approved sharing approach for collecting those observations.
Can younger students use this lesson?
This site is intended for people aged 13 and older. The activity can also be done with paper sketches, but the online product should not be positioned for younger children.