What Leaders and Managers Can Learn from The Magic of Thinking Big
Managers are trusted with other people's ceilings as much as their own, and the trap is subtle: a manager who quietly caps their own ambition tends to cap their team's without ever saying so out loud. The safe headcount ask, the modest OKR, the promotion case that undersells someone's actual potential — these aren't neutral choices, they're a belief system leaking into every decision the manager makes on behalf of others.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Manage the ceiling you're setting for your team, not just yourself
A manager's private assumptions about what's achievable become the team's public reality through a thousand small decisions — which goals get approved, which requests get made upward, which stretch assignments get offered. Raising your own sense of what's possible is, for a manager, also an act of raising it for everyone reporting to you.
A manager consistently submits budget requests well below what the team actually needs "to be realistic," and the team quietly becomes known as the group that never asks for much and never gets much, while a peer team that asks boldly keeps getting resourced.
Before finalizing your next team goal or resource request, write down what you'd propose if you assumed leadership wanted you to think bigger, and compare it to what you were about to submit.
Separate "that's not how we do things here" from a real limit
Managers accumulate a long list of institutional excuses — "leadership won't go for it," "we don't have the political capital" — some accurate readings of a real constraint, some just untested fear repeated until it sounds like fact. A genuine resource shortage or documented policy is not an excuse to overcome by thinking bigger; it's information to plan around. The excuse worth challenging is the one you've never actually tested.
A manager avoids proposing a reorganization they believe would help the team, assuming "leadership already decided against this kind of thing," when in fact no one above them has heard the idea in its current form.
List the reasons you've given for not raising an idea, and mark each one "tested" or "assumed" — then take the top assumed one to the person who could actually confirm or deny it.
Float the idea in the next meeting instead of the next quarter
Management culture rewards fully-formed proposals, which quietly trains people to sit on half-built ideas until they're bulletproof — by which point someone else has often already tried a version of it. A rough idea raised early, even imperfectly, gathers real feedback faster than a polished one raised late.
A manager holds a process improvement idea for two full quarters, wanting to build a complete business case first, while the recurring problem it would have solved keeps costing the team hours every single week.
Take one idea you've been privately refining and raise a rough, one-paragraph version of it in your very next 1:1 or team meeting.
Set a specific team goal and build the room that expects it
A vague aspiration like "raise the bar" changes nothing about how the team runs its Tuesday; a specific, dated goal does. Combine that with deliberately building a team culture, hiring bar, and peer group that treats ambitious goals as the norm rather than the exception, and the goal stops resting entirely on any one person's daily motivation.
Encouraging your team to challenge their excuses can collide with genuinely limited resources — pushing people to "think bigger" about a project that truly lacks budget or headcount just breeds resentment. Resolve this by being explicit about which constraints are real and fixed for now and which are assumptions worth testing, so ambition gets aimed at the second category, not the first.
Name one thing, honestly
Where has your own sense of what's realistic quietly become the ceiling for someone on your team, without you ever deciding that on purpose?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Take one idea you've been privately refining and raise a rough, one-paragraph version of it in your very next 1:1 or team meeting.