[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C8NP1JB9JK7FQRFFSDTE5":3,"skill-same:01M73C8NP1JB9JK7FQRFFSDTE5":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73C8NP1JB9JK7FQRFFSDTE5","drive-motivation",null,"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 designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: drive-motivation\ndescription: '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 designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.'\nlicense: MIT\nmetadata:\n  author: wondelai\n  version: \"1.1.0\"\n---\n\n# Drive Motivation Framework\n\nFramework 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.\n\n## Core Principle\n\n**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.**\n\n**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.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating motivation systems (product features, team incentives, gamification, engagement loops), rate 0-10 based on AMP principles. A 10\u002F10 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\u002F10.\n\n## Motivation 1.0, 2.0, and 3.0\n\n| Version | Core Assumption | Approach | Era |\n|---------|----------------|----------|-----|\n| **1.0** | Humans are biological beings | Survival drives (food, shelter, safety) | Pre-industrial |\n| **2.0** | Humans respond to rewards\u002Fpunishments | Carrot and stick (bonuses, penalties) | Industrial age |\n| **3.0** | Humans seek autonomy, mastery, purpose | Intrinsic motivation | Knowledge economy |\n\n**The problem with Motivation 2.0 (carrot and stick):**\n\nMost organizations still run on Motivation 2.0, but it's fundamentally broken for modern work.\n\n### The Seven Deadly Flaws of Extrinsic Rewards\n\nExternal rewards (\"if-then\" rewards: \"If you do X, then you get Y\"):\n\n| Flaw | Mechanism | Example |\n|------|-----------|---------|\n| **1. Extinguish intrinsic motivation** | Turns play into work | Kids who were paid to draw stopped drawing when payments stopped |\n| **2. Diminish performance** | Narrow focus, reduce creativity | Candle problem: reward group performed worse |\n| **3. Crush creativity** | Focus on reward, not exploration | Artists creating commissioned work are less creative |\n| **4. Crowd out good behavior** | Financial framing replaces moral framing | Day care late-pickup fee: lateness increased (became a \"service\") |\n| **5. Encourage cheating** | Goal fixation leads to shortcuts | Wells Fargo fake accounts scandal |\n| **6. Become addictive** | Need bigger rewards over time | Bonus escalation: last year's bonus = this year's expectation |\n| **7. Foster short-term thinking** | Optimize for reward period | Quarterly bonuses → quarterly thinking |\n\n**When extrinsic rewards DO work:**\n- Routine, algorithmic tasks (assembly line, data entry)\n- Tasks requiring no creativity or judgment\n- When the task is genuinely boring and no intrinsic motivation exists\n\n**When extrinsic rewards DON'T work (and hurt):**\n- Creative work\n- Complex problem-solving\n- Any task requiring cognitive effort\n- Long-term engagement\n\nSee: [references\u002Fextrinsic-rewards.md](references\u002Fextrinsic-rewards.md) for the science behind reward failures.\n\n## The Three Pillars: Autonomy, Mastery, Purpose\n\n### 1. Autonomy\n\n**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.\n\n**Autonomy ≠ independence.** Autonomy means acting with choice. You can be autonomous while being interdependent with a team.\n\n**The Four T's of Autonomy:**\n\n| Dimension | Question | Example |\n|-----------|----------|---------|\n| **Task** | What do I work on? | Google's 20% time, Atlassian ShipIt days |\n| **Time** | When do I work? | Flexible hours, no mandatory meetings |\n| **Technique** | How do I do it? | Choose your own tools, methods, approach |\n| **Team** | Who do I work with? | Self-forming teams, choose collaborators |\n\n**Product applications:**\n\n| Context | Autonomy Killer | Autonomy Enabler |\n|---------|----------------|-------------------|\n| **Onboarding** | Forced linear tutorial | Choose your own path, skip steps |\n| **Customization** | One-size-fits-all | Themes, layouts, preferences |\n| **Content** | Algorithm-only feed | User-controlled feeds, filters |\n| **Communication** | Forced notifications | Notification preferences, DND |\n| **Workflow** | Rigid process | Flexible workflow, custom automations |\n| **Features** | Feature bloat (all visible) | Show\u002Fhide features, progressive disclosure |\n\n**Autonomy audit questions:**\n- Can users choose WHAT to do in the product?\n- Can users choose WHEN to engage?\n- Can users choose HOW to complete tasks?\n- Can users choose their own path through the experience?\n\n**Warning signs of autonomy violation:**\n- \"You must complete X before Y\"\n- Forced tutorials with no skip option\n- Mandatory notifications\n- No customization options\n- Rigid workflows with no flexibility\n\nSee: [references\u002Fautonomy.md](references\u002Fautonomy.md) for autonomy design patterns.\n\n### 2. Mastery\n\n**Definition:** The desire to get better at something that matters — to continually improve and grow.\n\n**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.\n\n**Three laws of mastery:**\n\n**Law 1: Mastery is a Mindset**\n- Growth mindset (Carol Dweck): Ability is developed, not fixed\n- People with growth mindset seek challenges and learn from failure\n- Fixed mindset people avoid challenges (might reveal inadequacy)\n- **Design implication:** Frame failures as learning, not judgment\n\n**Law 2: Mastery is a Pain**\n- Requires effort, deliberate practice, and grit\n- Flow (Csikszentmihalyi): Optimal state between boredom and anxiety\n- Challenge must match skill level — too easy = boring, too hard = anxious\n- **Design implication:** Calibrate difficulty to user's level\n\n**Law 3: Mastery is Asymptotic**\n- You can approach mastery but never fully arrive\n- The pursuit itself is the reward\n- **Design implication:** Always have next level, next challenge\n\n**The Flow Channel:**\n\n```\n                ANXIETY\n               \u002F\n              \u002F\n    FLOW ←──────────── Optimal challenge zone\n              \\\n               \\\n                BOREDOM\n\n    Low Skill ──────────────── High Skill\n```\n\n**Flow conditions:**\n- Clear goals\n- Immediate feedback\n- Challenge\u002Fskill balance\n- Sense of control\n- Deep concentration\n\n**Product applications:**\n\n| Context | Mastery Design | Example |\n|---------|---------------|---------|\n| **Progress** | Visible skill development | GitHub contribution graph, Duolingo levels |\n| **Difficulty** | Adaptive challenge | Games that adjust to player skill |\n| **Feedback** | Immediate, clear signals | Real-time writing analysis (Grammarly) |\n| **Goals** | Clear, achievable milestones | LinkedIn profile strength meter |\n| **Learning** | Skill trees, structured paths | Codecademy learning paths |\n| **Streaks** | Consistency tracking | Duolingo streaks (careful: can become extrinsic) |\n\n**Mastery audit questions:**\n- Can users see their progress over time?\n- Does the product adapt to skill level?\n- Is there immediate, meaningful feedback?\n- Are there clear next steps for improvement?\n- Does the challenge increase as skill increases?\n\n**Warning signs of mastery violation:**\n- No way to see improvement\n- Same difficulty regardless of skill\n- Delayed or absent feedback\n- No clear path forward\n- Punishing failures instead of teaching\n\nSee: [references\u002Fmastery.md](references\u002Fmastery.md) for mastery design patterns and flow state principles.\n\n### 3. Purpose\n\n**Definition:** The yearning to do what we do in the service of something larger than ourselves.\n\n**Purpose is the context for autonomy and mastery.** Without purpose, autonomy is directionless and mastery is hollow.\n\n**Three expressions of purpose:**\n\n| Expression | How It Manifests | Example |\n|-----------|-----------------|---------|\n| **Goals** | Purpose-driven objectives | TOMS: \"With every product you purchase, TOMS will help a person in need\" |\n| **Words** | Language of purpose, not profit | \"Associates\" not \"employees\", \"community\" not \"users\" |\n| **Policies** | Actions that demonstrate purpose | Patagonia: \"Don't Buy This Jacket\" campaign |\n\n**Product applications:**\n\n| Context | Purpose Design | Example |\n|---------|---------------|---------|\n| **Mission** | Clear, inspiring why | \"Organize the world's information\" (Google) |\n| **Impact** | Show user's contribution | Wikipedia edit counter, Kiva lending impact |\n| **Community** | Connect to something bigger | Open source contribution, community goals |\n| **Transparency** | Show how product helps | Charity: Water shows exact well location |\n| **Values** | Align product with beliefs | Ecosia: \"Search the web to plant trees\" |\n\n**Purpose audit questions:**\n- Does the user understand WHY this product\u002Ffeature exists?\n- Can users see their impact on something bigger?\n- Does the product connect to values the user cares about?\n- Is there a mission beyond profit?\n\n**Purpose in product design:**\n- Show aggregate impact (\"Together, our users have saved 1M hours\")\n- Connect individual actions to collective outcomes\n- Frame features in terms of why, not just what\n- Celebrate meaningful milestones, not vanity metrics\n\nSee: [references\u002Fpurpose.md](references\u002Fpurpose.md) for purpose-driven design patterns.\n\n## AMP Applied: Product Design\n\n### Gamification Done Right vs. Wrong\n\n**Wrong gamification (extrinsic, Motivation 2.0):**\n- Points for every action (becomes meaningless)\n- Badges for trivial achievements\n- Leaderboards that discourage (I'll never catch up)\n- Rewards that replace intrinsic motivation\n\n**Right gamification (intrinsic, Motivation 3.0):**\n\n| Principle | Bad (Extrinsic) | Good (Intrinsic) |\n|-----------|-----------------|-------------------|\n| **Autonomy** | Forced challenges, mandatory participation | Choose challenges, opt-in |\n| **Mastery** | Points for everything | Skill-based progression, meaningful milestones |\n| **Purpose** | Pointless competition | Contribute to community, personal growth |\n\n**Example: Duolingo**\n- **Autonomy:** Choose language, pace, topics\n- **Mastery:** Adaptive difficulty, progress tracking, skill levels\n- **Purpose:** \"Learn a language to connect with people\"\n- **Caution:** Streaks can shift from mastery (intrinsic) to loss aversion (extrinsic)\n\n### Team Motivation\n\n**How to apply AMP to team management:**\n\n| Principle | Manager Action | Example |\n|-----------|---------------|---------|\n| **Autonomy** | Give control over task, time, technique, team | \"Here's the goal. How you get there is up to you.\" |\n| **Mastery** | Provide challenge, feedback, growth | Stretch assignments, mentorship, skill development budget |\n| **Purpose** | Connect work to mission | \"Here's why this matters for our customers\" |\n\n**\"If-then\" vs. \"Now that\" rewards:**\n- **Bad:** \"If you hit target, you get bonus\" (if-then, creates pressure)\n- **Better:** \"You hit target! Here's a bonus.\" (now-that, unexpected recognition)\n- **Best:** \"Let's talk about what you want to work on next.\" (intrinsic)\n\n### Compensation and Incentives\n\n**Pink's recommendations:**\n1. Pay people enough to take money off the table\n2. Then focus on autonomy, mastery, purpose\n3. Use \"now-that\" rewards (unexpected), not \"if-then\" rewards (contingent)\n\n**The baseline:**\n- Fair compensation eliminates distraction\n- Above-market pay signals respect\n- But beyond \"enough,\" more money doesn't increase motivation\n- Once baseline is met, AMP drives engagement\n\nSee: [references\u002Fapplications.md](references\u002Fapplications.md) for product and team applications.\n\n## Type I vs. Type X Behavior\n\n| Type X (Extrinsic) | Type I (Intrinsic) |\n|--------------------|---------------------|\n| Fueled by external rewards | Fueled by autonomy, mastery, purpose |\n| Concerned with external recognition | Concerned with inherent satisfaction |\n| Short-term focused | Long-term focused |\n| Sees effort as burden | Sees effort as path to mastery |\n| Fixed mindset tendencies | Growth mindset tendencies |\n\n**Goal:** Design products and teams that cultivate Type I behavior.\n\n**Type I behavior:**\n- Is made, not born (anyone can develop it)\n- Doesn't disdain money or recognition\n- Is a renewable resource (doesn't deplete)\n- Promotes greater physical and mental well-being\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Points for everything** | Crowds out intrinsic motivation | Reserve rewards for meaningful milestones |\n| **Mandatory participation** | Kills autonomy | Make engagement opt-in |\n| **Same challenge for everyone** | No flow state (bored or anxious) | Adaptive difficulty matching |\n| **No visible progress** | Can't see mastery | Progress indicators, skill tracking |\n| **Missing \"why\"** | Actions feel meaningless | Connect every feature to purpose |\n| **If-then bonuses** | Creates short-term thinking | Pay fairly, focus on AMP |\n\n## Quick Diagnostic\n\nAudit any motivation system:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Can users choose what\u002Fwhen\u002Fhow? | Autonomy violation | Add choices, flexibility, customization |\n| Can users see their progress? | No mastery signal | Add progress tracking, skill levels |\n| Is the challenge matched to skill? | Boredom or anxiety | Implement adaptive difficulty |\n| Is there immediate feedback? | Can't improve | Add real-time response to actions |\n| Does the user know WHY this matters? | No purpose | Connect to mission, show impact |\n| Are we using \"if-then\" rewards? | Extrinsic motivation | Switch to \"now-that\" or intrinsic design |\n\n## Reference Files\n\n- [extrinsic-rewards.md](references\u002Fextrinsic-rewards.md): The seven flaws, when rewards work and don't\n- [autonomy.md](references\u002Fautonomy.md): Four T's, product and team autonomy design\n- [mastery.md](references\u002Fmastery.md): Flow state, growth mindset, deliberate practice\n- [purpose.md](references\u002Fpurpose.md): Purpose-driven design, mission alignment\n- [applications.md](references\u002Fapplications.md): Product gamification, team management, compensation\n- [type-i.md](references\u002Ftype-i.md): Type I vs. Type X, cultivating intrinsic motivation\n- [case-studies.md](references\u002Fcase-studies.md): Atlassian, 3M, Duolingo, ROWE, Wikipedia\n\n## Further Reading\n\nThis skill is based on Daniel Pink's research on motivation science. For the complete framework:\n\n- [*\"Drive: The Surprising Truth About What Motivates Us\"*](https:\u002F\u002Fwww.amazon.com\u002FDrive-Surprising-Truth-About-Motivates\u002Fdp\u002F1594484805?tag=wondelai00-20) by Daniel H. Pink\n- [*\"To Sell Is Human\"*](https:\u002F\u002Fwww.amazon.com\u002FSell-Human-Surprising-Moving-Others\u002Fdp\u002F1594631905?tag=wondelai00-20) by Daniel H. Pink (applying motivation to sales and persuasion)\n\n## About the Author\n\n**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.\n","# Drive Motivation Framework\n\nFramework 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.\n\n## Core Principle\n\n**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.**\n\n**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.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating motivation systems (product features, team incentives, gamification, engagement loops), rate 0-10 based on AMP principles. A 10\u002F10 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\u002F10.\n\n## Motivation 1.0, 2.0, and 3.0\n\n| Version | Core Assumption | Approach | Era |\n|---------|----------------|----------|-----|\n| **1.0** | Humans are biological beings | Survival drives (food, shelter, safety) | Pre-industrial |\n| **2.0** | Humans respond to rewards\u002Fpunishments | Carrot and stick (bonuses, penalties) | Industrial age |\n| **3.0** | Humans seek autonomy, mastery, purpose | Intrinsic motivation | Knowledge economy |\n\n**The problem with Motivation 2.0 (carrot and stick):**\n\nMost organizations still run on Motivation 2.0, but it's fundamentally broken for modern work.\n\n### The Seven Deadly Flaws of Extrinsic Rewards\n\nExternal rewards (\"if-then\" rewards: \"If you do X, then you get Y\"):\n\n| Flaw | Mechanism | Example |\n|------|-----------|---------|\n| **1. Extinguish intrinsic motivation** | Turns play into work | Kids who were paid to draw stopped drawing when payments stopped |\n| **2. Diminish performance** | Narrow focus, reduce creativity | Candle problem: reward group performed worse |\n| **3. Crush creativity** | Focus on reward, not exploration | Artists creating commissioned work are less creative |\n| **4. Crowd out good behavior** | Financial framing replaces moral framing | Day care late-pickup fee: lateness increased (became a \"service\") |\n| **5. Encourage cheating** | Goal fixation leads to shortcuts | Wells Fargo fake accounts scandal |\n| **6. Become addictive** | Need bigger rewards over time | Bonus escalation: last year's bonus = this year's expectation |\n| **7. Foster short-term thinking** | Optimize for reward period | Quarterly bonuses → quarterly thinking |\n\n**When extrinsic rewards DO work:**\n- Routine, algorithmic tasks (assembly line, data entry)\n- Tasks requiring no creativity or judgment\n- When the task is genuinely boring and no intrinsic motivation exists\n\n**When extrinsic rewards DON'T work (and hurt):**\n- Creative work\n- Complex problem-solving\n- Any task requiring cognitive effort\n- Long-term engagement\n\nSee: [references\u002Fextrinsic-rewards.md](references\u002Fextrinsic-rewards.md) for the science behind reward failures.\n\n## The Three Pillars: Autonomy, Mastery, Purpose\n\n### 1. Autonomy\n\n**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.\n\n**Autonomy ≠ independence.** Autonomy means acting with choice. You can be autonomous while being interdependent with a team.\n\n**The Four T's of Autonomy:**\n\n| Dimension | Question | Example |\n|-----------|----------|---------|\n| **Task** | What do I work on? | Google's 20% time, Atlassian ShipIt days |\n| **Time** | When do I work? | Flexible hours, no mandatory meetings |\n| **Technique** | How do I do it? | Choose your own tools, methods, approach |\n| **Team** | Who do I work with? | Self-forming teams, choose collaborators |\n\n**Product applications:**\n\n| Context | Autonomy Killer | Autonomy Enabler |\n|---------|----------------|-------------------|\n| **Onboarding** | Forced linear tutorial | Choose your own path, skip steps |\n| **Customization** | One-size-fits-all | Themes, layouts, preferences |\n| **Content** | Algorithm-only feed | User-controlled feeds, filters |\n| **Communication** | Forced notifications | Notification preferences, DND |\n| **Workflow** | Rigid process | Flexible workflow, custom automations |\n| **Features** | Feature bloat (all visible) | Show\u002Fhide features, progressive disclosure |\n\n**Autonomy audit questions:**\n- Can users choose WHAT to do in the product?\n- Can users choose WHEN to engage?\n- Can users choose HOW to complete tasks?\n- Can users choose their own path through the experience?\n\n**Warning signs of autonomy violation:**\n- \"You must complete X before Y\"\n- Forced tutorials with no skip option\n- Mandatory notifications\n- No customization options\n- Rigid workflows with no flexibility\n\nSee: [references\u002Fautonomy.md](references\u002Fautonomy.md) for autonomy design patterns.\n\n### 2. Mastery\n\n**Definition:** The desire to get better at something that matters — to continually improve and grow.\n\n**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.\n\n**Three laws of mastery:**\n\n**Law 1: Mastery is a Mindset**\n- Growth mindset (Carol Dweck): Ability is developed, not fixed\n- People with growth mindset seek challenges and learn from failure\n- Fixed mindset people avoid challenges (might reveal inadequacy)\n- **Design implication:** Frame failures as learning, not judgment\n\n**Law 2: Mastery is a Pain**\n- Requires effort, deliberate practice, and grit\n- Flow (Csikszentmihalyi): Optimal state between boredom and anxiety\n- Challenge must match skill level — too easy = boring, too hard = anxious\n- **Design implication:** Calibrate difficulty to user's level\n\n**Law 3: Mastery is Asymptotic**\n- You can approach mastery but never fully arrive\n- The pursuit itself is the reward\n- **Design implication:** Always have next level, next challenge\n\n**The Flow Channel:**\n\n```\n                ANXIETY\n               \u002F\n              \u002F\n    FLOW ←──────────── Optimal challenge zone\n              \\\n               \\\n                BOREDOM\n\n    Low Skill ──────────────── High Skill\n```\n\n**Flow conditions:**\n- Clear goals\n- Immediate feedback\n- Challenge\u002Fskill balance\n- Sense of control\n- Deep concentration\n\n**Product applications:**\n\n| Context | Mastery Design | Example |\n|---------|---------------|---------|\n| **Progress** | Visible skill development | GitHub contribution graph, Duolingo levels |\n| **Difficulty** | Adaptive challenge | Games that adjust to player skill |\n| **Feedback** | Immediate, clear signals | Real-time writing analysis (Grammarly) |\n| **Goals** | Clear, achievable milestones | LinkedIn profile strength meter |\n| **Learning** | Skill trees, structured paths | Codecademy learning paths |\n| **Streaks** | Consistency tracking | Duolingo streaks (careful: can become extrinsic) |\n\n**Mastery audit questions:**\n- Can users see their progress over time?\n- Does the product adapt to skill level?\n- Is there immediate, meaningful feedback?\n- Are there clear next steps for improvement?\n- Does the challenge increase as skill increases?\n\n**Warning signs of mastery violation:**\n- No way to see improvement\n- Same difficulty regardless of skill\n- Delayed or absent feedback\n- No clear path forward\n- Punishing failures instead of teaching\n\nSee: [references\u002Fmastery.md](references\u002Fmastery.md) for mastery design patterns and flow state principles.\n\n### 3. Purpose\n\n**Definition:** The yearning to do what we do in the service of something larger than ourselves.\n\n**Purpose is the context for autonomy and mastery.** Without purpose, autonomy is directionless and mastery is hollow.\n\n**Three expressions of purpose:**\n\n| Expression | How It Manifests | Example |\n|-----------|-----------------|---------|\n| **Goals** | Purpose-driven objectives | TOMS: \"With every product you purchase, TOMS will help a person in need\" |\n| **Words** | Language of purpose, not profit | \"Associates\" not \"employees\", \"community\" not \"users\" |\n| **Policies** | Actions that demonstrate purpose | Patagonia: \"Don't Buy This Jacket\" campaign |\n\n**Product applications:**\n\n| Context | Purpose Design | Example |\n|---------|---------------|---------|\n| **Mission** | Clear, inspiring why | \"Organize the world's information\" (Google) |\n| **Impact** | Show user's contribution | Wikipedia edit counter, Kiva lending impact |\n| **Community** | Connect to something bigger | Open source contribution, community goals |\n| **Transparency** | Show how product helps | Charity: Water shows exact well location |\n| **Values** | Align product with beliefs | Ecosia: \"Search the web to plant trees\" |\n\n**Purpose audit questions:**\n- Does the user understand WHY this product\u002Ffeature exists?\n- Can users see their impact on something bigger?\n- Does the product connect to values the user cares about?\n- Is there a mission beyond profit?\n\n**Purpose in product design:**\n- Show aggregate impact (\"Together, our users have saved 1M hours\")\n- Connect individual actions to collective outcomes\n- Frame features in terms of why, not just what\n- Celebrate meaningful milestones, not vanity metrics\n\nSee: [references\u002Fpurpose.md](references\u002Fpurpose.md) for purpose-driven design patterns.\n\n## AMP Applied: Product Design\n\n### Gamification Done Right vs. Wrong\n\n**Wrong gamification (extrinsic, Motivation 2.0):**\n- Points for every action (becomes meaningless)\n- Badges for trivial achievements\n- Leaderboards that discourage (I'll never catch up)\n- Rewards that replace intrinsic motivation\n\n**Right gamification (intrinsic, Motivation 3.0):**\n\n| Principle | Bad (Extrinsic) | Good (Intrinsic) |\n|-----------|-----------------|-------------------|\n| **Autonomy** | Forced challenges, mandatory participation | Choose challenges, opt-in |\n| **Mastery** | Points for everything | Skill-based progression, meaningful milestones |\n| **Purpose** | Pointless competition | Contribute to community, personal growth |\n\n**Example: Duolingo**\n- **Autonomy:** Choose language, pace, topics\n- **Mastery:** Adaptive difficulty, progress tracking, skill levels\n- **Purpose:** \"Learn a language to connect with people\"\n- **Caution:** Streaks can shift from mastery (intrinsic) to loss aversion (extrinsic)\n\n### Team Motivation\n\n**How to apply AMP to team management:**\n\n| Principle | Manager Action | Example |\n|-----------|---------------|---------|\n| **Autonomy** | Give control over task, time, technique, team | \"Here's the goal. How you get there is up to you.\" |\n| **Mastery** | Provide challenge, feedback, growth | Stretch assignments, mentorship, skill development budget |\n| **Purpose** | Connect work to mission | \"Here's why this matters for our customers\" |\n\n**\"If-then\" vs. \"Now that\" rewards:**\n- **Bad:** \"If you hit target, you get bonus\" (if-then, creates pressure)\n- **Better:** \"You hit target! Here's a bonus.\" (now-that, unexpected recognition)\n- **Best:** \"Let's talk about what you want to work on next.\" (intrinsic)\n\n### Compensation and Incentives\n\n**Pink's recommendations:**\n1. Pay people enough to take money off the table\n2. Then focus on autonomy, mastery, purpose\n3. Use \"now-that\" rewards (unexpected), not \"if-then\" rewards (contingent)\n\n**The baseline:**\n- Fair compensation eliminates distraction\n- Above-market pay signals respect\n- But beyond \"enough,\" more money doesn't increase motivation\n- Once baseline is met, AMP drives engagement\n\nSee: [references\u002Fapplications.md](references\u002Fapplications.md) for product and team applications.\n\n## Type I vs. Type X Behavior\n\n| Type X (Extrinsic) | Type I (Intrinsic) |\n|--------------------|---------------------|\n| Fueled by external rewards | Fueled by autonomy, mastery, purpose |\n| Concerned with external recognition | Concerned with inherent satisfaction |\n| Short-term focused | Long-term focused |\n| Sees effort as burden | Sees effort as path to mastery |\n| Fixed mindset tendencies | Growth mindset tendencies |\n\n**Goal:** Design products and teams that cultivate Type I behavior.\n\n**Type I behavior:**\n- Is made, not born (anyone can develop it)\n- Doesn't disdain money or recognition\n- Is a renewable resource (doesn't deplete)\n- Promotes greater physical and mental well-being\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Points for everything** | Crowds out intrinsic motivation | Reserve rewards for meaningful milestones |\n| **Mandatory participation** | Kills autonomy | Make engagement opt-in |\n| **Same challenge for everyone** | No flow state (bored or anxious) | Adaptive difficulty matching |\n| **No visible progress** | Can't see mastery | Progress indicators, skill tracking |\n| **Missing \"why\"** | Actions feel meaningless | Connect every feature to purpose |\n| **If-then bonuses** | Creates short-term thinking | Pay fairly, focus on AMP |\n\n## Quick Diagnostic\n\nAudit any motivation system:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Can users choose what\u002Fwhen\u002Fhow? | Autonomy violation | Add choices, flexibility, customization |\n| Can users see their progress? | No mastery signal | Add progress tracking, skill levels |\n| Is the challenge matched to skill? | Boredom or anxiety | Implement adaptive difficulty |\n| Is there immediate feedback? | Can't improve | Add real-time response to actions |\n| Does the user know WHY this matters? | No purpose | Connect to mission, show impact |\n| Are we using \"if-then\" rewards? | Extrinsic motivation | Switch to \"now-that\" or intrinsic design |\n\n## Reference Files\n\n- [extrinsic-rewards.md](references\u002Fextrinsic-rewards.md): The seven flaws, when rewards work and don't\n- [autonomy.md](references\u002Fautonomy.md): Four T's, product and team autonomy design\n- [mastery.md](references\u002Fmastery.md): Flow state, growth mindset, deliberate practice\n- [purpose.md](references\u002Fpurpose.md): Purpose-driven design, mission alignment\n- [applications.md](references\u002Fapplications.md): Product gamification, team management, compensation\n- [type-i.md](references\u002Ftype-i.md): Type I vs. Type X, cultivating intrinsic motivation\n- [case-studies.md](references\u002Fcase-studies.md): Atlassian, 3M, Duolingo, ROWE, Wikipedia\n\n## Further Reading\n\nThis skill is based on Daniel Pink's research on motivation science. For the complete framework:\n\n- [*\"Drive: The Surprising Truth About What Motivates Us\"*](https:\u002F\u002Fwww.amazon.com\u002FDrive-Surprising-Truth-About-Motivates\u002Fdp\u002F1594484805?tag=wondelai00-20) by Daniel H. Pink\n- [*\"To Sell Is Human\"*](https:\u002F\u002Fwww.amazon.com\u002FSell-Human-Surprising-Moving-Others\u002Fdp\u002F1594631905?tag=wondelai00-20) by Daniel H. Pink (applying motivation to sales and persuasion)\n\n## About the Author\n\n**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.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"wondelai","1.1.0","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fwondelai-drive-motivation","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill drive-motivation",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill drive-motivation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill drive-motivation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002FSKILL.md",true,[49,55,59,63,67,71,75],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fapplications.md","REFERENCE","参考文档",17021,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fapplications.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fautonomy.md",12915,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fautonomy.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcase-studies.md",14314,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fcase-studies.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fextrinsic-rewards.md",14983,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fextrinsic-rewards.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fmastery.md",14755,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fmastery.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fpurpose.md",14774,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Fpurpose.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ftype-i.md",15984,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fwondelai-drive-motivation\u002Freferences\u002Ftype-i.md",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]