本文へ移動
cccskills
無料GitHub で公開

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", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when designing onboarding progression, 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.

インストール方法を見る

含まれるファイル(8)

  • SKILL.md12.1 KB
  • references/applications.md16.6 KB
  • references/autonomy.md12.6 KB
  • references/case-studies.md14.0 KB
  • references/extrinsic-rewards.md14.6 KB
  • references/mastery.md14.4 KB
  • references/purpose.md14.4 KB
  • references/type-i.md15.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says 'it works but it is slow and getting worse'. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

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", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

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)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3972026年9月11日 更新

wondelai のスキルをすべて見る

このスキルの問題を報告する