drive-motivation

Original🇺🇸 English
Translated

Motivation science framework based on Daniel Pink's "Drive". Use when you need to: (1) design features that leverage intrinsic motivation, (2) create progress systems that support mastery, (3) craft purpose-driven messaging and missions, (4) audit if product mechanics undermine autonomy, (5) design team structures and incentives with AMP principles (Autonomy, Mastery, Purpose), (6) understand why gamification fails, (7) replace carrot-and-stick approaches with intrinsic motivation.

2installs
Added on

NPX Install

npx skill4agent add wondelai/skills drive-motivation

Drive Motivation Framework

Framework for designing motivation systems in products, teams, and organizations based on the science of what actually motivates humans. Replaces outdated carrot-and-stick thinking with intrinsic motivation.

Core Principle

The secret to high performance isn't rewards and punishment — it's the deeply human need to direct our own lives, learn and create new things, and do better for ourselves and our world.
The foundation: For any task requiring even rudimentary cognitive effort, external rewards (bonuses, prizes, punishments) either don't work or actively make performance worse. Intrinsic motivation — Autonomy, Mastery, Purpose — drives lasting engagement.

Scoring

Goal: 10/10. When evaluating motivation systems (product features, team incentives, gamification, engagement loops), rate 0-10 based on AMP principles. A 10/10 means the system supports autonomy, enables mastery, and connects to purpose; lower scores indicate reliance on extrinsic rewards or controlling behaviors. Always provide current score and improvements to reach 10/10.

Motivation 1.0, 2.0, and 3.0

VersionCore AssumptionApproachEra
1.0Humans are biological beingsSurvival drives (food, shelter, safety)Pre-industrial
2.0Humans respond to rewards/punishmentsCarrot and stick (bonuses, penalties)Industrial age
3.0Humans seek autonomy, mastery, purposeIntrinsic motivationKnowledge economy
The problem with Motivation 2.0 (carrot and stick):
Most organizations still run on Motivation 2.0, but it's fundamentally broken for modern work.

The Seven Deadly Flaws of Extrinsic Rewards

External rewards ("if-then" rewards: "If you do X, then you get Y"):
FlawMechanismExample
1. Extinguish intrinsic motivationTurns play into workKids who were paid to draw stopped drawing when payments stopped
2. Diminish performanceNarrow focus, reduce creativityCandle problem: reward group performed worse
3. Crush creativityFocus on reward, not explorationArtists creating commissioned work are less creative
4. Crowd out good behaviorFinancial framing replaces moral framingDay care late-pickup fee: lateness increased (became a "service")
5. Encourage cheatingGoal fixation leads to shortcutsWells Fargo fake accounts scandal
6. Become addictiveNeed bigger rewards over timeBonus escalation: last year's bonus = this year's expectation
7. Foster short-term thinkingOptimize for reward periodQuarterly bonuses → quarterly thinking
When extrinsic rewards DO work:
  • Routine, algorithmic tasks (assembly line, data entry)
  • Tasks requiring no creativity or judgment
  • When the task is genuinely boring and no intrinsic motivation exists
When extrinsic rewards DON'T work (and hurt):
  • Creative work
  • Complex problem-solving
  • Any task requiring cognitive effort
  • Long-term engagement
See: references/extrinsic-rewards.md for the science behind reward failures.

The Three Pillars: Autonomy, Mastery, Purpose

1. Autonomy

Definition: The desire to direct our own lives — to have choice over what we do, when we do it, how we do it, and who we do it with.
Autonomy ≠ independence. Autonomy means acting with choice. You can be autonomous while being interdependent with a team.
The Four T's of Autonomy:
DimensionQuestionExample
TaskWhat do I work on?Google's 20% time, Atlassian ShipIt days
TimeWhen do I work?Flexible hours, no mandatory meetings
TechniqueHow do I do it?Choose your own tools, methods, approach
TeamWho do I work with?Self-forming teams, choose collaborators
Product applications:
ContextAutonomy KillerAutonomy Enabler
OnboardingForced linear tutorialChoose your own path, skip steps
CustomizationOne-size-fits-allThemes, layouts, preferences
ContentAlgorithm-only feedUser-controlled feeds, filters
CommunicationForced notificationsNotification preferences, DND
WorkflowRigid processFlexible workflow, custom automations
FeaturesFeature bloat (all visible)Show/hide features, progressive disclosure
Autonomy audit questions:
  • Can users choose WHAT to do in the product?
  • Can users choose WHEN to engage?
  • Can users choose HOW to complete tasks?
  • Can users choose their own path through the experience?
