Introduce one mechanic at a time

What it is

One mechanic at a time is a pacing principle for teaching: each teaching segment introduces a single new interaction concept, lets the player confirm mastery through use, and only then layers on the next. It comes from the scaffolding tradition—complex skills are built from simpler ones, and the learning order must establish components before assembly.

Why it happens

When two or more new mechanics arrive together, the player cannot attribute failure: was the jump mistimed, the grab mistimed, or the combined sequence wrong? Each attempt varies more than one variable, causal signal drowns in noise, and learning degrades into random trial and error. Working memory has a limited capacity for simultaneously maintained new mappings; exceeding it pushes earlier mechanics out, which shows up as "I could do it a moment ago but now I can't." Introducing one at a time makes every failure point to exactly one new variable, maximising the information in each feedback cycle.

Where it stops holding

This principle applies to teaching segments, not to the entire game's release schedule. Experienced players entering a sequel or same-genre game do not need old mechanics retaught in isolation—differences in new combinations suffice. Games whose core appeal is concurrent management (real-time strategy, multitasking simulations) must build the meta-skill of attending to several things early and cannot remain serial forever. "One at a time" refers to interaction concepts, not to preventing a new mechanic from appearing inside a scenario that exercises an older one.

Applying it

• Map all mechanics' dependency relations, order them into a learning sequence with dependencies appearing first, and place each new mechanic after everything it relies on.
• After introducing a mechanic, place at least one small challenge solvable only by it; confirm the player completes it independently before layering the next.
• Verification: end the teaching sequence with a combined challenge mixing the previous two mechanics and measure the pass rate. A pass rate notably lower than the individual challenges means one mechanic has not settled.

Related

• Same group: W6.01.1 Teaching through play beats teaching before play · W6.01.3 Forced tutorials drive away experienced players
• Nearby: W6.02 Progressive mechanic introduction · C2.01 Working memory capacity · Q3.04 Usability testing
• Search terms: scaffolding · incremental complexity · mechanic isolation · difficulty curve