Service
Playable Design
Shape one understandable interaction around the accepted creative hypothesis before implementation expands.
Concept illustration · Service stage
Design the promise, action, and outcome together
A playable has little time to teach itself. The opening frame must establish what matters, the first action must be discoverable, and the feedback must show that the action changed something. We map those moments as one short interaction rather than reproducing the whole game loop.
The design handoff
- A frame-by-frame interaction outline covering load, instruction, first input, feedback, progress, outcome, and CTA.
- A state list for normal, pressed, correct, incorrect, win, fail, and end-card behavior where each applies.
- Responsive rules for the supported viewports and orientations named in the brief.
- An asset plan showing what comes from supplied game materials, what needs adaptation, and what is outside scope.
- A variant map that identifies safe controlled changes without pretending every idea is the same master.
A concrete design review
Suppose the accepted hypothesis is that the satisfaction of clearing a jammed board will attract puzzle players. The design review should answer: what does the player see before touching; which object is the obvious first move; how does an invalid move respond; how quickly does the board visibly improve; and what outcome leads naturally to the CTA? ‘Make it more fun’ is not reviewable. ‘Reduce the first board to three decision points and make the legal move readable without a hand cursor’ is.
Review question | Approval evidence | Reason to reopen scope |
|---|---|---|
Can the first action be inferred? | A reviewer can point to the target and expected input | The mechanic needs a tutorial sequence |
Does feedback explain success? | State change is visible and immediate | New animation or asset production is required |
Does the outcome support the CTA? | The transition and destination are named | A second gameplay loop is requested |
What design approval means
Approval locks the interaction direction, required states, asset approach, and reviewable variant dimensions. Small tuning still happens during implementation. A request for a different core action, major new art system, or additional level returns to scoping because it changes the master.
What this stage cannot establish
A clear interaction can improve the quality of the test, but design review cannot prove campaign performance. It also cannot establish whether a network will accept an export that has not yet been packaged and tested in its current tools.
Read the mechanic selection guide or bring an accepted brief to start the interaction plan.