Skip to content
drive-motivation logo

Drive Motivation Framework

drive-motivation

Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "team incentives", "autonomy", "mastery", "purpose-driven", "employee engagement", or "reward systems". Also trigger when de...

wondelai/skills4.6Kinstalls2.3Kstars

SKILL.md

Full skill instructions

Drive Motivation Framework

Design motivation systems for products, teams, and organizations using the science of 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. For any task requiring even rudimentary cognitive effort, external rewards either don't work or actively worsen performance. Intrinsic motivation — Autonomy, Mastery, Purpose (AMP) — drives lasting engagement.

Scoring

Goal: 10/​10. Score any motivation system (product features, team incentives, gamification, engagement loops) against the Quick Diagnostic: start at 5, add 1 for each of the first five rows answered "yes," then subtract 2 if the sixth row is also "yes" — an "if-then" reward doing the motivating crowds out the rest. Bands:

  • 9-10 — autonomy, mastery, and purpose all present; no if-then crowding-out.
  • 5-6 — one pillar carries the system; the other two are weak or extrinsic.
  • ≤3 — relies on rewards, mandates, or controlling behaviors; intrinsic motivation absent.

Always state the current score, which diagnostic rows failed, and the specific fixes to reach 10/​10.

Motivation 1.0, 2.0, and 3.0

VersionCore AssumptionApproachEra
1.0Humans are biologicalSurvival drivesPre-industrial
2.0Humans respond to rewards/​punishmentsCarrot and stickIndustrial age
3.0Humans seek autonomy, mastery, purposeIntrinsic motivationKnowledge economy

The Seven Deadly Flaws of Extrinsic Rewards

"If-then" rewards ("If you do X, then you get Y"):

FlawMechanismExample
1. Extinguish intrinsic motivationTurns play into workKids paid to draw stopped drawing when payments stopped
2. Diminish performanceNarrow focus, reduce creativityCandle problem: rewarded group performed worse
3. Crush creativityReward focus replaces explorationCommissioned art rated less creative
4. Crowd out good behaviorFinancial framing replaces moral framingDay-care late fee: lateness increased (became a "service")
5. Encourage cheatingGoal fixation invites shortcutsWells Fargo fake accounts
6. Become addictiveBigger rewards needed over timeLast year's bonus = this year's expectation
7. Foster short-term thinkingOptimize for the reward periodQuarterly bonuses → quarterly thinking

The boundary: extrinsic rewards work only for routine, algorithmic tasks with no intrinsic interest. For creative work, complex problem-solving, or long-term engagement, they backfire.

See references/​extrinsic-rewards.md when a reward or incentive scheme is backfiring — the named studies behind each flaw and a decision rule for when rewards are safe to use.

The Three Pillars: Autonomy, Mastery, Purpose

1. Autonomy

Core concept: The desire to direct our own lives — choice over what, when, how, and with whom. Autonomy ≠ independence: people can act with choice while staying 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 tools, methods, approach
TeamWho do I work with?Self-forming teams

Product applications:

ContextAutonomy KillerAutonomy Enabler
OnboardingForced linear tutorialChoose your path, skip steps
ContentAlgorithm-only feedUser-controlled feeds, filters
WorkflowRigid process, feature bloatCustom automations, show/​hide, progressive disclosure

Autonomy violations: "You must complete X before Y", unskippable tutorials, mandatory notifications, and forced single paths through the experience.

See references/​autonomy.md when designing onboarding, feeds, or workflow controls — full Four T's patterns plus the autonomy audit checklist.

2. Mastery

Core concept: The desire to get better at something that matters. Mastery is a mindset, not a destination — it's asymptotic, and the joy is in the pursuit.