Warning signs of autonomy violation:
  • "You must complete X before Y"
  • Forced tutorials with no skip option
  • Mandatory notifications
  • No customization options
  • Rigid workflows with no flexibility
See: references/autonomy.md for autonomy design patterns.

2. Mastery

Definition: The desire to get better at something that matters — to continually improve and grow.
Mastery is a mindset, not a destination. It's asymptotic — you can approach it but never fully reach it. The joy is in the pursuit.
Three laws of mastery:
Law 1: Mastery is a Mindset
  • Growth mindset (Carol Dweck): Ability is developed, not fixed
  • People with growth mindset seek challenges and learn from failure
  • Fixed mindset people avoid challenges (might reveal inadequacy)
  • Design implication: Frame failures as learning, not judgment
Law 2: Mastery is a Pain
  • Requires effort, deliberate practice, and grit
  • Flow (Csikszentmihalyi): Optimal state between boredom and anxiety
  • Challenge must match skill level — too easy = boring, too hard = anxious
  • Design implication: Calibrate difficulty to user's level
Law 3: Mastery is Asymptotic
  • You can approach mastery but never fully arrive
  • The pursuit itself is the reward
  • Design implication: Always have next level, next challenge
The Flow Channel:
                ANXIETY
               /
              /
    FLOW ←──────────── Optimal challenge zone
              \
               \
                BOREDOM

    Low Skill ──────────────── High Skill
Flow conditions:
  • Clear goals
  • Immediate feedback
  • Challenge/skill balance
  • Sense of control
  • Deep concentration
Product applications:
ContextMastery DesignExample
ProgressVisible skill developmentGitHub contribution graph, Duolingo levels
DifficultyAdaptive challengeGames that adjust to player skill
FeedbackImmediate, clear signalsReal-time writing analysis (Grammarly)
GoalsClear, achievable milestonesLinkedIn profile strength meter
LearningSkill trees, structured pathsCodecademy learning paths
StreaksConsistency trackingDuolingo streaks (careful: can become extrinsic)
Mastery audit questions:
  • Can users see their progress over time?
  • Does the product adapt to skill level?
  • Is there immediate, meaningful feedback?
  • Are there clear next steps for improvement?
  • Does the challenge increase as skill increases?
Warning signs of mastery violation:
  • No way to see improvement
  • Same difficulty regardless of skill
  • Delayed or absent feedback
  • No clear path forward
  • Punishing failures instead of teaching
See: references/mastery.md for mastery design patterns and flow state principles.

3. Purpose

Definition: The yearning to do what we do in the service of something larger than ourselves.
Purpose is the context for autonomy and mastery. Without purpose, autonomy is directionless and mastery is hollow.
Three expressions of purpose:
ExpressionHow It ManifestsExample
GoalsPurpose-driven objectivesTOMS: "With every product you purchase, TOMS will help a person in need"
WordsLanguage of purpose, not profit"Associates" not "employees", "community" not "users"
PoliciesActions that demonstrate purposePatagonia: "Don't Buy This Jacket" campaign
Product applications:
ContextPurpose DesignExample
MissionClear, inspiring why"Organize the world's information" (Google)
ImpactShow user's contributionWikipedia edit counter, Kiva lending impact
CommunityConnect to something biggerOpen source contribution, community goals
TransparencyShow how product helpsCharity: Water shows exact well location
ValuesAlign product with beliefsEcosia: "Search the web to plant trees"
Purpose audit questions:
  • Does the user understand WHY this product/feature exists?
  • Can users see their impact on something bigger?
  • Does the product connect to values the user cares about?
  • Is there a mission beyond profit?
Purpose in product design:
  • Show aggregate impact ("Together, our users have saved 1M hours")
  • Connect individual actions to collective outcomes
  • Frame features in terms of why, not just what
  • Celebrate meaningful milestones, not vanity metrics
See: references/purpose.md for purpose-driven design patterns.

AMP Applied: Product Design

Gamification Done Right vs. Wrong

