Overview
Player motivation fails when it is reduced to rewards. The designer adds experience points, loot drops, achievement badges, and daily login bonuses to every action. The player performs every action for the reward, not for the action itself. When the rewards stop (or when the player has all of them), the motivation stops too. The player was never engaged with the game — they were engaged with the reward schedule. Remove the rewards and the game is empty.
The Motivation Architecture prompt builds motivation systems with three properties: (1) SDT-based layering — the three basic psychological needs from Self-Determination Theory (competence, autonomy, relatedness) are treated as independent motivation channels that can be satisfied simultaneously, sequentially, or in trade-off configurations, and the architecture specifies which channel each game system serves, (2) motivation conflict resolution — when satisfying one need undermines another (e.g., rigid quest structures satisfy competence but undermine autonomy), the architecture specifies how the conflict is resolved, and (3) intrinsic-to-extrinsic transition management — the architecture tracks when intrinsic motivation (doing something because it is inherently satisfying) is at risk of being replaced by extrinsic motivation (doing something for a reward), and specifies design interventions that prevent the transition.
What you get: - SDT need-channel mapping (which systems serve which needs) - Motivation conflict matrix (need-vs-need with resolution rules) - Intrinsic motivation protection protocol - Extrinsic motivation calibration guide (when rewards help vs. harm) - Player motivation state model (tracking which needs are satisfied/deficient) - Motivation architecture audit checklist
Built for: game designers, systems designers, and live ops teams who need players who play because they want to — not players who play because they are paid to.