Drive Pink

1. 1Diagnose the task type before you design the motivation. Sort the work into algorithmic (single established pathway to one conclusion) versus heuristic (no algorithm exists, requires experimentation). Intrinsic motivation is the load-bearing drive only for the heuristic, complex, self-directed work.
2. 2Strip out or de-emphasize salient external rewards for work you want people to sustain. Deci's rule: 'the less salient they are made, the better.' Do not dangle cash, grades, or contingent bonuses as the reason to engage—those deliver a short-term boost then erode longer-term interest.
3. 3Build for the state of optimal challenge ('flow') by matching difficulty to capacity—hard enough that mastering it feels gratifying, not so hard it defeats. Open-source developers reported reaching flow frequently, and that creative feeling was the strongest driver of participation.
4. 4Feed the three innate needs Deci and Ryan name in self-determination theory: competence (getting better), autonomy (directing your own life), and relatedness. When satisfied, motivation, productivity, and happiness rise; when thwarted, they plummet.
5. 5Diagnose before you incentivize. When someone isn't producing, Ryan warns against 'trying to run over the problem with a carrot or a stick.' Ask what actual need—competence, autonomy, relatedness—is being blocked, then remove the block.
6. 6Preserve the environment, because this drive is fragile. Deci found the third drive 'needed the right environment to survive'—so protect the task's inherent interest rather than layering controls on top of it.
7. 7Let people give and create. The German study of open-source projects found participants driven by 'the fun of mastering the challenge' and 'the desire to give a gift to the programmer community'—design work so contribution itself is the payoff.

Deci's Soma puzzle experiment is the template. He gave participants an inherently engaging Parker Brothers cube (millions of possible configurations) and split them into groups. Group A was paid to solve puzzles during one session; the other group was not. When the money stopped, Group A—the previously paid subjects—spent significantly less free-choice time playing: about two minutes less than their paid session and a full minute less than their very first, unpaid session when they'd obviously enjoyed the puzzle. The unpaid group's interest held steady. Deci concluded, 'When money is used as an external reward for some activity, the subjects lose intrinsic interest for the activity.' The lesson: introducing a salient reward for something already enjoyable didn't amplify the drive—it corroded it, echoing Harlow's monkeys, whose performance was disrupted, not improved, when raisins were introduced.

• If the task is heuristic and self-directed, then rely on intrinsic motivation and protect the joy of the task; if it's purely algorithmic and routine, external incentives may still work (Chapter 2a's special circumstances).
• If people already find the activity gratifying, then do not attach a salient contingent reward—Deci and Harlow both show this reduces frequency and quality.
• If a reward is genuinely necessary (as in most workplaces), then make it as non-salient as possible—'when people use rewards to motivate, that's when they're most demotivating.'
• If someone stops producing, then diagnose the thwarted need (competence, autonomy, or relatedness) before reaching for a carrot or stick.
• If you want durable engagement rather than a short burst, then build for flow and mastery—rewards give only a caffeine-like jolt that wears off.

• Assuming rewards always intensify interest. The tell: performance or free-choice engagement drops after you add pay or prizes—Deci's Group A played a full minute less than before they were ever paid.
• Treating the third drive as subordinate to the biological and extrinsic drives. The tell: you 'sweeten' an already-loved task with raisins/cash and watch errors rise, as Harlow's monkeys did.
• Making rewards highly salient. The tell: people talk about the bonus or grade rather than the work itself, and motivation collapses once the reward is removed.
• Running over problems with carrots and sticks instead of diagnosing. The tell: you've never identified whether the block is competence, autonomy, or relatedness—Ryan's 'you haven't done the hard work of diagnosing.'
• Ignoring the fragility of intrinsic motivation. The tell: you design controls and external-control systems (monetary rewards, monitoring) and the inherent interest quietly disappears because the environment stopped supporting it.
• Applying Taylorist assumptions to complex work. The tell: you assume work is 'simple, not particularly interesting' needing incentives and monitoring, while the actual job is heuristic and self-directed.

• ▸Task type: algorithmic or heuristic? (name the single pathway, or note none exists)
• ▸Current salient rewards: list any cash/grades/bonuses tied to this activity
• ▸Reward salience test: could you make each reward less prominent or non-contingent? how?
• ▸Flow check: is difficulty matched to capacity for optimal challenge? (too easy / right / too hard)
• ▸Competence: what makes the person feel they're getting better here?
• ▸Autonomy: where can the person direct their own approach, time, or method?
• ▸Relatedness / gift: is there a way contribution serves a community they care about?
• ▸Blocked-need diagnosis: which innate need is thwarted right now, and what's the evidence?
• ▸Environment action: one change that protects the joy of the task instead of controlling it

1. 1Set a single, concrete goal for the session so you know exactly what "done" looks like—reach the top of the mountain, hit the ball across the net, mold the clay just right. Vague goals prevent flow.
2. 2Calibrate the challenge to a notch or two beyond current ability. Assess your actual skill, then set the task slightly above it so it stretches you without overwhelming. Too easy produces boredom; too hard produces anxiety.
3. 3Build in immediate feedback loops so you can tell in real time whether you're succeeding—the mountaintop gets closer or farther, the ball lands in or out, the pot comes out smooth or uneven. If your work lacks natural feedback, engineer a signal.
4. 4Strip out salient extrinsic rewards during the task. Per Deci, rewards are most demotivating when made most salient; adding carrots on top of inherently interesting work dampens motivation. Make any necessary rewards low-key.
5. 5Protect uninterrupted, self-directed time. Flow depends on autonomy and deep engagement; monitoring and interruption break the state where sense of time, place, and self melt away.
6. 6Replace annual review cycles with frequent engagement check-ins. Following Ericsson's Stefan Falk, sit down one-on-one multiple times a year to recalibrate objectives and discuss the path toward mastery, rather than waiting twelve months.
7. 7Re-tune when the state breaks: if bored, raise the challenge; if anxious, lower it or build skill. Treat the challenge-skill match as a dial you adjust continuously, not a one-time setup.

Stefan Falk, a vice president at Ericsson, used flow principles to smooth a merger of the company's business units. He persuaded managers to configure work assignments so employees had clear objectives—satisfying the "goals are clear" condition of flow. He also gave employees a way to get quick feedback rather than leaving them to guess how they were doing. Instead of once-a-year performance reviews, managers sat down with employees one-on-one six times a year, often for as long as ninety minutes, to discuss engagement and the path toward mastery. This turned periodic judgment into continuous recalibration of the challenge-skill balance. The strategy worked well enough that Ericsson adopted it in offices around the world, after which Falk carried it to Green Cargo. The case shows flow isn't a happy accident but a set of conditions—clear goals, immediate feedback, matched challenge—you can deliberately build into work.

• If a task is heuristic (solving novel problems, creating something new) rather than algorithmic/routine, then rely on flow and intrinsic motivation—not carrots and sticks, which impair creative performance.
• If the person is bored, then the challenge is too easy—raise it; if anxious, then it's too hard—lower it or build the underlying skill first.
• If you must use a reward, then make it as un-salient as possible; salient rewards on interesting work are the most demotivating.
• If work is nonroutine and interesting, then favor self-direction and minimal monitoring; save close direction for routine, not-so-interesting jobs.
• If feedback isn't immediate and natural in the task, then build an explicit signal so progress is visible in real time.

