CEPD · Module 5 — Serious games that rehearse

Mission layouts in Studio

Objective panel, step list, constraints and fail feedback, written as production beats before skinning.

About 18 min

Practice in the lesson player

Sorting, matching, quizzes, and the module gate stay behind a free account so scored answers are not public. The teaching notes below are the same cited curriculum.

What this lesson covers

  1. 01

    Mission beats

    Objective: One sentence from the action map: what success looks like on the job.

    Constraints: Job-real limits: time, missing information, faulty equipment, competing requests.

    Steps: The ordered actions the learner must take, each scored.

    Fail feedback and debrief: What went wrong, why, and a new attempt.

  2. 02

    Write the beats before you skin them

    A warehouse pick mission starts from one sentence: pick the correct aisle, scan the bin, confirm the quantity, stage the pallet. Constraints are job-real: the scanner times out, the bin label is in Arabic and the ticket in English, the quantity on the ticket disagrees with the shelf. Steps are ordered actions with a score each. The art comes after.

  3. 03

    Mission spec

    Field | Example

    Objective | Stage the correct pallet without skipping the scan

    Constraint 1 | Scanner times out after 20 seconds

    Constraint 2 | Ticket quantity 24, shelf shows 20

    Step scoring | Correct aisle (1), scan before pick (2), resolve quantity mismatch by reporting (3), stage (1)

    Fail states | Pick without scan; stage with wrong quantity

    Debrief | Steps matched and missed, with the policy line

    Retry | Same objective, new bin and quantities

  4. 04

    Mission costume or mission ready

    Costume: Use the mission template for the safety module. · Timer added for excitement.

    Ready to build: Objective, constraints and step scoring written and signed. · Timer only where the job is timed, with pause and extend.

  5. 05

    Design the difficulty curve

    A single mission played once is a test, not practice. Plan three to five instances with rising difficulty: first with one constraint and a visible hint, then with two constraints, then with a distractor (a plausible wrong bin), then under time pressure if the job is timed. This is the same idea as task classes in 4C/ID and fading in worked examples: same objective, more of the real job's complexity each time.

  6. 06

    Write the mission spec

    Fill the mission spec table for your sequence, and plan three instances of rising difficulty.