The CliftonStrengths domains told you how a teammate tends to behave. The motivation map tells you why they show up at all. Two engineers with nearly identical CliftonStrengths profiles can be moved by completely different things: one by the chance to go deep on a hard system, another by the feeling that her work matters to someone outside the building. If you don't know which is which, you'll reach for the same lever for both, and one of them will quietly disengage. This unit builds the lens for that.

Most of what we call "motivation" runs on two very different engines. Extrinsic motivation comes from outside the work: the bonus, the title bump, the public callout, the deadline pressure. Intrinsic motivation comes from inside the work itself: the satisfaction of getting good at something hard, the autonomy of figuring out your own path, the sense that the work connects to something you care about.

Both engines work. The difference is what they do over time. Extrinsic levers are fast, predictable, and shallow. They reliably move behavior in the short term, but they rarely deepen commitment, and they have a quiet side effect researchers call the overjustification effect: when you pay someone to do something they already loved doing, their intrinsic interest tends to erode. The activity becomes the price of the reward. Intrinsic motivation is slower to build and harder to engineer, but it's the only engine that survives a bad quarter, a reorg, or the moment your bonus pool gets cut.

The coaching move isn't to pick one. It's to know which engine you're pulling on with each decision. A spot bonus for a one-time push during a launch crunch is fine. A spot bonus repeated quarterly for the team's core craft will train your team to stop doing the work without it. Use extrinsic levers like adrenaline shots: occasional, targeted, and not the thing your team runs on day to day.

Here's where well-intentioned managers do the most damage. Most of the tactics that crush intrinsic motivation feel like good management in the moment. The artificial deadline you set "to create urgency" on a creative scoping task. The leaderboard you posted in the team channel "to celebrate wins." The time you rewrote a teammate's deck the night before a client meeting "to help." Each one carries a hidden message: that the goal isn't the work, it's the metric; that recognition is a competition; that you don't trust them to handle the thing they own.

The mechanism matters. Public rankings turn collaborators into competitors and trigger threat response in the people not at the top. Tight deadlines on exploratory work tell your team that thinking carefully is a luxury you don't actually fund. Rewriting someone's deliverable, even with good intent, says "I don't trust your judgment" louder than any feedback ever could. None of these tactics are inherently wrong, but each one taxes intrinsic motivation, and the tax compounds.

• Jake: I offered a $500 bonus for whoever shipped the bug-bash list first. Got one of them done in a day.
• Nova: And the other four?
• Jake: Slower than usual, honestly. And the person who won has been asking what's next on bonuses.
• Nova: So you bought one ticket and charged the team's intrinsic motivation for it. What was the work itself supposed to feel like before the bonus?
• Jake: Ownership. They picked the bugs.
• Nova: And now it feels like piecework. That's the trade you made, even if you didn't mean to.

Notice that Nova doesn't tell Jake bonuses are bad. She makes him price the trade.

The corrective isn't to guess what motivates each teammate; it's to hypothesize and test. A working motivation map is a one-pager with three columns per direct report. First, a specific hypothesis about what intrinsically drives them, anchored in autonomy (control over the how), mastery (getting deeply good at something), purpose (impact that matters to them), or a more personal driver like teaching others, building from scratch, or owning a customer relationship. Second, the behavioral evidence for that hypothesis: the moments they leaned in, the projects they volunteered for, the kind of feedback that visibly landed. Third, the experiment you'll run in your next 1:1 to test it: a different framing of work, a question you haven't asked before, a small expansion of decision rights.

Treat each row as a falsifiable claim. If you've written "Ryan is motivated by mastery" and you can't point to two pieces of evidence, name the evidence gap and design the experiment to surface it. The point of the document is to drive different questions in your next round of 1:1s, not sit pretty in a Notion doc.

The single takeaway: intrinsic motivation is the engine you want, extrinsic levers tax it more often than they help, and the only honest way to know what drives each teammate is to write down a testable guess and run the experiment.

Two short reps and a build sit ahead of you. First, a quick judgment check on whether common management moves tap intrinsic or extrinsic motivation, and what each does to engagement over a quarter. Then a written tactic audit on your own recent quarter, the kind your skip-level might actually ask for. Finally, you'll draft the motivation map itself, one row per direct report, with the hypothesis, the evidence, and the experiment you'll run in your next 1:1. The map only earns its keep when every row drives a real question in a real conversation.