Three laws of mastery:

  • Mastery is a mindset — ability is developed, not fixed (Dweck's growth mindset). Frame failures as learning, not judgment.
  • Mastery is a pain — it demands effort and deliberate practice. Flow (Csikszentmihalyi) lives between boredom and anxiety, so calibrate challenge to skill level.
  • Mastery is asymptotic — users never fully arrive. Always offer a next level, next challenge.

Flow conditions: clear goals, immediate feedback, challenge/​skill balance, sense of control.

Product applications:

ContextMastery DesignExample
ProgressVisible skill developmentGitHub contribution graph, Duolingo levels
DifficultyAdaptive challengeGames that adjust to player skill
FeedbackImmediate, clear signalsGrammarly real-time writing analysis

Mastery violations: flat difficulty that never adapts, and failure that is punished rather than framed as learning.

See references/​mastery.md when designing progress, difficulty, or feedback systems — flow-state calibration, deliberate practice, and the mastery audit checklist.

3. Purpose

Core concept: The yearning to act in service of something larger than ourselves. Purpose is the context for the other two pillars — without it, autonomy is directionless and mastery hollow.

Three expressions of purpose:

ExpressionHow It ManifestsExample
GoalsPurpose-driven objectivesTOMS: every purchase helps a person in need
WordsLanguage of purpose, not profit"Associates" not "employees", "community" not "users"
PoliciesActions that demonstrate purposePatagonia: "Don't Buy This Jacket"

Product applications:

ContextPurpose DesignExample
ImpactShow the user's contributionWikipedia edit counter, Kiva lending impact
CommunityConnect to something biggerOpen source contributions, community goals
ValuesAlign product with beliefsEcosia: "Search the web to plant trees"

Purpose prescriptions: show aggregate impact ("Together, our users have saved 1M hours"), connect individual actions to collective outcomes, and celebrate meaningful milestones over vanity metrics.

See references/​purpose.md when wiring impact, community, or values features — Goals/​Words/​Policies patterns and the purpose audit checklist.

AMP Applied: Product Design

Gamification Done Right vs. Wrong

PrincipleBad (Extrinsic)Good (Intrinsic)
AutonomyForced challenges, mandatory participationOpt-in, chosen challenges
MasteryPoints for everything, trivial badgesSkill-based progression, meaningful milestones
PurposePointless competition, discouraging leaderboardsCommunity contribution, personal growth

Example — Duolingo: autonomy (choose language, pace, topics), mastery (adaptive difficulty, skill levels), purpose ("learn a language to connect with people"). Caution: streaks can shift from intrinsic mastery to extrinsic loss aversion.

Team Motivation

PrincipleManager ActionExample
AutonomyHand over task, time, technique, team"Here's the goal. How you get there is up to you."
MasteryProvide challenge, feedback, growthStretch assignments, mentorship, learning budget
PurposeConnect work to mission"Here's why this matters for our customers"

Compensation and Incentives

Pay people enough to take money off the table — fair, ideally above-market — then focus on AMP; beyond "enough," more money doesn't increase motivation. Prefer "now-that" rewards (unexpected recognition after the fact: "You hit target! Here's a bonus.") over "if-then" rewards ("If you hit target, you get a bonus"), which create pressure and short-term thinking.

See references/​applications.md when applying AMP to a concrete gamification, team-management, or compensation design — worked examples and escalation tables.

Type I vs. Type X Behavior

Type X (Extrinsic)Type I (Intrinsic)
Fueled by external rewardsFueled by autonomy, mastery, purpose
Seeks external recognitionSeeks inherent satisfaction
Short-term focus, fixed mindsetLong-term focus, growth mindset

Design products and teams that cultivate Type I behavior: it's made, not born; it doesn't disdain money or recognition; it's renewable; and it promotes well-being.

See references/​type-i.md when shifting a team or user base from Type X to Type I — the full behavioral contrast and conversion tactics. For real-world AMP programs (Atlassian ShipIt, 3M, ROWE, Duolingo, Wikipedia), see references/​case-studies.md.

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 — boredom or anxietyAdaptive difficulty matching
No visible progressMastery is invisibleProgress indicators, skill tracking
Missing "why"Actions feel meaninglessConnect every feature to purpose
If-then bonusesShort-term thinking, gamingPay fairly; use "now-that" rewards; 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 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 crowding-outSwitch to "now-that" or intrinsic design

Further Reading

Based on Daniel Pink's research on motivation science:

About the Author

Daniel H. Pink is the author of seven books, including four New York Times bestsellers. Drive, translated into 40+ languages, changed how organizations think about motivation, and his TED Talk on motivation science is among the most-viewed of all time. He was previously chief speechwriter for Vice President Al Gore.

More skills from wondelai

domain-driven-design logo
wondelai/skills

domain-driven-design

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also...

2.3K 6.5K
View
clean-architecture logo
wondelai/skills

clean-architecture

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming...

2.3K 6.4K
View
top-design logo
wondelai/skills

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also ...

2.3K 6.4K
View
jobs-to-be-done logo
wondelai/skills

jobs-to-be-done

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs e...

2.3K 6.1K
View
microinteractions logo
wondelai/skills

microinteractions

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "interaction polish", "state transitions", or "input feedb...

2.3K 6K
View
clean-code logo
wondelai/skills

clean-code

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also tri...

2.3K 5.9K
View
refactoring-patterns logo
wondelai/skills

refactoring-patterns

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleani...

2.3K 5.7K
View
hooked-ux logo
wondelai/skills

hooked-ux

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "engagement loops", "habit formation", "push notifications", "variable rewards", "daily active users", "habit zone", or "user retention loo...

2.3K 5.6K
View
system-design logo
wondelai/skills

system-design

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning...

2.3K 5.5K
View
cro-methodology logo
wondelai/skills

cro-methodology

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger wh...

2.3K 5.5K
View

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigge...

2.3K 5.5K
View
storybrand-messaging logo
wondelai/skills

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting...

2.3K 5.4K
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View