• Treating flow as a happy accident rather than a designed condition—the Type X assumption. Tell: managers who never structure goals or feedback and are surprised engagement is low.
• Leaving goals vague. Tell: the person can't say what "done" looks like, so there's no target to lose themselves in.
• Piling salient extrinsic rewards onto inherently interesting work. Tell: motivation and performance drop after the reward is introduced, exactly as Deci found.
• Mismatching challenge and skill. Tell: chronic boredom (task too easy) or chronic anxiety (task too hard)—neither produces the absorbed, time-melting state.
• Relying on annual reviews and heavy monitoring. Tell: feedback arrives months late and workers feel watched, breaking the autonomy and immediacy flow requires.

• ▸Task: name the one thing you'll work on this session
• ▸Clear goal: state exactly what "done" looks like (top of mountain, ball across net)
• ▸Current skill level: honestly rate your ability at this task (1-10)
• ▸Challenge setting: describe how this task sits a notch or two above that level
• ▸Feedback signal: name the immediate cue that tells you if you're succeeding
• ▸Reward check: list any extrinsic rewards present and how to make them less salient
• ▸Protected time block: set the uninterrupted, self-directed window
• ▸Recalibration note: after the session, mark whether you felt bored (raise challenge) or anxious (lower it/build skill)

1. 1Name your operating self-theory for a specific ability. Ask: do I treat this capacity as fixed (like height) or malleable (like strength you build by pumping iron)? The answer determines whether encounters become measures or opportunities.
2. 2Convert your performance goals into learning goals. Restate 'get an A in French class' as 'be able to speak French.' Both fuel achievement, but only the learning goal survives contact with novel problems.
3. 3Reframe effort as the mechanism of improvement, not a signal of deficiency. When work feels hard, read it as 'this is how I get better' rather than 'this means I'm not good.' Refuse the diet of easy successes.
4. 4Deliberately choose stretch targets over easy wins. Entity thinking picks tasks that affirm existing ability; incremental thinking picks tasks slightly beyond current reach that expand it, even at the cost of looking less competent short-term.
5. 5When you hit a wall, blame nothing—not your intelligence, not the task. Treat the setback as an inevitable guidepost on the road to mastery, and respond by trying more solutions and inventing new strategies.
6. 6Apply the frame to any capability, not just intelligence. Dweck's findings extend to most human capacities, so run the same fixed-vs-malleable check on skills like empathy, writing, or leadership.

In one Dweck study, junior high students learned a set of scientific principles under two conditions: half were given a performance goal, half a learning goal. Both groups demonstrated they had grasped the material equally. Then researchers asked them to apply that knowledge to a new set of problems—related but not identical to what they'd studied. The learning-goal students scored significantly higher on these novel challenges, worked longer, and tried more solutions. The performance goal had worked fine for straightforward problems but inhibited transfer to new situations. The lesson is operational: if you want a skill that survives novelty, orient toward learning the thing rather than proving you're smart, because learning goals let you 'hang in and keep trying' without first needing to feel you're already good.

• If a task is straightforward and one-off, a performance goal is fine; if it requires applying concepts to new situations, switch to a learning goal.
• If you find yourself choosing an easy target to protect your self-image, treat that as a fixed-mindset tell and pick a harder one instead.
• If effort makes you feel exposed as 'not very good,' flip the interpretation: exertion is how malleable ability gets stronger.
• If a setback triggers you to blame your intelligence, stop and reclassify the setback as an inevitable guidepost, then generate a new strategy.
• If mastery is the goal, begin from the incremental theory—starting from the entity theory makes mastery impossible by design.

• Wanting to look like a master without expending the effort to attain mastery—tell: you gravitate to tasks you already ace and avoid ones you'd have to struggle through.
• Confusing early success with durability—tell: you crush the practice set then collapse when the problem is slightly rephrased or novel.
• Reading hard work as evidence of low ability—tell: you quit or feel ashamed the moment something requires sustained struggle, like the fixed-mindset fifth-graders who gave up on the tough problems.
• Chasing performance goals exclusively (the A, the high mark) so that knowledge doesn't transfer—tell: strong grades but weak ability to apply what you learned in new contexts.
• Being 'ashamed that what you're doing is childish' and abandoning the probing, feedback-seeking pursuit of mastery that children do naturally—tell: you stop experimenting because it feels beneath an adult.

• ▸Ability in question: name the specific skill or capacity you're evaluating.
• ▸Current self-theory: is this fixed (height) or malleable (strength)? State which and why.
• ▸Performance goal I'm holding: write the prove-it version (e.g., get the A).
• ▸Learning-goal rewrite: restate it as a develop-it version (e.g., be able to speak the language).
• ▸Effort reframe: one sentence recasting hard work as the path to improvement.
• ▸Stretch target chosen: a task slightly beyond current ability that expands, not just affirms.
• ▸Setback protocol: what strategy will I try next instead of blaming my intelligence?
• ▸Transfer test: how will I check that I can apply this to a new, non-identical problem?

1. 1Define one specific domain and a single performance metric you want to raise; deliberate practice has one objective—to improve performance, not just to log hours.
2. 2Set a target slightly above your current level, then structure each session around straining to reach a bit higher rather than repeating what you can already do.
3. 3Isolate your weaknesses and aim practice ruthlessly at them—those who get better work on what they're bad at, not what they already do well.
4. 4Build in extreme repetition on the weak component: don't shoot ten free throws, shoot five hundred; repetition is a form of change.
5. 5Install a constant feedback loop—measure or get critique after each rep so you always know how you're doing and what to correct next.
6. 6Accept the session will be mentally and physically exhausting; treat the exhaustion as the signal it's working, not a reason to stop.
7. 7Reframe the domain as infinitely improvable (a mindset, not a fixed ceiling) and treat mastery as an asymptote you approach but never fully reach.
8. 8Repeat the whole cycle over long horizons—Ericsson frames this as a lifelong effort, roughly a decade of sustained work—sustained by grit: perseverance and passion for the long-term goal.

Ericsson contrasts two tennis players to make the point concrete. Someone who plays tennis once a week for years doing the same thing each time does not get any better, because repetition without new goals isn't deliberate practice. The player who improves instead changes their performance—setting new goals and straining to reach a bit higher each session. The basketball analogue Colvin and Pink cite is sharper still: greats don't shoot ten free throws at the end of team practice, they shoot five hundred, targeting the weak mechanic with critical feedback after each attempt. The work is repetitive, mentally demanding, and often unpleasant, which is exactly why so few people commit to it—and exactly why it separates masters from the merely good.

• If you finish a practice session feeling comfortable and unstrained, then you weren't doing deliberate practice—raise the target.
• If you're spending time on skills you're already good at, then redirect that time to your weakest component.
• If you can't tell how you performed after a rep, then stop and build a feedback mechanism before continuing.
• If you see your ability as fixed rather than infinitely improvable, then you'll quit at the plateau—reframe the ceiling first.
• If the goal is short-term and someone offers an 'if-then' reward to make you practice, then expect long-term interest to drain; keep the drive intrinsic.