Wrong gamification (extrinsic, Motivation 2.0):
  • Points for every action (becomes meaningless)
  • Badges for trivial achievements
  • Leaderboards that discourage (I'll never catch up)
  • Rewards that replace intrinsic motivation
Right gamification (intrinsic, Motivation 3.0):
PrincipleBad (Extrinsic)Good (Intrinsic)
AutonomyForced challenges, mandatory participationChoose challenges, opt-in
MasteryPoints for everythingSkill-based progression, meaningful milestones
PurposePointless competitionContribute to community, personal growth
Example: Duolingo
  • Autonomy: Choose language, pace, topics
  • Mastery: Adaptive difficulty, progress tracking, skill levels
  • Purpose: "Learn a language to connect with people"
  • Caution: Streaks can shift from mastery (intrinsic) to loss aversion (extrinsic)

Team Motivation

How to apply AMP to team management:
PrincipleManager ActionExample
AutonomyGive control over task, time, technique, team"Here's the goal. How you get there is up to you."
MasteryProvide challenge, feedback, growthStretch assignments, mentorship, skill development budget
PurposeConnect work to mission"Here's why this matters for our customers"
"If-then" vs. "Now that" rewards:
  • Bad: "If you hit target, you get bonus" (if-then, creates pressure)
  • Better: "You hit target! Here's a bonus." (now-that, unexpected recognition)
  • Best: "Let's talk about what you want to work on next." (intrinsic)

Compensation and Incentives

Pink's recommendations:
  1. Pay people enough to take money off the table
  2. Then focus on autonomy, mastery, purpose
  3. Use "now-that" rewards (unexpected), not "if-then" rewards (contingent)
The baseline:
  • Fair compensation eliminates distraction
  • Above-market pay signals respect
  • But beyond "enough," more money doesn't increase motivation
  • Once baseline is met, AMP drives engagement
See: references/applications.md for product and team applications.

Type I vs. Type X Behavior

Type X (Extrinsic)Type I (Intrinsic)
Fueled by external rewardsFueled by autonomy, mastery, purpose
Concerned with external recognitionConcerned with inherent satisfaction
Short-term focusedLong-term focused
Sees effort as burdenSees effort as path to mastery
Fixed mindset tendenciesGrowth mindset tendencies
Goal: Design products and teams that cultivate Type I behavior.
Type I behavior:
  • Is made, not born (anyone can develop it)
  • Doesn't disdain money or recognition
  • Is a renewable resource (doesn't deplete)
  • Promotes greater physical and mental well-being

Common Mistakes

MistakeWhy It FailsFix
Points for everythingCrowds out intrinsic motivationReserve rewards for meaningful milestones
Mandatory participationKills autonomyMake engagement opt-in
Same challenge for everyoneNo flow state (bored or anxious)Adaptive difficulty matching
No visible progressCan't see masteryProgress indicators, skill tracking
Missing "why"Actions feel meaninglessConnect every feature to purpose
If-then bonusesCreates short-term thinkingPay fairly, focus on AMP

Quick Diagnostic

Audit any motivation system:
QuestionIf NoAction
Can users choose what/when/how?Autonomy violationAdd choices, flexibility, customization
Can users see their progress?No mastery signalAdd progress tracking, skill levels
Is the challenge matched to skill?Boredom or anxietyImplement adaptive difficulty
Is there immediate feedback?Can't improveAdd real-time response to actions
Does the user know WHY this matters?No purposeConnect to mission, show impact
Are we using "if-then" rewards?Extrinsic motivationSwitch to "now-that" or intrinsic design

Reference Files

  • extrinsic-rewards.md: The seven flaws, when rewards work and don't
  • autonomy.md: Four T's, product and team autonomy design
  • mastery.md: Flow state, growth mindset, deliberate practice
  • purpose.md: Purpose-driven design, mission alignment
  • applications.md: Product gamification, team management, compensation
  • type-i.md: Type I vs. Type X, cultivating intrinsic motivation
  • case-studies.md: Atlassian, 3M, Duolingo, ROWE, Wikipedia

Further Reading

This skill is based on Daniel Pink's research on motivation science. For the complete framework:

About the Author

Daniel H. Pink is the author of seven books including four New York Times bestsellers. Drive has been translated into over 40 languages and fundamentally changed how organizations think about motivation. Pink's TED Talk on the science of motivation is one of the most-viewed of all time (45M+ views). He has advised companies, governments, and nonprofits worldwide on motivation, creativity, and human performance. Pink was previously a speechwriter for Vice President Al Gore and has written for The New York Times, Harvard Business Review, and Wired.