Multipliers

1. 1Assign ownership for the whole result, not a task. Name the person who owns the outcome and state plainly that they own it end-to-end, then stop holding it yourself.
2. 2Invest before you extract: teach and coach the person so they build capacity, rather than solving it for them. When someone hits a wall, ask questions that shape their thinking instead of taking the pen.
3. 3When the team is stuck and looks to you for the answer, resist rescuing. Hand the problem back with the resources and framing they need to solve it themselves.
4. 4Provide the necessary resources for success—time, data, access, coaching—so the person is genuinely equipped, not set up to fail.
5. 5Set high expectations explicitly and state the standard people are accountable to, so the bar is unrelenting even when you leave the room.
6. 6Hold people accountable to their commitments: follow up on what they said they would deliver, and let them carry the consequences and the credit.
7. 7Return ownership after you intervene. If you must step in, give the pen back so the person keeps accountability for the final result.

At the McKinsey office in Seoul, a project team led by Hyunjee works past midnight, two days from a critical client presentation. Partner Jae Choi joins to guide, challenge, and shape their thinking as they retest the story line against new facts. It becomes clear the team is stuck, and Hyunjee gives Jae the desperate look that signals 'I could use a little help here.' Jae has been on countless projects like this and could easily take the whiteboard and solve it. An Investor does not rescue; he asks questions, keeps the pen in Hyunjee's hand, and returns ownership so the team produces the result and carries the accountability. The exhaustion is real, but so is the capability built—people describe working with such leaders as an intense but exhilarating workout that gets things from them they didn't know they had to give.

• If the team looks to you for the answer, then hand the problem back with framing and data rather than solving it—keep the pen with the owner.
• If you must jump in to unblock a situation, then give ownership back immediately so accountability stays with the person, not you.
• If someone lacks what they need to succeed, then invest the resource (coaching, data, access) before you expect the result.
• If a commitment is missed, then hold the person accountable to it directly rather than absorbing the work yourself.
• If you find yourself managing for results through your personal involvement, then you have slipped into Micromanager—reassign ownership.

• Rescuing when the team gets stuck: you take the whiteboard and solve it, and the tell is relief in the room plus a leader doing the work at midnight.
• Assigning tasks instead of ownership: people execute pieces but no one owns the outcome, and the tell is everyone pointing to you when it fails.
• Investing without accountability—coaching people but never following up on commitments, so high expectations quietly erode; the tell is missed commitments with no consequence.
• Going soft: mistaking Investor for a nice-guy, feel-good style; the tell is comfort without stretch and people who feel liked but underutilized.
• Intervening and keeping the pen: you step in to help but never return ownership, becoming a Micromanager driving results through personal involvement; the tell is that nothing finishes without you.

• ▸Result owned: name the single person accountable for the whole outcome.
• ▸The result (not the task): state the end result they own end-to-end.
• ▸Standard/expectation: write the high bar they are accountable to.
• ▸Investment made: list coaching, teaching, or resources you provided.
• ▸Resources needed: note data, access, or time still required for success.
• ▸Intervention rule: define when you may step in and how you return the pen.
• ▸Accountability checkpoint: name the commitment and date you will follow up on.
• ▸Ownership returned? yes/no—confirm the person carries the final result and credit.

1. 1Operate with consistency: hold the same demeanor across good news and bad. Like the jump-rope image, your steady rhythm tells people when they can jump in and contribute. Erratic reactions make them wait, hesitate, or never enter.
2. 2Contain stress instead of flowing it outward. When the environment panics—as SAP did in the 2008 meltdown—absorb the tension rather than transmit it, so people can focus on the real issue instead of managing your mood.
3. 3Disarm the hierarchy. Present yourself as a peer, stay accessible three levels down, and signal 'I want to know what you think.' This makes people transparent instead of telling you what you want to hear.
4. 4Level the playing field: identify whose voices are inherently advantaged (senior execs, product/sales, legacy-knowledge holders) and deliberately amplify the muffled voices closest to the real issues.
5. 5When someone raises a hard truth, run a learning process instead of judging. Restrain the authoritarian reflex, ask 'How can we take this to the next level?', and create space for the team to fix the problem themselves.
6. 6Use self-deprecating humor to put people at ease—don't take yourself or the situation too seriously, so people can be themselves and see error as recoverable, not fatal.
7. 7Signal that recovery beats placation. Say the equivalent of 'Ignore me as needed to get your job done'—make clear you'd rather people trust their judgment and keep moving than wait for your approval.
8. 8Remove blockers, including yourself. If a prima donna—or you, the banyan tree—is shading out others' growth, get out of the way so people get the sun to grow.

When Robert Enslin took over SAP's Japanese subsidiary to fix sales performance, his first forecast meeting revealed a process in complete disarray. The authoritarian path was to judge the failure and dictate a solution. Instead, Robert restrained himself and started a learning process—helping the team see the current process's limits and the new approach's advantages, then drawing on their knowledge of the Japanese business by asking, 'How can we take this to the next level?' He created space for them to try new approaches and fix the problem themselves, staying on the issue for months until they could run a forecast that delivered predictable results. His accessibility—being 'a commoner, one of us'—made people transparent rather than fearful, which is how he ran a massive organization 'with no surprises.' Contrast Jenna, who berated Daniel for ten minutes when he raised IT-utilization data: the next presenters watered down anything controversial, nothing much was said, and the organization kept missing its targets.