• Logging hours instead of changing performance—the tell is a routine that feels the same each time and produces no measurable gain (the once-a-week tennis player).
• Practicing strengths because they feel good—the tell is you avoid the drills that expose you and gravitate to what you already do well.
• No feedback loop—the tell is you can't state what specifically improved or worsened after a session.
• Quitting when it hurts—the tell is you treat the mental and physical exhaustion as a stop signal rather than confirmation it's working.
• Treating mastery as fully attainable and getting discouraged—the tell is frustration that you never 'arrive'; mastery is an asymptote by design.

• ▸Domain & metric: the one skill and the number you're trying to move
• ▸Current level: honest baseline on that metric today
• ▸Stretch target: the 'bit higher' you'll strain toward this session
• ▸Weakness targeted: the specific weak component this session attacks
• ▸Repetition plan: exact count of reps (aim high, e.g. 500 not 10)
• ▸Feedback source: how you'll know how each rep went
• ▸Exhaustion check: note the point where it got hard—confirm you kept going
• ▸Grit reminder: the long-term goal (approx. 10-year horizon) this session serves

1. 1Separate the two goal types before you commit: goals you set for yourself devoted to attaining mastery are healthy; goals imposed by others (sales targets, quarterly returns, test scores) narrow focus and can induce unethical behavior. Frame your progress markers as the former.
2. 2Redefine your target as an asymptote, not a finish line. State the thing you want to get better and better at, then accept you approach it but never fully reach it — this keeps effort ongoing rather than terminating at a payoff.
3. 3Audit the task type. For algorithmic work (following a formula to its logical end) contingent rewards can help; for conceptual, right-brain work demanding flexible problem-solving and inventiveness, remove the 'if-then' reward so it doesn't blinker your wide-ranging thinking.
4. 4Engineer for flow — the state of optimal challenge open-source programmers reported reaching frequently. Match the difficulty of the next increment to your current skill so the activity itself carries you.
5. 5Detach the activity from external reward as your primary destination. The art-school study shows those least motivated by extrinsic rewards produced work later recognized as superior — so treat the joy of discovery and challenge of creation as their own return.
6. 6Build in autonomy over what you practice. Like Google's grouplets — small self-organized teams with almost no budget or authority — carve out self-directed effort that lets you pursue improvement without top-down direction.
7. 7Track the trend of your capability, not a one-time score. Because mastery is never fully attained, measure whether you are moving toward it over months and years, not whether you hit a single number.

The School of the Art Institute of Chicago study is the cleanest case. Researchers surveyed sophomores and juniors in the early 1960s on whether they were more intrinsically or extrinsically motivated, then a follow-up researcher tracked the same students into the early 1980s. The starkest finding, especially for men: the less evidence of extrinsic motivation during art school, the more professional success both a few years after graduation and nearly twenty years later. Painters and sculptors driven by the joy of discovery and the challenge of creation weathered the inevitable lean years of no money and no recognition — and kept getting better. The paradox: those least motivated to pursue extrinsic rewards eventually received them, producing art socially recognized as superior. Mastery advanced precisely because these artists treated the work as an approach toward better, not a means to a payoff.

• If a goal is self-set and aimed at getting better, keep it; if it's imposed and short-term with a big payoff on achievement, treat it as a warning-labeled hazard that narrows your view.
• If the task is algorithmic, an extrinsic reward may work; if it demands inventiveness or conceptual understanding, strip the contingent reward so you can see the periphery.
• If you complete a project and feel finished, redraw the target — mastery is an asymptote, so there should always be a next increment to approach.
• If you notice you're checking yourself to satisfy an outside client rather than creating, expect the Sawyer Effect: the work becomes 'work' rather than joy, and progress stalls.
• If the activity absorbs you so completely you work through the night without noticing time, you've hit flow — protect and repeat those conditions.

• Chasing an imposed, measurable target as the only destination — the tell is Sears-style behavior (overcharging, unnecessary repairs) or Enron/Ford Pinto shortcuts, where hitting the number crowds out the broader dimensions of the work.
• Treating mastery as attainable and quitting once a milestone is hit — the tell is a plateau you mistake for arrival, with no next increment defined.
• Bolting rewards onto inherently interesting or creative work — the tell is the joy draining out and output narrowing, because you've neglected autonomy, mastery, and purpose.
• Optimizing for recognition and remuneration early — the tell mirrors the art-school extrinsically motivated group: harder to weather lean times, and lower eventual success.
• Confusing algorithmic and conceptual work and applying the wrong incentive — the tell is that a reward that boosted routine output suddenly makes original solutions harder to find.

• ▸The thing that matters: name the capability you want to get better and better at
• ▸Asymptote statement: write why this can be approached but never fully attained
• ▸Task type: algorithmic or conceptual (and reward implication for each)
• ▸Self-set vs imposed: mark which goals here are yours and which are external
• ▸Next increment: the single harder challenge that matches your current skill (aim for flow)
• ▸Autonomy carve-out: the self-directed time/space you protect for this practice
• ▸Extrinsic detach check: what reward, if any, is contaminating the joy — and how you'll neutralize it
• ▸Trend note: are you moving toward or away from better over this period, with evidence

1. 1Classify the task before you choose a motivator. Ask: is this routine (climbing rung by rung up a ladder of instructions) or nonroutine (creative, conceptual, requires deep thinking)? The answer dictates everything downstream.
2. 2For routine work, if-then rewards won't hurt and may help—but attach three supports: give a rationale for why the task matters to the larger mission, acknowledge openly that the task is boring, and grant autonomy over how it gets done (state the outcome, not the method).
3. 3For nonroutine, creative work, stop using contingent 'if-then' rewards. They narrow focus, increase constraint, and degrade the quality of output even when technical execution holds steady. Instead build the environment.
4. 4Diagnose the actual performance problem before reaching for a carrot or a stick. When someone isn't producing, do the hard work of asking which of the three needs—competence, autonomy, relatedness—is being thwarted, rather than running over the problem with an incentive.
5. 5If rewards are necessary (they often are in workplaces), make them as non-salient as possible. The more you foreground the reward as the reason to act, the more demotivating it becomes.
6. 6Protect the third drive—intrinsic interest—because it is fragile and needs the right conditions to survive. Give people novelty, challenge, and the room to extend and exercise their capacities.
7. 7Measure output on the dimensions that matter for the task type: for creative work, track quality and durability (long-term motivation to continue), not just short-term throughput. A caffeine-like reward jolt can lift quantity briefly while quietly eroding the interest that sustains the work.

Amabile recruited twenty-three professional artists and had each randomly select ten commissioned and ten noncommissioned works of their own. A blind panel of accomplished artists and curators rated every piece on creativity and technical skill. The commissioned works—the ones done for an external reward—were rated significantly less creative, yet no different in technical quality. The artists themselves reported feeling significantly more constrained doing commissioned pieces. One artist explained the mechanism: 'when you are doing a piece for someone else it becomes more work than joy,' whereas working for himself brought 'the pure joy of creating.' The lesson for managing creative productivity: the contingent reward didn't damage skill, it damaged the creative quality that skill serves—and it did so by replacing joy with constraint.

