Skip to main content
ClaudeWave
Skill1.3k estrellas del repoactualizado 2d ago

drive-motivation

# ClaudeWave Entry: drive-motivation The drive-motivation skill designs motivation systems based on autonomy, mastery, and purpose (AMP) rather than traditional carrot-and-stick rewards. Use it when addressing intrinsic motivation challenges, fixing broken gamification, building team incentives, designing onboarding progressions, or creating performance systems that sustain engagement through meaningful work rather than external rewards.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/wondelai/skills /tmp/drive-motivation && cp -r /tmp/drive-motivation/drive-motivation ~/.claude/skills/drive-motivation
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Drive Motivation Framework

Design motivation systems for products, teams, and organizations based on the science of what actually motivates humans — replacing 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.** 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.** Rate any motivation system (product features, team incentives, gamification, engagement loops) 0-10 against the AMP principles below. A 10/10 supports autonomy, enables mastery, and connects to purpose; lower scores indicate reliance on extrinsic rewards or controlling behaviors. Always state the current score and the specific improvements needed to reach 10/10.

## Motivation 1.0, 2.0, and 3.0

| Version | Core Assumption | Approach | Era |
|---------|----------------|----------|-----|
| **1.0** | Humans are biological | Survival drives | Pre-industrial |
| **2.0** | Humans respond to rewards/punishments | Carrot and stick | Industrial age |
| **3.0** | Humans seek autonomy, mastery, purpose | Intrinsic motivation | Knowledge economy |

Most organizations still run on Motivation 2.0 — fundamentally broken for modern cognitive work.

### The Seven Deadly Flaws of Extrinsic Rewards

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

| Flaw | Mechanism | Example |
|------|-----------|---------|
| **1. Extinguish intrinsic motivation** | Turns play into work | Kids paid to draw stopped drawing when payments stopped |
| **2. Diminish performance** | Narrow focus, reduce creativity | Candle problem: rewarded group performed worse |
| **3. Crush creativity** | Reward focus replaces exploration | Commissioned art rated less creative |
| **4. Crowd out good behavior** | Financial framing replaces moral framing | Day-care late fee: lateness increased (became a "service") |
| **5. Encourage cheating** | Goal fixation invites shortcuts | Wells Fargo fake accounts |
| **6. Become addictive** | Bigger rewards needed over time | Last year's bonus = this year's expectation |
| **7. Foster short-term thinking** | Optimize for the reward period | Quarterly 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](references/extrinsic-rewards.md) for the science behind reward failures.

## 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:**

| Dimension | Question | Example |
|-----------|----------|---------|
| **Task** | What do I work on? | Google's 20% time, Atlassian ShipIt days |
| **Time** | When do I work? | Flexible hours, no mandatory meetings |
| **Technique** | How do I do it? | Choose tools, methods, approach |
| **Team** | Who do I work with? | Self-forming teams |

**Product applications:**

| Context | Autonomy Killer | Autonomy Enabler |
|---------|----------------|-------------------|
| **Onboarding** | Forced linear tutorial | Choose your path, skip steps |
| **Content** | Algorithm-only feed | User-controlled feeds, filters |
| **Workflow** | Rigid process, feature bloat | Custom automations, show/hide, progressive disclosure |

**Autonomy audit:** can users choose WHAT to do, WHEN to engage, HOW to complete tasks, and their own path through the experience? "You must complete X before Y", unskippable tutorials, and mandatory notifications are violations.

See: [references/autonomy.md](references/autonomy.md) for autonomy design patterns.

### 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:**

| Context | Mastery Design | Example |
|---------|---------------|---------|
| **Progress** | Visible skill development | GitHub contribution graph, Duolingo levels |
| **Difficulty** | Adaptive challenge | Games that adjust to player skill |
| **Feedback** | Immediate, clear signals | Grammarly real-time writing analysis |

**Mastery audit:** can users see progress over time, get immediate feedback, and find a clear next step? Flat difficulty and punished failure are violations.

See: [references/mastery.md](references/mastery.md) for mastery design patterns and flow state principles.

### 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:**

| Expression | How It Manifests | Example |
|-----------|-----------------|---------|
| **Goals** | Purpose-driven objectives | TOMS: every purchase helps a person in need |
| **Words** | Language of purpose, not profit | "Associates" not "employees", "community" not "users" |
| **Policies** | Actions that demonstrate purpose | Pat
37signals-waySkill

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

blue-ocean-strategySkill

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

clean-architectureSkill

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 architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

clean-codeSkill

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 trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

contagiousSkill

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

continuous-discoverySkill

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

cro-methodologySkill

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 when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

crossing-the-chasmSkill

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.