• If you feel the pull to be tyrannical because you can, then restrain it and run a learning process—intimidation and fear rarely produce great work.
• If a follower raises an uncomfortable truth (like Daniel's IT data), then ask a curious question instead of snapping—the response you give sets the safety level for everyone still to present.
• If certain voices are structurally advantaged, then deliberately amplify the lower-end voices, because they are often closest to the real issues.
• If the environment is panicking, then contain the stress rather than flowing it out, so people stay focused on delivering value.
• If you're the blocker shading others' growth, then get out of the way—signal 'ignore me as needed to get your job done.'

• Believing pressure increases performance: you demand best thinking but get only the safest ideas, because best thinking must be given, not taken. Tell: you pay full price for people but get about 50 percent of their value.
• Being inconsistent/erratic: people can't predict when it's safe to jump in, so they wait or never contribute. Tell: meetings go quiet and people scramble to strip anything controversial.
• The Jenna trap—judging and berating in front of the group. Tell: a rapid dash for the door at break, presenters watering down their slides, and a 'chill in the hall.'
• The Accidental Diminisher: you think you're open-minded and creative, but your strong ideas and drive for results kill others' thinking. Tell: a 360 comment like 'it is just easier to hold back and let Kate do the thinking.'
• Being a banyan tree: you protect and shade your people so nothing grows under you. Tell: comfort without stretch, and talent that stays but never develops.

• ▸Consistency check: name one recent situation where your reaction was erratic and what it cost.
• ▸Stress containment: what tension am I flowing outward that I should absorb this week?
• ▸Disarm move: one concrete way I made myself a peer/accessible to someone below me.
• ▸Muffled voice: whose voice is closest to the real issue but structurally disadvantaged—and how will I amplify it?
• ▸Learning-process substitute: which judgment did I hold back, and what 'how can we take this to the next level?' question did I ask instead?
• ▸Recovery signal: how did I show a mistake was recoverable rather than fatal?
• ▸Blocker check: who (including me) is shading others' growth, and what's my get-out-of-the-way move?
• ▸Intensity balance: where did I demand best effort while keeping the space comfortable enough to give it?
• ▸Tell-watch: what evidence (silence, watered-down work, held-back ideas) suggests fear crept in?

1. 1Observe each person in action and locate their native genius: what they do better than anything else, better than peers, without effort, without being asked, and without needing to be paid.
2. 2Name the genius out loud to the person, ideally publicly, so they become aware of a capability they treat as ordinary (fish discover water last) and can start deliberately using it.
3. 3Assign roles that use those talents against the real work, and in one-on-ones ask the stretch questions: 'What is the next challenge for you? What would be a stretch assignment?'
4. 4Hand over full ownership when you delegate — make the person responsible for implementing outcomes, not just attending and reporting back; position yourself as sounding board, not the decision maker.
5. 5Ask about blockers, not just status: 'What is getting in the way of your being successful?' Then flow that problem back to them to solve rather than taking it back.
6. 6Build a safe environment where boldest (not safest) ideas can be offered, since best thinking must be given voluntarily, not taken — pressure only yields the safe ideas the leader already agrees with.
7. 7Stop bungeeing in and out on high-visibility items only; give equal presence to the less visible backbone projects so people don't learn dependency and disengagement.
8. 8Create conditions where the best work is deeply needed by the environment itself, so the person freely bestows discretionary effort.

You lead a division and must send someone to a cross-functional task force. In the Diminisher version, you send Jyanthi as your representative, tell her to report back so you can weigh in, and warn her not to give the wrong impression — so she attends many meetings, contributes little, avoids controversy, and several decisions land against your division while the task force leader notes 'the lack of engagement from your division.' In the Multiplier version, you tell her she was chosen for her market understanding and ability to assimilate data, that she represents the entire division and is fully responsible for implementing outcomes, and that the task force is her project with you available only as a sounding board. You recommend she come armed with data to weigh in live during debates. The result: she engages fully, gains new understanding of the competitive landscape, advocates for programs that benefit your division, and impresses the task force leader who thinks 'this group has great talent.' The difference is ownership and the assumption that people are smart and can figure it out.

• If you assume only a few people are worth listening to, you will hire the star's favorite and decide privately — instead, assume 'with enough minds we can figure it out' and pursue every relevant insight.
• If a person hands you their problem, then flow it back and keep it there; your job is to manage the work, not do the work.
• If you only show up when the CEO is watching, stop — presence tied to visibility creates dependency and disengagement on the equally critical low-visibility work.
• If the environment feels tense or unsafe, expect only the safest ideas the leader already agrees with; if you want boldest ideas, they must be given voluntarily, so build safety first.
• If someone does something easily, freely, and without being asked or paid, that is their native genius — name it publicly to unlock discretionary effort.

• Elitist view of intelligence: running inclusive-looking meetings while making high-stakes calls privately with one or two advisors — tell: 'open-door policy' but lots of closed-door meetings, and empty chairs when you next call a meeting.
• Bungee bossing: springing in when senior management notices, then springing back out — tell: your team can't get your attention on critical-but-invisible projects.
• Taking problems back as an overzealous superhero — tell: you're the last one in a dark office wondering why delegated work keeps returning to you.
• Delegating attendance instead of ownership — tell: your representative attends everything but contributes nothing and steers clear of controversy.
• Know-It-All directives that showcase your knowledge — tell: idle cycles as people wait to be told what to do, and an organization that won't get ahead of the boss.

• ▸Person: name of the individual you're developing.
• ▸Native genius observed: what they do better than anything, effortlessly, unpaid, unasked.
• ▸Where I named it: when/how you told them (publicly preferred) to raise their awareness.
• ▸Stretch assignment: the next challenge that goes beyond what they currently know how to do.
• ▸Ownership statement: the sentence transferring full responsibility for implementing the outcome.
• ▸Blocker question asked: 'What is getting in the way of your being successful?' — and their answer.
• ▸Problem flowed back: the issue you refused to take back and returned for them to solve.
• ▸Safety check: one thing you did to make bold (not safe) ideas offerable here.
• ▸Presence check: how you showed up on their low-visibility work, not just the CEO-visible work.

1. 1Set a challenge above the person's current proven level, then say the words that transfer belief: state your confidence explicitly and name the specific reason you believe they can do it (as the organization president told a 20-year-old, 'I have great confidence in you. You can do this.').
2. 2Cap your own airtime. In meetings speak roughly 10 percent of the time, and use it only to 'crisp up' the problem statement, not to supply the answer — George Schneer's ratio, versus Manager #2's 30 percent of talk that killed ideas.
3. 3After framing the problem, physically and verbally back away to create space; give the person room to generate the answer rather than announcing your own.
4. 4Fully utilize the capability you already have before adding headcount: assume the person is underutilized and assign work that draws more from them than their present job requires.
5. 5Provide the materials and support that make the stretch achievable ('I will give you the materials to help you prepare'), so the challenge lands as demanding-but-possible rather than abandonment.
6. 6Measure growth over repeated cycles: track whether the person now solves harder problems, adapts faster, and takes more intelligent action — the signs they became smarter, not just felt smarter.
7. 7Reinvest the excess capability. Once someone gives beyond 100 percent, raise the next challenge so the 5–10 percent growth bonus compounds instead of plateauing.

Vikram worked as an engineering manager at Intel under George Schneer, a division manager. George grew Vikram's intelligence by engaging it rather than displaying his own — he wasn't the center of attention and didn't worry about how smart he looked. In a typical meeting he spoke only about 10 percent of the time, mostly to sharpen the problem statement, then backed away and gave the team space to figure out the answer. The ideas the team generated were often worth millions, and the group drove the revenue growth and profit bridge that let Intel enter the microprocessor business. Vikram's own account marks the capability jump: 'I was a rock star around George. He made me. Because of him I transitioned from an individual contributor to big-time manager... He got 100 percent from me — it was exhilarating.' The contrast came under Manager #2, a brilliant scientist who did all the thinking, did about 30 percent of the talking, and gave feedback mostly about how bad ideas were — people shut down and eventually quit. Same company, same role, opposite growth trajectory.

• If you find yourself supplying the answer, then stop and hand back the problem — your job is to crisp the question, not close it.
• If someone is meeting their current job's demands easily, then they are underutilized; assign a challenge above their proven level rather than assuming they've maxed out.
• If a new demand arrives, then ask 'who already here can be stretched into this?' before asking for more headcount — practice the logic of multiplication, not addition.
• If you're about to give feedback, then check whether it opens thinking (engages intelligence) or forecloses it (kills the idea like Manager #2).
• If the person doubts they can do it, then transfer confidence explicitly and provide preparation materials — belief plus support turns doubt into stretch.

• Being the smartest person in the room: you do all the thinking and announce decisions to the organization. Tell — you have a strong opinion for everything and people stop offering theirs.
• Feedback as idea-killing: giving lots of feedback that is mostly about how bad the ideas are. Tell — people 'shut down' around you and start quitting or threatening to.
• Dominating airtime: talking 30 percent or more and selling your ideas to get execution on details. Tell — no one else's opinion seems to matter in the meeting.
• Defaulting to the logic of addition: insisting more revenue requires more headcount (the sales executive's linear model). Tell — you can't hit targets without expanding the team.
• Confusing 'feels smarter' with 'is smarter': settling for morale without growth. Tell — no evidence the person now solves harder problems, adapts faster, or takes more intelligent action.

• ▸Person & current proven level: where they already perform reliably today
• ▸Underutilization gap: capability their present job doesn't require
• ▸The stretch challenge: task set above proven level (what, by when)
• ▸Confidence statement: the explicit words + specific reason you believe they can do it
• ▸Support/materials provided: what you give so the stretch is achievable
• ▸My airtime cap: the ~10% I'll use only to crisp the problem statement
• ▸Space plan: how I back away and leave the answer to them
• ▸Growth evidence to track: which harder problem / faster adaptation proves they got smarter
• ▸Next reinvestment: how I raise the bar to compound the 5–10% growth bonus

1. 1When something goes off the rails, decide explicitly: take over or invest. Jump in to teach or share an idea only if you then 'give the pen back' so accountability returns to the person.
2. 2Set high, clear expectations for the outcome, not the method. Name the result you require and let people exercise their own judgment on how to get there (Deb Lange: 'Ignore me as needed to get your job done').
3. 3Provide the resources people need to succeed — this is the Investor's affirmative act, not just benevolence. Infuse others with resources plus ownership, then expect results in return.
4. 4Hold people accountable to their specific commitments. Return to accountability every time you intervene; ask for the commitment back so ownership stays with them.
5. 5When work is submitted below capacity, refuse to accept it and hand it back with a question rather than the fix (Kissinger: 'Is this your best work?'). Keep returning it until the person declares it is their best.
6. 6Give escalating ownership as people mature — start small, expand the scope as they prove capability (Elaben's chief executives each 'given greater and greater ownership as they matured').
7. 7Build for your own absence. Test whether the team can act intelligently and deliver without your direct presence; if it can't, you've built dependency, not accountability.

Barak Hershkovitz, CTO for Better Place, prepared for a critical meeting with a skeptical car maker and, hedging, created a compromise 'Plan B' he could fall back on. When he told Shai Agassi about it, Shai didn't take the pen — he asked questions: 'Do you believe in what you are doing?... Is it the right solution?... Is there a better solution?' Barak admitted Plan B was a weaker compromise. Shai said, 'Believe in what you do and stick with the truth. I'll back you up.' The ownership stayed with Barak, who then stood up and gave the speech for the original solution. Shai invested confidence and backing rather than rescuing Barak with his own answer, leaving Barak accountable for the outcome.

• If you jump in to teach or coach, then give the pen back so people know they are still in charge.
• If the person hands you work below their capability, then hand it back with 'Is this your best work?' instead of fixing it yourself.
• If you find yourself owning the details and driving results through personal involvement, then you're micromanaging — return ownership and hold them to the commitment instead.
• If a person has matured and proven capable, then expand their ownership; give greater scope so you can step away.
• If the team cannot deliver without your direct presence, then you have created dependency and must rebuild self-sufficiency before results will sustain.

• Taking the pen and never giving it back — you save the day and drive results yourself, creating an organization dependent on your rescue. Tell: people wait for you to jump in before acting.
• Being a 'feel-good' manager who lowers expectations to keep people comfortable. Tell: no one is stretched and results are merely adequate, not extraordinary.
• Providing ownership without resources (or resources without ownership) — investing incompletely. Tell: people are accountable but lack what they need, or well-resourced but not held to commitments.
• Managing method instead of outcome — dictating how, which suppresses judgment. Tell: staff placate the boss rather than trust their judgment and get the job done.
• Hoarding talent and resources like an Empire Builder, believing people must report to you to perform. Tell: your first instinct for a problem is 'it should report to me,' and people around you languish or regress.

• ▸Result required: the specific outcome and standard you expect (not the method)
• ▸Owner: the single person accountable for delivering it
• ▸Resources provided: what you're investing (time, access, budget, coaching) so they can succeed
• ▸My intervention limit: when I may jump in to teach — and the trigger for giving the pen back
• ▸Commitment captured: what the owner specifically committed to, in their words
• ▸'Best work' check: the question you'll ask if the work comes in below capacity
• ▸Independence test: what proves this can be delivered without my direct presence
• ▸Ownership escalation: the next larger scope this person earns once they prove capable

1. 1Reframe the request in the language of multiplication, not addition: when a bigger target lands, refuse the reflexive 'more output requires more headcount' equation and ask instead which existing capability is going unused.
2. 2Estimate current utilization honestly. The premise is that most people run well below capacity while feeling maxed out; separate feeling overworked from actually being fully leveraged. Target moving people toward 70-100 percent or more of real capability.
3. 3Gather the key players across job functions—not just the department under pressure—and dedicate concentrated time (Apple took a week) to study the problem before touching resources.
4. 4Redesign the model to route work to your deepest talent. Apple built competency centers to put best salespeople and deep industry experts into the sales cycle rather than spreading work thinly across added hires.
5. 5Hunt for and dismantle redundancy. Diminishers load up on resources and build duplicate infrastructure; audit for the office-tower equivalents and fold them back in.
6. 6Add the growth bonus: because people get smarter and more capable working for a Multiplier, expect a 5-10 percent compounding gain on top of the 2X. Design roles that stretch people so this actually accrues.
7. 7Measure real ROI before praising activity. Jasper looked productive until the true return calculation exposed the waste; force the honest number.

Tim Cook, COO of Apple, opened a budget review in one sales division and set the imperative as revenue growth—then asked for that growth with no additional headcount. The sales executive argued the target was attainable only by following the proven linear model of incremental headcount growth, insisting more revenue means more people. The two spoke past each other for months: the sales executive in the language of addition, Cook in the language of multiplication. When Apple actually needed rapid growth with flat resources, they didn't expand the sales force. They gathered key players across job functions, spent a week studying the problem, and collaboratively changed the sales model to use competency centers that better leveraged their best salespeople and deep industry experts in the sales cycle. The result was double-digit year-over-year growth with virtually flat resources—a demonstration that the 2X effect comes from deeper leverage, not more bodies.

• If a leader responds to a stretch target by requesting headcount, then treat that as the logic of addition and redirect to the question of what capability already exists but goes unused.
• If your best people are the most maxed out, then suspect misallocation of their capability rather than a genuine shortage—overworked and underutilized coexist.
• If someone is loading up on resources and building parallel infrastructure, then run the real ROI calculation before it 'catches up' like it did with Jasper.
• If you can access the intelligence you already hired, then you outperform competitors; if you only hire smart people but can't extract it, the strategy fails.
• If people are actually getting smarter and more capable working for you, then you can bank the 5-10 percent growth bonus on top of the 2X; if not, you're at best getting 100 percent.

• Confusing feeling overworked with being fully utilized—people report being maxed out while running well below real capability; the tell is a team that pleads for more resources yet leaves capability on the plate.
• The buffet-child pattern: eagerly loading up on resources, getting the job done, but leaving many people unused. The tell is redundant hires and infrastructure that duplicate what already exists.
• Rewarding articulate hype over results, like Jasper Wallis who talked a good game and was politically savvy—the tell surfaces only when the real ROI number is finally calculated and market share is already lost.
• Over-investing management effort in resource allocation while neglecting resource leverage—Hamel and Prahalad's warning that this makes top management's value-added 'modest indeed.' The tell is endless allocation negotiations settling on '20 percent more output with 5 percent more resources' that satisfies no one.
• Diminishing people unintentionally while believing you're driving performance—shutting down capability overtly or subtly. The tell is that the mental life gets sucked out and problems that should be solvable stall.

• ▸Stretch target: state the new demand in output terms.
• ▸Reflexive headcount ask: what addition would be requested by default?
• ▸Current utilization estimate: where does each key person actually operate (toward 70-100%+)?
• ▸Underused capability inventory: name specific talent/expertise going to waste.
• ▸Redundant resources: list duplicate infrastructure, staff, or overlap to fold back.
• ▸Model redesign: how do you re-route work to your deepest experts (e.g., competency centers)?
• ▸Concentrated study block: who convenes, across which functions, for how long?
• ▸Growth-bonus check: where will people get smarter, adding 5-10% on top of 2X?
• ▸Real ROI line: the honest return number that must beat the hype.

1. 1Adopt the logic of multiplication over addition: assume most people are underutilized, that all capability can be leveraged with the right leadership, and therefore intelligence can be multiplied without a bigger investment. Before requesting new headcount or budget, audit what capacity your current people are not being asked to give.
2. 2When you face a growth target with flat resources, don't expand the workforce—gather the key players across job functions, dedicate concentrated time to study the problem, and collaboratively redesign how you deploy existing talent (Apple's approach).
3. 3Ignore org charts when sourcing intelligence. Map talent networks instead—identify who has genius you can put to work regardless of reporting lines, then open a pathway for them to contribute to your problem.
4. 4Find each person's native genius by watching for what they do easily and well, then place them where they operate at their highest point of contribution rather than where the chart assigns them.
5. 5Set high expectations and drive hard results—be a hard-edged manager, not a feel-good one. Because you see a lot in people, expect a lot; extract capability people didn't know they had to give.
6. 6Restore capability by leading like Lior, not Yuval: replace testing, mocking, and detail-control with calm inquiry and shared problem-solving that lowers fear so people can think and perform.
7. 7Measure outcomes with a real ROI calculation, not hype or infrastructure size. Fold or remove empire-building duplication before it wastes millions and forfeits market opportunities.

Apple needed rapid growth in one division with flat resources and did not expand its sales force. Leaders gathered the key players across various job functions and took a week to study the problem, then collaboratively developed a solution. They changed the sales model to use competency centers that better leveraged their best salespeople and deep industry experts within the sales cycle. The result was year-over-year growth in the double digits with virtually flat resources. The contrast is Jasper, who hired at a breakneck pace, built redundant infrastructure, and even secured a dedicated office tower—until the real ROI calculation showed his products were hype and the company was losing market share, at which point he was removed and his division folded after millions were wasted.

• If you're tempted to throw more resources at a problem, then first ask what capability your existing people are not being asked to contribute—multiply before you add.
• If someone's genius is visible but they don't report to you, then treat the org chart as irrelevant and open a pathway for them to contribute anyway—everyone works for a Multiplier.
• If a group needs facilitation more than a boss, then lead through inquiry and shared problem-solving rather than commanding every detail.
• If a capable person's performance collapses, then examine the leader above them (the Yuval effect) before concluding the person lacks ability.
• If a division is generating hype and duplicate infrastructure, then run the real ROI calculation and consolidate rather than fund the empire.

• Confusing motion with results—hiring fast and building infrastructure (Jasper) reads as growth but hides lost market share; the tell is impressive headcount and office space with no ROI calculation behind it.
• Being a feel-good manager instead of a hard-edged one; the tell is people feel pleasant but aren't stretched—Multipliers get things from people they didn't know they had to give.
• Controlling every detail and finding every mistake like Yuval; the tell is a smart person becoming tense, fearful, and failing maneuvers they aced in the classroom.
• Respecting org-chart boundaries when sourcing talent; the tell is untapped genius sitting in other functions while you claim you lack the people to grow.
• Underutilizing talent by hoarding resources (Empire Builder); the tell is stagnant, inert people, a downward cycle of decline, and difficulty attracting top talent.

• ▸Growth target: the outcome you must hit (revenue, faster problem solving, quality)
• ▸Current resource baseline: people and budget you have right now
• ▸Underutilized capability: capacity people are not being asked to give today
• ▸Key players to convene: cross-functional individuals who own the problem
• ▸Native genius map: each person's easy-and-excellent contribution and where it belongs
• ▸Boundaries to ignore: talent outside your reporting line you can put to work
• ▸Redesign move: how you'll change the model to leverage existing talent (e.g., competency centers)
• ▸ROI check: the real return calculation that confirms results, not hype
• ▸Leadership tell: are you acting as Yuval (control/fear) or Lior (inquiry/shared problem-solving)?

1. 1State the operating assumption explicitly before you act: 'People are smart and will figure this out.' Behavior follows assumptions, so name the assumption first, then let it drive the choice of behavior.
2. 2For each person you lead, ask the diagnostic question the interviewed manager used: 'In what way is this person smart?' Write down the specific, often-hidden capability you surface — don't settle for a generic label.
3. 3Convert that capability into a stretch: find an assignment that both stretches the individual and furthers the organization's interest. The assignment must be real work, not busywork.
4. 4Shift your default across the five leadership moments: develop instead of use, explore mistakes instead of blame, challenge instead of tell, consult instead of decide, support instead of control.
5. 5In meetings, count how many voices you actually draw out. Treat the room as full of intelligence to access, not a stage for your own — bring the right people together, liberate their best thinking, then get out of the way.
6. 6Measure access, not just talent: ask what percentage of a person's capability you are actually getting. Diminishers extract 20–50%; aim for the Multiplier range of 70–100%.
7. 7Reframe leverage from 'more with less' to 'more by using more' — more of people's existing intelligence and capability that is currently underutilized.

Contrast the two minds directly. The 'intellectual supremacist' ran a technology division of over 4,000 highly educated knowledge workers, yet after a meeting of his top twenty managers troubleshooting a go-to-market problem, he told the author, 'In meetings, I typically only listen to a couple of people. No one else really has anything to offer.' His scarcity/elitism assumption produced a predictable operating style: tell people what to do, make all decisions, take over when someone falters — which manufactured subordination and dependency and left him always 'right.' The Multiplier manager operates from the opposite belief: she takes stock of each team member by asking 'In what way is this person smart?', finds colorful capabilities hidden below the surface, then assigns work that stretches the person while advancing the organization. One CEO captured the stakes: 'Eighty people can either operate with the productivity of fifty or they can operate as though they were five hundred.' The difference isn't the people's raw intelligence; it's how much of it the leader accesses.

• If your instinct is 'they'll never figure this out without me,' then stop — that is the Diminisher's fixed-mindset logic; extend the challenge and give space instead of taking over.
• If someone appears to be failing, then explore the mistake rather than jump in and rescue or blame; rescuing produces dependency.
• If you catch yourself listening to only 'a couple of people,' then treat it as evidence you're diminishing the room, not that the room is empty of intelligence.
• If a person seems unremarkable, then ask 'In what way is this person smart?' before writing them off, and pair the answer with a stretch assignment.
• If you're extracting under 70% of someone's capability, then the constraint is your access, not their talent — change your behavior, not your headcount.

• Believing intelligence is fixed and rare (Dweck's fixed mindset): the tell is the recurring thought 'people who don't get it now, never will,' which forces you to keep doing everyone's thinking.
• Confusing being soft with being a Multiplier — Multipliers are hard-edged, expect great things, and drive extraordinary results; the tell is lowering standards in the name of 'supporting' people.
• Reducing leverage to 'do more with less': the tell is chasing efficiency by subtraction rather than accessing the capability people already possess but their jobs don't require them to use.
• Adopting the language without the assumption — letting 'Multiplier' become a buzzword; the tell is behavior unchanged while vocabulary shifts.
• Taking over the moment work gets hard or high-stakes: the tell is that your smartest people have 'no vacation' and every important decision routes through you.

• ▸Person: name the individual you lead
• ▸In what way is this person smart?: the specific, often-hidden capability you observe
• ▸Current access %: your honest estimate of how much of their capability you extract (target 70–100%)
• ▸Default behavior I use: tell / decide / control / blame / use — circle the diminishing default you fall into
• ▸Multiplier shift: challenge / consult / support / explore / develop — the replacement move
• ▸Stretch assignment: real work that stretches them AND serves the organization
• ▸Assumption I'm operating from: write it verbatim — 'they can't without me' vs. 'they're smart and will figure it out'
• ▸Where I get out of the way: the decision or space I'll hand over this week

1. 1Scan for native genius, not resumes. Watch people the way a genius watcher watches: notice the type of intelligence someone shows quickly and naturally, then name it. You are looking for capability that their present job 'does not allow or even require them to use.'
2. 2Attract regardless of ownership. Drop the Empire Builder split between resources you own and those you don't. Recruit and pull in talent across job functions, and treat the question 'who owns this resource?' as irrelevant to whether you deploy it.
3. 3Place people at their highest point of contribution, not their most visible role. Give real, meaningful assignments, not showpiece or 'hood ornament' positions. Match the assignment to the native genius you identified.
4. 4Use more, not less. Reject the logic of addition ('throw more resources at it'). Instead extract fuller capability from existing people — get eighty people to operate as though they were five hundred by accessing intelligence already present.
5. 5Remove the blockers that suppress capability. Identify Diminisher behaviors — public mocking, constant scrutiny, one-way flow of intelligence — and strip them out so people's ideas stop suffocating in your presence.
6. 6Keep a hard edge while doing it. Because you see a lot, expect a lot. Set higher standards and drive extraordinary results; being a Talent Magnet is not being a 'feel-good' manager.
7. 7Ready talent for the next stage. Accelerate careers — make sure people can honestly say they grew more around you than any other manager, and that your reputation is a place where talented people develop, not where careers die.

Mitt Romney operated as a Talent Magnet by accelerating Meg Whitman's career; she went on to become CEO of eBay and led an eighty-eight-times increase in revenue. He was not a one-off: he was a magnet and accelerator in the careers of hundreds of people with similar stories. Contrast this with the Diminisher's tell in the tank-commander example: Yuval, top 0.1 percent of talent, treated Gabriel's battlefield savvy as competition, publicly mocked his team when they missed waypoints, and kept them under constant scrutiny. Within a week Gabriel — a proven battlefield star with ten times the in-tank hours of his peers — was convinced he couldn't navigate. Same person, same talent; the difference was whether the leader drew out capability or suffocated it. A Talent Magnet would have deployed Gabriel's fast, accurate situational read at its highest point of contribution rather than proving something at his expense.

• If you catch yourself asking 'who owns this resource?' before deploying someone, then you are Empire Building — deploy on fit to native genius instead.
• If a talented person you recruited holds a visible but not meaningful role, then you have a hood ornament, not a contribution — reassign to real work or you will watch their capability languish.
• If the shared IQ drops and meetings double when you enter, then you are the black hole — stop injecting your own intelligence and start pulling out theirs.
• If your people are 'overworked and underutilized,' then your problem is access to capability, not headcount — add demands on their genius, not bodies.
• If someone is struggling in silence and pulling all-nighters rather than getting help, then your environment is punishing exposure — remove that blocker before adding challenge.

• Recruiting for show. You heavily recruit talented people, then give them a showpiece role and leave them to languish; the tell is people were 'drawn in' but describe their role as visible, not meaningful.
• Empire Building. You hoard and control resources, dividing them into owned and not-owned; the tell is your recognition is measured by the size of your organization growing, not by people growing.
• Being the smartest person in the room. Your resolve to look smart makes others look dumb and intelligence flows only one way; the tell is that ideas suffocate and die in your presence.
• Mistaking scrutiny for standards. Like Yuval, you flaunt superior knowledge and mock failures; the tell is capable people become less capable the longer they work under you.
• Going soft. You confuse being a Talent Magnet with feel-good management; the tell is you find capability but don't demand all of it, so results stay ordinary.

• ▸Person: name the individual you are assessing.
• ▸Native genius: the one type of intelligence they show quickly and naturally.
• ▸Current utilization %: rough estimate of capability their present role uses.
• ▸Ownership status: whose 'resource' are they — and note it is irrelevant to deployment.
• ▸Highest point of contribution: the specific assignment that would use their genius fully.
• ▸Real vs. visible: is the intended role meaningful work or a hood ornament? (state which).
• ▸Blockers to remove: fears, scrutiny, or your own behaviors suppressing their capability.
• ▸Stretch standard: the extraordinary result you expect that gives them a hard edge to grow against.
• ▸Next-stage readiness: what this assignment prepares them for after this one.

1. 1Audit your default reaction when someone else is working: if you jump in and do it for them, hold back instead. Michael Chang learned that when he restrains himself, people step up and often produce something better than he would have.
2. 2Recruit for a learning orientation, not just current competence. Screen deliberately for people who show a strong appetite to learn, because the environment you build runs on rapid learning from mistakes.
3. 3Remove fear before you raise intensity. Strip out the fear of judgment first (the thing that gives thinking a chilling effect), then load the environment with demand for best effort. Comfort and intensity coexist; you need both.
4. 4Separate directness from destructiveness. Tell the truth plainly, but calibrate it so people 'blossom' rather than shrink. Michael saw brutal honesty damaged people and rebuilt his candor to be direct without being destructive.
5. 5Give explicit permission to think and physical/agenda space to do the work. Everyone should know they are allowed to contribute; then do not fill that space yourself.
6. 6Hold a hard edge on standards. Expect great things, be tough and exacting, and drive people to extraordinary results — the intensity is not softness, it is high demand paired with safety.
7. 7Treat mistakes as learning events. Build the environment so people can make an error, extract the lesson fast, and grow from it rather than hide it.

Michael Chang started his career forceful with his opinions, erring toward brutal honesty. He noticed its damaging effect and reflected that it 'certainly doesn't get people to blossom.' As he gained experience, he grasped that once you become the leader the center of gravity is no longer yourself; a mentor taught him the leader's job is to put other people on stage. He became less controlling and learned to give people space, holding back where he used to jump in and do it for them — and found people not only stepped up but often surprised him by producing something better than he would have. He built specific practices: recruiting people with a strong learning orientation and creating a learning environment where he could tell the truth and have others grow from it, learning to be direct without being destructive. Today he is CEO of a thriving start-up. The lesson: liberation is not going soft — it is removing fear while keeping the demand high.

• If you catch yourself about to jump in and do the work, then hold back and let the person step up first.
• If the environment is comfortable but slack, then add demand for best effort; if it is intense but fearful, then remove the fear of judgment first.
• If your honesty makes people shrink rather than grow, then keep the truth but recalibrate delivery to be direct without being destructive.
• If you demand best thinking but don't get it, then check whether you are operating as a Tyrant — fear is suppressing the very thinking you're demanding.
• If a candidate lacks a strong learning orientation, then question the hire, because the environment depends on people who learn fast from mistakes.

• Confusing intensity with tension: you create a tense, fearful climate (the Tyrant) that suppresses thinking, then wonder why people give you less than their best. Tell: you demand best thinking yet consistently don't get it.
• Mistaking liberation for being a 'feel-good' manager: you drop standards to be liked. Tell: people enjoy the relationship's pleasantries but produce nothing extraordinary — Multipliers are hard-edged, not feel-good.
• Brutal honesty as a habit: you equate candor with harshness. Tell: people don't blossom, they go quiet and defensive around you.
• Being an Accidental Diminisher: you don't realize the restrictive impact you have because you assume your job is to be the smartest in the room. Tell: you're surprised to learn how little people give you despite how hard they work.
• Filling the space you claim to give: you say people can think, then jump into the details and do it for them. Tell: you never see the better-than-yours work that emerges when you actually hold back.

• ▸Fear source to remove: name the specific judgment or reaction people fear from you
• ▸Space to give: where/when will you hold back and let others step up
• ▸Intensity signal: the high standard or best-effort demand you will state plainly
• ▸Directness check: rephrase your feedback to be true but non-destructive
• ▸Learning-orientation screen: how you'll test a hire's appetite to learn
• ▸Mistake protocol: how a specific error will be turned into fast learning, not blame
• ▸Your jump-in trigger: the moment you habitually take over — and your replacement move
• ▸Permission statement: the exact words granting people the right to think and contribute

1. 1Start with a question, not an answer. Frame the challenge as a bigger question that people cannot yet answer (Drucker: the difference between a Nobel winner and others is that they ask bigger questions). Ask something like 'How do you run a country without oil?'
2. 2Seed the opportunity rather than dictating the solution. Multipliers 'ensure direction gets set' rather than personally giving directives to showcase what they know. Resist the Know-It-All reflex to hand over the answer.
3. 3Test and iterate the question in small groups before committing. Pose the question, gather colleagues, work the problem across weeks or months until the opportunity comes into focus — do not demand instant execution of a fully-formed plan.
4. 4Lay down a concrete stretch challenge that extends people beyond current knowledge — define an opportunity 'that causes people to stretch,' not one that repeats what they already know.
5. 5Generate belief that the impossible is possible. Explicitly build conviction that it can be done, so people extend past what they currently know rather than shrinking from the size of the challenge.
6. 6Keep the hard edge. Expect great things and drive people to extraordinary results — Challenger is not a feel-good posture. Look into people, find capability, and demand all of it.
7. 7Hold the challenge until the opportunity is clear, then build the team by explaining the opportunity as you see it — recruit through the clarity of the opportunity itself.

In 2005 Shai Agassi sat at Davos as one of 200 Young Global Leaders and was asked a simple question: 'What could you do to make the world a better place?' The question stuck. Rather than jump to an answer, he distilled it into a sharper challenge — 'How do you run a country without oil?' — where the answers were initially far from simple. He posed the question and tested ideas with his Young Global Leaders colleagues and in a white paper to the World Economic Forum, then worked the question in small groups for six months, iterating through several versions. After several iterations he could see the opportunity; after a year he knew pursuing it was right. He left SAP in 2007 and founded Better Place in Palo Alto, then built his team simply by explaining the opportunity as he saw it. The sequence — bigger question, iterated in small groups, opportunity made visible, team built on belief — is Challenger discipline in action.

• If you already know the answer and are giving directives to show it, then you are operating as a Know-It-All, not a Challenger — convert the directive into a question.
• If the challenge only asks people to repeat what they already know, then it is not a stretch — raise it until it forces people to extend beyond current knowledge.
• If people don't yet believe it can be done, then stop assigning tasks and invest in generating belief first.
• If the environment feels tense (fear of judgment) rather than intense (demand for best thinking), then you have crossed into Tyrant territory and thinking will shut down — re-establish safety before extending the challenge.
• If you're being a 'feel-good' manager who eases expectations, then you've dropped the hard edge — expect great things and drive for extraordinary results.

• Answering your own question to display knowledge — the tell: you leave meetings having 'set direction' by monologue, and people execute your plan rather than one they helped shape.
• Skipping the iteration phase and demanding instant execution of a fully-formed plan — the tell: no small-group testing, no white-paper stage, people meet the challenge as a fait accompli.
• Setting a stretch goal without generating belief — the tell: people privately think it's impossible and quietly disengage while nodding along.
• Being an Accidental Diminisher — you grew up praised for personal intelligence, became boss, and assume your job is to be the smartest; the tell is you don't notice the restrictive impact you're having on others.
• Confusing intensity with fear — the tell: people give safe, cautious answers and withhold their best thinking because they fear judgment.

• ▸Bigger question: state the challenge as a question you cannot yet answer
• ▸Seeded opportunity: what possibility are you pointing to (not the solution)?
• ▸Small-group test plan: who will you pose the question to and over what period?
• ▸Iterations run: what versions of the question/idea have you cycled through?
• ▸Stretch gap: what must people learn that they don't currently know?
• ▸Belief-building move: how will you convince them the impossible is possible?
• ▸Hard-edge standard: what extraordinary result are you expecting, exactly?
• ▸Direction check: did you set direction yourself or ensure direction gets set by them?

1. 1Frame the issue before the meeting: name the decision, define why it matters, and state the question people will debate so they arrive prepared to think, not react.
2. 2Recruit the right minds and give them a clear role: bring in people who hold relevant intelligence and tell them their job is to challenge the position with facts, not defer to rank.
3. 3Demand evidence over opinion: require each participant to ground claims in data or observed reality, forcing the debate onto facts rather than volume or seniority.
4. 4Create safety and rigor simultaneously: signal that disagreement is expected and welcomed, then hold everyone to the standard of defending positions under hard questions.
5. 5Actively provoke the debate: ask the hard questions yourself, invite the counterarguments, and pull the quiet experts into the exchange so intelligence flows both ways, not just from you.
6. 6Drive to a sound decision the group understands: after rigorous exchange, name the decision and the reasoning behind it so the organization executes rather than relitigates it.
7. 7Close the loop for execution: because people debated the issue up front, they understand it well enough to act efficiently once you decide.

Lutz Ziob, general manager of Microsoft Learning, runs decisions this way. His team describes him as someone who "creates an environment where good things happen" and who "ferociously debates the important decisions." He recruits great people and lets them make mistakes, which builds the safety needed for real debate. But the debate is not soft: he demands the team's best effort while sharing the success with everyone. Contrast this with the Intel Diminisher who decided alone, telling his people "no one else's opinion mattered" and getting only 50 percent of Vikram's contribution. The Debate Maker version gets both the sound decision and an organization that understands and can execute it.

• If a decision is high-stakes and the organization must execute it, then debate the issue up front rather than deciding efficiently inside a small inner circle.
• If someone advances a position, then require it be grounded in facts—if they can only offer opinion or authority, the claim doesn't count.
• If the room goes quiet or agrees too fast, then ask the hard questions yourself and pull in the experts, because unchallenged consensus is a warning, not a win.
• If you find yourself listening to only a couple of people, then you are deciding like a Diminisher—stop and widen the debate.
• If the debate has run its course, then name the decision and its reasoning so people execute it instead of debating its soundness afterward.

• Deciding efficiently in a small inner circle and leaving the broader organization in the dark—the tell is that people debate whether the decision was sound instead of executing it.
• Demanding best thinking while creating fear of judgment (the Tyrant move)—the tell is that people go quiet and you don't get the thinking you asked for.
• Using debate as theater while the real decision is already made—the tell is that no fact ever changes the outcome.
• Believing "they will never figure this out without me" and dominating the exchange—the tell is intelligence flowing only one direction, from you to them.
• Sparking rigor but never closing—the tell is endless relitigation because no clear decision and rationale were named.

• ▸Decision to be made: state the single decision in one sentence.
• ▸Why it matters: name the stakes so people bring their best effort.
• ▸Debate question: write the exact question people will argue.
• ▸Minds in the room: list who holds relevant intelligence and their assigned challenge role.
• ▸Required evidence: specify the facts/data each side must bring.
• ▸Hard questions I will ask: list the provocations that force rigor.
• ▸Safety signal: state how you'll show disagreement is expected.
• ▸Decision + rationale: record what was decided and why, in plain terms.
• ▸Execution handoff: note who understands it well enough to act, and next step.