What Leaders and Managers Can Learn from Unlimited Power
Managers are promoted for being good individually, then handed a team and left to guess at leadership from scratch, as though no one has ever solved the problem of running a one-on-one or delivering hard feedback before. When a project slips, a manager's own flat, irritable mood spreads through the team before the actual issue gets addressed. Vague phrases like "the team isn't performing" cover for one specific gap that could be named and fixed. And a manager who gives every direct report the same kind of feedback in the same tone will connect with some of them and completely miss 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
Find the manager who already does it well
Rather than improvising your management style meeting by meeting, find someone who runs the specific situation you're facing better than you do — a peer manager who runs tight one-on-ones, or a leader known for calm layoff conversations — and study exactly what they do: their questions, their pacing, their follow-up. Test their approach in your own context before deciding it doesn't apply to you.
A new manager spends a month designing her own performance-review format from a blank document, convinced her team is too different for any existing template, while a manager one floor up already built a version that solves the same problem and would have shared it if asked.
Before your next hard conversation — a review, a layoff, a conflict between two reports — find one manager who has handled that exact situation well and ask them to walk you through what they actually said.
Change your state before you walk into the room
Your mood at the start of a one-on-one sets the tone for the whole conversation, and waiting to "feel ready" before a hard talk wastes the only window you control. A minute of standing tall, breathing slowly, and deciding what you want to focus on can shift you from reactive to steady before you open the door.
A manager walks into a tense team meeting straight from a bad call with his own boss, still tense and short with people, and the team reads his mood as a verdict on their own performance rather than what it actually was.
Before any conversation that matters, take ninety seconds alone — stand, breathe deliberately, picture the outcome you want — rather than walking in carrying whatever mood the last meeting left you in.
Name the specific problem, not the sweeping one
"The team isn't performing" is a verdict with nowhere to go; "two of the five deliverables missed their date last sprint" is a problem you can actually solve. Precise language about what's actually happening keeps a fixable issue from calcifying into a story about failure.
A manager tells her director "the team is falling apart" after one missed deadline, triggering an unnecessary reorg conversation, when the specific issue was one engineer overloaded on two projects at once.
Before raising a concern with your own boss or team, write the specific, bounded version of the problem and use that language instead of the sweeping one.
Manage each person the way they actually communicate
Some direct reports want feedback direct and fast; others need context first or prefer it in writing before a conversation. Notice how each person naturally communicates and adjust your approach to meet them there, rather than running one management style on everyone and wondering why it lands unevenly.
Borrowing another manager's exact style can clash with matching your own team's communication preferences — what works for their team may not fit yours. Take the borrowed approach as a starting structure, then adjust the specific delivery to how your own people actually take in information.
Name one thing, honestly
Which member of your team do you manage least effectively simply because their communication style is furthest from your own natural one?
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
Before raising a concern with your own boss or team, write the specific, bounded version of the problem and use that language instead of the sweeping one.