• If the task is routine and uninteresting, then if-then rewards are acceptable—but only when paired with rationale, empathy, and autonomy over method.
• If the task requires more than climbing rung by rung up a ladder of instructions, then avoid contingent rewards and focus on the environment instead.
• If you're about to use a reward to motivate, then make it as non-salient as possible—salient rewards are the most demotivating.
• If someone isn't producing, then diagnose which need (competence, autonomy, relatedness) is thwarted before applying any incentive.
• If you need durable output over time, then don't buy short-term boosts with cash—the effect wears off and reduces longer-term motivation to continue the project.

• Assuming bigger rewards buy better performance. The tell: an over-incentivized group (like the 400-rupee, five-months'-pay participants) that lags behind both low- and medium-reward groups—higher incentives led to worse performance in eight of nine tasks.
• Treating people as parts in a machine—reward the good, punish the bad—and applying that Motivation 2.0 logic to sophisticated, nonroutine work. The tell: rising resistance and falling engagement as the work gets more complex.
• Using cash as the go-to lever for creative or interesting work. The tell: a short-term jolt followed by people spending significantly less time on the task than before they were ever paid—like Deci's Group A dropping below even their unpaid baseline.
• Running over the problem with a carrot or stick instead of diagnosing it. The tell: repeated incentive programs that never fix the underlying deficit in autonomy, competence, or relatedness.
• Grading only technical quality and throughput while ignoring creativity and durability. The tell: output that's technically fine but measurably less creative—and workers who report feeling constrained rather than absorbed.

• ▸Task description: state the specific output you need in one line.
• ▸Task type: mark routine (ladder of instructions) or nonroutine (creative/conceptual).
• ▸Interest level: is this inherently gratifying, boring, or mixed?
• ▸Reward decision: given type + interest, will a contingent reward help, hurt, or be neutral?
• ▸Rationale (routine only): the one-sentence reason this task serves the larger mission.
• ▸Empathy note (routine only): how you'll acknowledge the task is boring.
• ▸Autonomy grant: which method choices you're handing to the person.
• ▸Need diagnosis (if underperforming): which of competence/autonomy/relatedness is thwarted?
• ▸Success metric: for creative work, name the quality and durability measures, not just throughput.

1. 1Classify the task before you design incentives: if it's heuristic (no clear algorithm, requires novel solutions), route it toward intrinsic motivation; if it's algorithmic (a set path to follow), extrinsic rewards remain safe. McKinsey's split — 70% heuristic, 30% algorithmic — tells you most modern work now falls in the first bucket.
2. 2Set baseline rewards adequately and equitably first. Pay people well enough that money is off the table as a grievance; otherwise their focus goes to unfairness and anxiety, and you get little motivation of any kind.
3. 3Remove the 'if-then' contingency from creative work. Do not tie the creative task itself to a bonus or certificate; contingent rewards convert play into work (the Sawyer Effect) and send creativity 'toppling like dominoes.'
4. 4Engineer for the three innate needs from self-determination theory — competence, autonomy, relatedness. Diagnose which one is thwarted rather than 'running over the problem with a carrot or a stick.'
5. 5Protect the conditions for flow. Give people work that stretches their capacities toward novelty and challenge, since children (and adults) seek flow 'with the inevitability of a natural law' when left to their own devices.
6. 6Diagnose motivation drops as thwarted needs, not laziness. Before adding an incentive, do 'the hard work of diagnosing what the problem is' — a missing autonomy, a broken sense of competence, or weak relatedness.
7. 7When you must reward creative output, prefer non-contingent, unexpected acknowledgment after the fact over pre-announced 'do-this-get-that' prizes, which are the form that reliably damages intrinsic interest.

Lepper, Greene, and Nisbett watched a preschool classroom for several days and identified the children who chose to draw during free play — a clearly intrinsic, creative activity. They split them into groups; the 'expected-award' group was shown a Good Player certificate with a blue ribbon and the child's name, and told they'd get it for drawing. Contingent reward was applied to an activity the children already loved. The pattern this classic study demonstrated is the hidden cost of rewards: once you pay for play, you diminish the child's later free-choice interest in drawing. The same alchemy runs through Twain's fence: obligation and payment turn a task into 'work,' while removing them turns it back into 'play.' The lesson for a manager is direct — do not attach an if-then prize to the very creative act you want more of.

• If the task is heuristic/creative, then withhold contingent extrinsic rewards and build for autonomy, competence, and relatedness instead.
• If baseline pay is inadequate or inequitable, then fix compensation first — no motivational technique works until money is 'a threshold motivator' that's off the table.
• If a person or team stops producing, then diagnose which of the three needs is thwarted before reaching for a carrot or stick.
• If the reward is larger, then expect worse — not better — performance on tasks requiring creativity or concentration (Madurai: in eight of nine tasks, higher incentives led to worse performance).
• If you want an activity to persist over the long term, then avoid rewards that give only a short-term 'caffeine' boost at the cost of durable intrinsic interest.

• Applying algorithmic-task incentives to heuristic work. The tell: you offer a bonus for a creative deliverable and quality drops instead of rising — the 400-rupee 'super-incentivized' group faring worst of all.
• Assuming bigger money buys better creative output. The tell: your best-paid performers on novel problems 'lag behind' the modestly paid ones, exactly as Ariely's Madurai study found.
• Making an inherently enjoyable task contingent on reward. The tell: people who used to do the work for its own sake now do it only when the prize is present — the Sawyer Effect, play converted into work.
• Treating people as 'human resources' / 'two-by-fours' rather than partners who direct their own lives. The tell: employees jump ship for a $10-20k raise because the work itself offers no autonomy.
• Reaching for a carrot or stick without diagnosis. The tell: motivation keeps sagging because you're 'trying to run over the problem' instead of finding the thwarted need beneath it.

• ▸Task type: heuristic (novel/no set path) or algorithmic (fixed path)? — write which and why.
• ▸Baseline check: is pay adequate and equitable so money is off the table? Yes/No + gap.
• ▸Contingency scan: name every if-then reward currently tied to this creative task.
• ▸Sawyer risk: does any reward turn an already-enjoyed activity into obligation? Flag it.
• ▸Competence: what stretches ability toward novelty/challenge here? Name one thing.
• ▸Autonomy: where does the person direct their own method, time, or team? Name it.
• ▸Relatedness: what connects this work to people it serves or partners on it?
• ▸Flow conditions: is the challenge matched to skill so 'optimal experience' is possible? Yes/No.
• ▸Diagnosis-first note: if output is dropping, which of the three needs is thwarted?

1. 1Audit what your core aspirations actually orient toward: list the goals driving your daily choices and mark each as intrinsic (growth, contribution, relationships) or Type X validation (money, fame, beauty). The research links the Type X cluster to poorer psychological health.
2. 2Diagnose need-satisfaction across the three innate needs SDT names—competence, autonomy, relatedness—rather than reaching for a reward or punishment. When people aren't producing, Ryan's point is that a carrot or stick 'runs over the problem' instead of solving it.
3. 3Make rewards less salient. Deci concedes rewards are necessary in workplaces, 'but the less salient they are made, the better.' Pay people fairly and off the table, then stop using contingent 'if-then' incentives to drive the activity itself.
4. 4Protect intrinsic interest by giving genuine free choice. Deci's experiment shows the third drive is more fragile than biological and reward drives; it 'needed the right environment to survive,' so build in real autonomy (acting with choice), not independence or isolation.
5. 5Reorient toward the three nutrients of Type I behavior: autonomy (self-directed), mastery (getting better at something that matters), and purpose (connecting the quest to something larger). Well-being follows from purpose-driven, intrinsically oriented living, not from control.
6. 6Track the outcomes that define psychological well-being over time—self-esteem, interpersonal relationship quality, general well-being, and reduced anxiety/defensiveness—rather than short-term output spikes, which fade like a caffeine jolt.

In Deci's Soma puzzle study, Group A was paid $1 per configuration in the second session; Group B was never paid. During the secretly observed eight-minute free-choice period, the paid group's interest spiked—they spent over five minutes on the puzzle when cash was on the line. But in the third unpaid session, the paid group's free-choice play dropped below their first-session baseline, while the unpaid group held steady. Deci concluded, 'When money is used as an external reward for some activity, the subjects lose intrinsic interest for the activity.' The reward delivered a short-term boost but eroded the very interest that sustains engagement and, by extension, the intrinsically oriented living tied to well-being. This is the mechanism to avoid: paying for something people already find worthwhile crowds out the internal drive.

• If someone isn't producing, then diagnose which of competence, autonomy, or relatedness is thwarted before adding any reward or punishment.
• If you must use rewards, then make them as non-salient as possible—salient contingent rewards are 'most demotivating.'
• If core aspirations are drifting toward money, fame, or beauty, then treat it as a well-being risk, since Type X orientation predicts poorer psychological health.
• If you want durable performance and richer lives, then build environments for autonomy, mastery, and purpose rather than chasing 'if-then' motivators that always grow more expensive.
• If you're confusing autonomy with independence, then correct it—autonomy means acting with choice and is compatible with being happily interdependent.

• Running over the problem with a carrot or stick: the tell is reaching for rewards/punishment without ever diagnosing which psychological need is unmet.
• Making rewards salient: the tell is announcing pay-for-performance as the headline motivator, which produces the demotivating effect Deci found.
• Reading the short-term reward spike as success: the tell is that engagement drops below baseline once the incentive is removed, like caffeine wearing off.
• Pursuing Type X validations (money, fame, beauty) as core aspirations: the tell is higher public self-consciousness, defensiveness, and Type A patterns alongside lower well-being.
• Mistaking autonomy for go-it-alone independence: the tell is isolating people or removing support in the name of freedom, when autonomy actually coexists with connection and relatedness.

• ▸Core aspiration audit: list your top 3 driving goals; mark each intrinsic or Type X.
• ▸Competence check: where do you feel you're getting better at something that matters?
• ▸Autonomy check: where do you act with genuine choice vs. felt pressure/demand?
• ▸Relatedness check: which relationships feel connected vs. thwarted?
• ▸Reward salience: list current 'if-then' incentives and how visible each is.
• ▸Salience reduction plan: how will you make necessary rewards less prominent?
• ▸Purpose link: how does your main pursuit connect to something larger than yourself?
• ▸Well-being markers: current self-esteem, relationship quality, anxiety/defensiveness level.
• ▸Next environment change: one condition you'll alter to support the third drive.

1. 1Audit every extrinsic goal you currently impose on yourself or others (sales targets, quarterly returns, test scores) and separate them from self-set mastery goals; the passages warn that imposed, short-term, measurable goals with big payoffs carry the danger.
2. 2Attach a warning label to each imposed goal in the spirit of the business school professors: name the specific risks it invites—narrowed focus, unethical behavior, increased risk taking, decreased cooperation, decreased intrinsic motivation.
3. 3Redefine the destination as the activity itself—deepening learning, delighting customers, doing one's best—so there is no shortcut to it; when the reward is the work, the only route is the high road.
4. 4Extend your gaze past the near-term slice. For any decision, ask what it does over three months versus decades, and stop rewarding or punishing tiny near-term blips (the quarterly-earnings obsession) that pull attention off the long horizon.
5. 5Replace 'if-then' fines and bonuses where they'd crowd out conduct: the Haifa day-care fine shows a stick can increase the very behavior it targets by converting a moral obligation into a priced transaction.
6. 6Design for the flow conditions instead of the payoff: clear goals, immediate feedback, and a challenge a notch or two beyond current ability, so effort becomes its own reward and shortcut-seeking loses its point.
7. 7Monitor for the tells of myopia and cheating—overcharging, gamed numbers, skipped safety checks—and treat their appearance as a signal that the incentive, not the person, is misdesigned.

Sears imposed a sales quota on its auto repair staff. The narrowed focus on hitting that imposed, measurable target drove workers to overcharge customers and complete unnecessary repairs—the quickest route to the only destination that mattered. The failure was not bad people but a goal that made the disadvantaged party a customer rather than the worker's own standards. Contrast the intended fix: had the reward been the activity itself—doing honest, excellent repair work—there would be no shortcut, because acting unethically would only disadvantage yourself. The same pattern recurs in the passages: Enron's lofty revenue goals catalyzed collapse, and Ford's fixation on a certain car at a certain weight, price, and date led it to omit safety checks and ship the dangerous Pinto. Each shows an extrinsic, short-term goal restricting the view of the broader dimensions of behavior.

• If a goal is self-set and aimed at mastery, then treat it as generally healthy; if it's imposed by others and short-term/measurable with a big payoff, then apply the warning label and monitor closely.
• If achieving the target delivers a quick win or quick fix regardless of lasting consequences, then assume some people will take the low road and redesign before deploying.
• If you're considering a fine or punishment to stop a behavior, then remember the Haifa result—a stick can convert obligation into a transaction and produce more of the behavior, not less.
• If the task is complex or conceptual, then avoid tangible 'if-then' rewards, which blinker wide-ranging thinking and shorten the depth of thought.
• If the reward is the activity itself, then no shortcut exists, because the only person disadvantaged by cheating is yourself.

• Deploying 'if-then' rewards as an over-the-counter salve for any performance problem; the tell is a narrowing focus that produces overcharging, gamed earnings, or skipped safety checks.
• Assuming punishment simply reverses bad behavior; the tell is that late pickups or violations rise after a fine is introduced, as at the Haifa day-care centers.
• Letting quarterly earnings become an obsession—devoting resources and brainpower to making numbers come out right and guiding analysts—while the tell is that companies spending the most time on quarterly guidance deliver worse long-run results.
• Confusing a good short-term concentration (get out of the burning building) with fixating on an immediate reward in non-emergencies; the tell is performance that decays over time despite hitting near-term marks.
• Ignoring that goals and rewards aren't inherently corrupting and over-correcting by abandoning goals entirely; the tell is drift and lost focus, since goals do concentrate the mind.

• ▸Goal statement: write the exact target as imposed or set.
• ▸Source: mark self-set/mastery or imposed by others (quota, quarter, test).
• ▸Time horizon: state the payoff window—next 3 months vs. multi-year.
• ▸Destination check: is the reward the activity itself or a separate payoff?
• ▸Shortcut exposure: name the quickest low-road route a person might take here.
• ▸Who is disadvantaged: a competitor/customer, or only yourself?
• ▸Risk flags: check any of narrowed focus, unethical behavior, increased risk taking, decreased cooperation, decreased intrinsic motivation.
• ▸Flow conditions: are goals clear, feedback immediate, challenge a notch beyond ability?
• ▸Decision: deploy as-is, redesign toward mastery/activity reward, or drop.

1. 1Audit which of the four T's you currently control top-down: task (what work gets done), time (when and how long), technique (how it gets done), and team (whom people work with). Name each one honestly rather than assuming 'empowerment' language already grants it.
2. 2Grant technique first if you can only move one lever: let people handle inquiries or build products 'the way they choose,' as JetBlue and the homeshore call centers do, and remove physical monitoring where possible.
3. 3Carve out dedicated task autonomy on a schedule, not a whim. Copy Atlassian's move from one-day FedEx Days to '20 percent time'—a fixed, recurring block of self-directed work that survives after the sprint ends.
4. 4Practice autonomy-supportive management as Deci, Ryan, and Baard defined it: see issues from the employee's point of view, give meaningful feedback and information, provide ample choice over what to do and how, and encourage people to take on new projects.
5. 5Make any necessary rewards as non-salient as possible. Deci's rule: rewards are necessary in workplaces, but 'the less salient they are made, the better'—so avoid 'if-then' contingent framing that forces people to forfeit autonomy.
6. 6Before reaching for a carrot or stick when someone underperforms, do 'the hard work of diagnosing what the problem is' instead of running over it with an incentive.
7. 7Adopt McKnight's operating credo—'Hire good people, and leave them alone'—and expect that good people 'are going to want to do their jobs in their own way,' including 'experimental doodling.'

Atlassian's Mike Cannon-Brookes ran FedEx Days—24 hours of self-directed building—and found they worked but had an inherent weakness: 'You built something in twenty-four hours, but you didn't get any more time to work on it.' In spring 2008 he and cofounder Farquhar doubled down on autonomy, letting developers spend 20 percent of their time for six months on any project they wanted. His reasoning was that as a company grows, an engineer 'spends less time building the things he personally wants in the product,' so 20 percent time gives 'dedicated stack time—of their own direction' for innovation, features, plugins, and fixes the engineers themselves judge most important. This grants task autonomy on a recurring, protected schedule rather than a single burst. It mirrors 3M's older practice under McKnight, whose 'Hire good people, and leave them alone' credo was subversive for its time. The through-line: fixed, self-directed time on self-chosen tasks, not one-off events.

• If someone isn't producing, then diagnose the actual problem before applying any reward or punishment—rewards used to motivate 'are most demotivating.'
• If you must use rewards, then make them non-contingent and non-salient; avoid 'if-then' framing, which forces people to forfeit autonomy and drains enjoyment.
• If pay is below the baseline or inequitable versus peers, then fix compensation first—autonomy support won't offset it; motivation 'will crater' regardless of Type X or I.
• If you can grant autonomy over only one T, then start with technique and time by removing monitoring—as homeshoring does—since these are lowest-cost and draw a deeper talent pool.
• If a self-direction practice depends on a special event (like a one-day sprint), then convert it into a recurring, protected allocation so the work continues afterward.

• Relabeling control as 'empowerment' or 'flexibility'—the tell is that the language 'presumes that the organization' still owns the power it dispenses; it's Motivation 2.1, a patch, not autonomy.
• Using contingent 'if-then' rewards to boost effort—the tell is a short-term productivity bump followed by collapsing intrinsic interest, the Sawyer Effect turning play into work.
• Reaching for a carrot or stick when output drops—the tell is that no one has diagnosed the underlying problem; you're 'trying to run over the problem' instead of solving it.
• Making rewards prominent as motivators—the tell is that the more salient the reward, the more demotivating it becomes; people watch the prize instead of the work.
• Granting autonomy in a one-time burst—the tell is Atlassian's early flaw: people build something in 24 hours but get no ongoing time, so the innovation stalls.

• ▸Task — What work gets assigned top-down vs. self-chosen? Note one shift toward choice.
• ▸Time — Where is when/how-long dictated? Name a fixed self-directed block (e.g., 20% time).
• ▸Technique — Is 'how' prescribed or the employee's call? List monitoring you can remove.
• ▸Team — Can people influence whom they work with, or are teams imposed?
• ▸Reward salience — Which incentives are 'if-then' and prominent? Plan to make them less salient.
• ▸Pay baseline check — Is compensation adequate and equitable vs. peers? Yes/No + fix.
• ▸Manager behaviors — Do you see the employee's view, give real feedback/info, offer choice, encourage new projects?
• ▸Diagnosis-first note — For any underperformer, what's the actual problem (before any reward/punishment)?
• ▸Recurring vs. one-off — Which autonomy practices are events that should become protected, ongoing allocations?

1. 1Confirm baseline components are covered first: wages/salary, benefits, and the few perks that constitute core compensation—these are the threshold before any motivation work matters.
2. 2Audit internal fairness: line up each person against colleagues with equivalent responsibility and experience, and check that pay differences map to actual differences in job difficulty or contribution.
3. 3Audit external fairness: benchmark each role against others doing similar work in similar organizations (e.g., auditors with ten years' experience at comparable Fortune 200 firms).
4. 4Where a gap exists, close it—external unfairness in particular causes a 'largely irreversible motivation dip,' so treat it as urgent, not cosmetic.
5. 5Consider paying slightly above market average (the Akerlof/Yellen approach) to buy further attention and remove any lingering doubt about adequacy.
6. 6Once fairness and adequacy are set, deliberately make compensation less prominent—'get compensation right and then get it out of sight'—so people focus on the work itself.
7. 7Only after the baseline is healthy, layer in autonomy, mastery, and purpose; do not attempt intrinsic-motivation levers on an unfair pay base.

You and Fred sit in adjoining cubicles with roughly equal responsibility and experience. If Fred makes scads more money than you, internal fairness is violated and your motivation plummets—your focus shifts to the unfairness of your situation. Now suppose you're both auditors with ten years' experience at a Fortune 200 company and you discover similarly experienced auditors at other Fortune 200 firms earn double your salaries; external fairness is violated and both of you suffer a largely irreversible motivation dip. The fix is not paying everyone the same: if Fred has a harder job or contributes more, he deserves a richer deal, and studies show most people accept that because it's fair. Getting internal and external equity right isn't itself a motivator—it's how you avoid putting money back on the table as a de-motivator. Only once that's settled can urgency, significance, and autonomy actually move performance.

• If baseline rewards aren't adequate or equitable, then expect near-zero motivation—neither extrinsic predictability nor intrinsic engagement—so fix pay before anything else.
• If someone's pay is out of line with colleagues doing equivalent work, then treat it as an internal-fairness breach and correct it, because motivation craters regardless of whether the person leans Type X or Type I.
• If pay lags comparable roles at comparable organizations, then treat the resulting motivation dip as largely irreversible and act with urgency.
• If one person genuinely has a harder job or contributes more, then pay them more—unequal pay is fine and accepted when it's fair.
• If the baseline is already healthy and you want more focus on the work, then make compensation less prominent rather than adding more reward salience.

• Trying to motivate with 'if-then' bonuses while pay is unfair—the tell is that focus stays on the unfairness and anxiety of the situation, and motivation stays flat no matter what carrots you add.
• Treating fair pay as itself a motivator—the tell is expecting a raise to lift performance when its real job is only to take money off the table.
• Making salary, perks, and benefits highly prominent—the tell is that the more visible compensation becomes, the more it inhibits creativity and unravels performance ('that's when they're most demotivating').
• Assuming Type I people don't care about money and underpaying them—the tell is that even intrinsically motivated people's motivation craters when pay is inadequate or inequitable.
• Enforcing equal pay in the name of fairness—the tell is resentment from higher contributors, because true fairness rewards harder jobs and larger contributions differently.

• ▸Role / person: whose compensation you're evaluating
• ▸Baseline components present: confirm wages, benefits, and perks are all covered
• ▸Internal comparators: list colleagues with equivalent responsibility/experience and their pay
• ▸Internal fairness verdict: are pay differences justified by job difficulty or contribution? (yes/no + gap)
• ▸External comparators: similar roles at similar organizations and their pay
• ▸External fairness verdict: is pay in line with the market? (yes/no + gap)
• ▸Above-average consideration: are you paying slightly above market to secure focus? (yes/no)
• ▸Prominence check: is compensation low-profile enough for the person to forget it and focus on work?
• ▸Action + urgency: gap to close and whether it's urgent (external gaps = irreversible, act now)

1. 1Before starting a task, decide whether the task is heuristic (open-ended, creative, no clear path) or algorithmic (a known route to follow). Reserve any 'if-then' contingency for the algorithmic case only, because rewards narrow focus and dull the wide view heuristic work needs.
2. 2For a task with intrinsic interest, do not announce a reward in advance. The damage comes specifically from the prior contingency—'if you do this, then you'll get that'—which forces the person to forfeit autonomy and turns play into work.
3. 3If you want to acknowledge good work on an intrinsically interesting task, deliver it after the fact and unexpectedly ('now that you've finished, here's...'). Deci's and Lepper/Greene's results show unexpected rewards had little impact on intrinsic motivation; only expected, contingent ones did the harm.
4. 4Replace controlling rewards with informational feedback—praise and useful comments about the work itself, especially from a peer rather than a boss, which carries deeper meaning and stays motivating.
5. 5Watch the time horizon: expect any contingent reward to produce a short-term burst (the paid Group A spent 5+ minutes on the puzzle when pay was live) followed by a longer-term drop (they later spent a full minute less than at first, unpaid, exposure). Judge the tactic by the long-term line, not the spike.
6. 6When paying is unavoidable (algorithmic, dull tasks), make the contingency explicit and don't pretend it builds love for the work; it buys compliance, not interest.
7. 7Run a periodic check of where you're attaching money or prizes to tasks people already enjoy, and unhook them—those are the exact spots draining intrinsic motivation.

Deci's Soma puzzle study is the cleanest demonstration. Across three days he watched two groups during a secretly observed eight-minute free-choice period. On day one both groups played with the puzzle for roughly three-and-a-half to four minutes, so both found it interesting. On day two he paid Group A for each configuration and left Group B unpaid; the paid group's engagement jumped to over five minutes while the unpaid group stayed the same. On day three he told Group A the money had run out—and now, working unpaid, they spent significantly less time on the puzzle, about two minutes less than their paid session and a full minute less than their very first, unpaid exposure. The contingent cash bought a short-term spike and then reduced the underlying interest that had been there all along.

• If the task is heuristic or creative (like the candle problem), then use no contingent reward—rewards narrow focus and block seeing new uses for old objects.
• If the person already finds the task gratifying, then withhold any prior 'if-then' offer; a reward here can drain the activity of its enjoyment.
• If you want to recognize completed work, then make it a 'now that' surprise plus specific feedback, not a promised prize.
• If you're measuring the tactic's success, then look at behavior weeks later (Lepper/Greene saw the drop two weeks on), not the immediate output.
• If a whole institution defaults to controlling behavior for short-term output, then assume long-term damage to motivation and creativity is accumulating.

• Reading the short-term spike as proof rewards work—the tell is impressive immediate output (paid kids drawing, industrial designer 'working like a maniac') followed by declining interest later.
• Attaching pay to something intrinsically loved, like paying a kid per workbook page—she gets diligent now and loses interest in math long term.
• Assuming higher incentive always means higher performance; the LSE analysis of 51 pay-for-performance plans and Ariely's India study found large incentives can produce a negative impact and be 'a losing proposition.'
• Using contingent rewards on creative work and mistaking the constraint for quality control—commissioned artworks rated significantly less creative (though equal in technical skill), with artists reporting they felt more constrained.
• Blaming the reward itself rather than its contingent, expected form—the tell is that unexpected rewards did little harm, so the problem is the prior 'if-then' promise, not the money.

• ▸Task type: heuristic/creative or algorithmic/routine? (one word)
• ▸Existing interest level: does the person already enjoy this? (yes/no)
• ▸Reward timing: is it promised before, or given after unexpectedly? (before/after)
• ▸Contingency wording: write the exact offer—flag any 'if you do X, then Y'
• ▸Autonomy cost: does this remove the person's control over how they work? (yes/no)
• ▸Short-term goal vs long-term motivation: which matters more here? (pick one)
• ▸Substitute plan: what informational feedback or peer praise replaces the reward?
• ▸Follow-up check date: when will you re-observe interest (e.g., two weeks out)?

1. 1Classify the task before you choose a motivator. Ask: does a set path exist that produces one right answer (algorithmic/routine), or must the person experiment and devise a novel solution (heuristic/nonroutine)? Grocery checkout is algorithmic; creating an ad campaign or poster is heuristic.
2. 2For routine, algorithmic tasks, apply carrots and sticks openly — external rewards and punishments 'work nicely' here and direction is appropriate.
3. 3For nonroutine, heuristic tasks, remove controlling 'if-then' rewards entirely. Never announce 'if you produce X, then you get a bonus' before creative work; it squashes conceptual, breakthrough thinking.
4. 4Establish baseline conditions first: make basic compensation adequate and fair relative to people doing similar work at similar organizations, make the workplace congenial, and give the team autonomy, mastery opportunities, and purpose.
5. 5If you reward creative work at all, use only unexpected 'now that' rewards given after the task is finished, so the reward isn't experienced as the reason for doing the work.
6. 6Prefer nontangible rewards — praise and positive feedback are far less corrosive than cash and trophies and can actually enhance intrinsic motivation.
7. 7Deliver rewards as information, not control: make feedback specific ('great use of color') and about effort and strategy, not a tacit effort to manipulate ('you did it exactly the way I asked').
8. 8Watch the entitlement drift: audit whether repeated 'now that' bonuses have hardened into expected 'if-then' entitlements, which crater performance.

Your nonprofit needs an inspiring poster to draw a crowd for its next event. Creating the poster is nonroutine — it requires conceptual, breakthrough, artistic thinking — so you do NOT stride in and say 'If you come up with a poster that rocks my world or boosts attendance, you'll get a ten-percent bonus,' because that 'if-then' offer is a recipe for reduced performance. Instead you have already established a motivating environment: fair baseline pay compared to similar organizations, a congenial workplace, and autonomy, mastery, and purpose for the team. When the poster turns out great, you may hand them an unexpected case of beer or cash bonus — a 'now that' reward they didn't expect and that didn't hinge on a specific outcome. Better still, you walk into their office and say, 'Wow, you did an amazing job on that poster — it's going to have a huge impact on getting people to come.' You focus feedback on specifics like great use of color and on effort and strategy rather than manipulation. This mirrors Amabile's commissioned-art finding: artists rated their commissions 'constraining' unless the commission felt 'enabling,' at which point creativity scores shot back up.

• If the task follows a set of established instructions down a single pathway to one right answer, then use direction and open incentives; if no algorithm exists and a novel solution is required, then use self-direction and drop controlling rewards.
• If work is heuristic and you must reward, then only reward unexpectedly and after completion ('now that'), never conditionally and before ('if-then').
• If you're choosing a reward for creative work, then prefer praise and positive feedback over cash and trophies.
• If feedback risks reading as manipulation ('you did it exactly the way I asked'), then replace it with specific, informational praise about effort and strategy.
• If a person says 'I need you to motivate me' for nonroutine work, then the fit is wrong — as one leader put it, 'If you need me to motivate you, I probably don't want to hire you.'

• Treating all white-collar work as routine and defaulting to carrots-and-sticks. Tell: you're scripting bonuses for jobs that actually require experimentation and novel solutions, and creativity flatlines.
• Offering 'if-then' rewards on inherently interesting tasks. Tell: performance and intrinsic motivation drop instead of rising — the mechanism designed to increase motivation dampens it.
• Letting unexpected 'now that' bonuses become routine. Tell: the team now expects the bonus and treats it as an entitlement, which craters performance.
• Giving controlling feedback disguised as praise ('perfect, exactly as I asked'). Tell: the artist reports feeling 'constrained,' checking themselves to please the client instead of creating.
• Skipping the baseline — expecting rewards to compensate for unfair pay or an uncongenial workplace. Tell: below the fairness threshold you get very little motivation at all, no matter how you incentivize.

• ▸Task described: state the specific task in one sentence
• ▸Algorithmic or heuristic: does one right-answer pathway exist, or must you devise a novel solution?
• ▸Baseline check: is pay adequate and fair vs. similar work at similar organizations? (yes/no)
• ▸Autonomy/mastery/purpose present: yes/no — if no, fix before rewarding
• ▸Reward timing: 'if-then' (before) or 'now that' (after, unexpected)?
• ▸Reward type: tangible cash/trophy or nontangible praise/feedback?
• ▸Feedback content: specific effort/strategy praise, or controlling 'as I asked' language?
• ▸Entitlement audit: has a past 'now that' bonus become an expected 'if-then'? (yes/no)
• ▸Decision: direct-and-incentivize (routine) or self-direct-and-enable (nonroutine)

1. 1Rewrite your organizational goal so profit is a byproduct, not the aim: state the larger social benefit first, then note the venture 'hopes to make money.' The North Carolina L3C states its real purpose as revitalizing a struggling region while still generating modest profits.
2. 2Replace input-based metrics that pull attention to self-interest (the billable hour, hours logged) with output metrics tied to the mission. When rewards come from time, time is what you get; when they come from solving the client's problem, purpose stays visible.
3. 3Codify purpose in structure, not just posters: amend bylaws (B Corporation) so incentives favor long-term value and social impact over short-term economic gain, so the mission survives leadership turnover.
4. 4Adopt purpose-oriented language deliberately. Swap the 'profit-maximization principle' for the 'social-benefit principle' (Yunus) in how you describe products, capital-raising, and market activity.
5. 5Recruit the mission by making the work itself the draw. Wikipedia and Firefox mobilize unpaid contributors because participation connects to something larger than a paycheck; design roles so people can choose work close to the content.
6. 6Audit whether your reward system is quietly teaching short-term, self-focused thinking. If-then incentives narrow both the breadth and depth of thinking; strip them from nonroutine, purpose-driven work.
7. 7Give people autonomy over what they take on so they can stay close to content they find meaningful — closeness to content is what makes research easy and meetings interesting.

Muhammad Yunus built 'social businesses' that raise capital, develop products, and sell them in an open market — the ordinary machinery of commerce. The single change is the operating principle: he replaces the 'profit-maximization principle' with the 'social-benefit principle.' The company still must be economically self-sustaining, so it is not charity; it just orients every goal toward a larger mission. Compare the L3C in North Carolina: it buys abandoned furniture factories, updates them with green technology, and leases them back to struggling manufacturers at a low rate. It 'hopes to make money,' but its 'real purpose is to help revitalize a struggling region.' The purpose is not a slogan bolted onto a normal business — it is written into the entity type (L3C, B Corporation, for-benefit) so incentives and bylaws point at social impact rather than short-term gain. That structural encoding is what makes the purpose connection durable rather than decorative.

• If a task is nonroutine and mission-driven, then reward the output (the problem solved), not the input (hours billed) — the link between time in and value out is irregular and unpredictable.
• If you want the mission to survive after you leave, then encode it in bylaws or entity type (B Corp, L3C, for-benefit), because language alone reverts to profit-maximization under pressure.
• If you need contributors you can't fully pay, then connect the work to something larger than themselves — open-source (Wikipedia, Firefox) shows people will contribute for free when purpose is present.
• If an if-then reward is present on purpose work, then remove it — such incentives narrow thinking and pull focus onto immediate self-interest.
• If people are close to the content and can choose their work, then keep it that way — proximity to meaningful content is the strongest driver of engagement.

• Declaring purpose in the mission statement while keeping profit-maximization as the actual operating principle — the tell is that every real decision defaults to short-term economic gain.
• Retaining input metrics like the billable hour on purpose work — the tell is people optimizing for logged hours and even exaggerating them (Rehnquist's warning about temptation to inflate).
• Bolting a social cause onto a company without structural encoding — the tell is the purpose evaporating the moment leadership or market conditions change, because nothing in the bylaws protects it.
• Trying to buy purpose with if-then rewards — the tell is narrowed, shallower thinking and worse decisions, since anticipation of reward pushes people toward short-term, self-focused choices.
• Assuming a for-benefit or social business can run on goodwill and lose money — the tell is insolvency; these entities must remain 'economically self-sustaining,' not charities.

• ▸Larger mission (one sentence): the cause beyond profit this work serves
• ▸Operating principle: state whether profit-maximization or social-benefit governs decisions
• ▸Structural encoding: entity type or bylaw change that locks in the mission (L3C, B Corp, for-benefit, or 'none — vulnerable')
• ▸Purpose language audit: three phrases your policies use that name the mission, not the money
• ▸Metric swap: the input metric to remove and the output/mission metric that replaces it
• ▸If-then reward check: list any tangible reward on this work that narrows or shortens thinking
• ▸Contributor draw: why someone would do this work for reasons larger than pay
• ▸Content proximity: how you let people choose work close to content they find meaningful
• ▸Self-sustaining test: how the venture stays economically viable while serving the mission