Static diagrams cannot convey movement
Aliases: motion sequence · temporal gesture · animation reference · static instruction limits
What it is
When a motion game teaches a gesture with a single diagram (a stick figure holding the target pose), it conveys only the end state or one frame—never the temporal structure of the movement: where it starts, which intermediate positions it passes through, and at what speed it transitions. A gesture is an event in time, not a shape in space. Teaching movement with a static image is like teaching table tennis with a photograph: the pose can be copied, but rhythm and trajectory are left to guessing.
Why it happens
Movement learning needs two information types working together: structural information (the relative positions of body parts) and timing information (which part reaches where at which moment, in what order). Static diagrams carry only the structural half. What the player gets is "what the endpoint should look like," but the hard part of execution lives in the intermediate process—the arm's swing path, the timing of weight transfer, the sequential engagement of joints. Without a timing reference, players fill the gaps themselves using everyday habits rather than the target gesture's demands, producing an approximation that looks right but moves wrong. The recognition system may accept or reject it, and the player cannot work backwards from the result to find what differed.
Where it stops holding
Static diagrams are not useless. For pose-holding interactions (arms raised and held, single-leg balance), the end state is the entire content and a static image suffices. As a supplement to dynamic demonstration—keyframe positions annotated beside an animation, or a list of common wrong poses for comparison—they strengthen memory but cannot be the only source. Dynamic demonstration has its own limit: video or skeletal animation shows someone else's movement, but learners cannot directly perceive how their own body deviates from it. That requires mirror feedback or real-time comparison—the next card's problem.
Applying it
- Teach every gesture with a dynamic demonstration (skeletal animation or live-action video) on loop, with adjustable speed (normal and slow).
- Place a static keyframe image beside the demonstration as a quick reference marking "start - key midpoint - end" so players can glance and compare mid-attempt.
- Verification: compare first-attempt success rate and average attempt count between a static-only build and a dynamic-demonstration build. If the dynamic version shows no significant gain, the problem may lie in the gesture's difficulty or recognition threshold rather than the presentation format.