What Leaders and Managers Can Learn from The Talent Code
Managers often run their weeks entirely inside the meetings and decisions they already handle well, while the harder skill — the direct feedback conversation, the reorganization that will upset people, the pitch to a skeptical executive — keeps getting pushed to next week. That's staying comfortably inside your current ability instead of working at its edge, and it means a manager can rack up years of tenure without actually getting better at the parts of the job that matter most in a crisis. Leaders also tend to treat their own missteps — a decision that landed badly, a 1:1 that went sideways — as things to move past quickly rather than specific moments worth dissecting. And without anyone senior enough to watch a manager actually run a real meeting or a real hard conversation, most leadership "development" is just more time in the job, not more skill. Tenure and skill are not the same thing, even though the org chart tends to treat them as interchangeable.
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
Run the meeting you're not yet good at
Every leader has a type of conversation they handle smoothly and one they route around — the technical leader avoids the values conversation, the people-person leader avoids the numbers review. The skill only develops by having the harder version, not more of the easier one.
A manager holds confident, well-rehearsed all-hands meetings but keeps delegating every difficult one-on-one performance conversation to HR, so that specific skill never gets a single real rep.
This week, run the one type of conversation you usually hand off or postpone, and do it yourself.
Take your bad meetings apart instead of moving past them
A decision that backfires or a meeting that goes flat contains a specific, findable cause. Leaders who examine that moment closely improve; leaders who file it under "tough week" repeat it.
After a reorg announcement lands badly, a leader tells their own boss "change is always hard" instead of identifying the exact sentence in the announcement that caused the room to shut down.
After your next rough meeting, name the specific moment it turned, and rewrite your approach to that one moment before you repeat the format.
Build a room where effort is visibly rewarded
People who watch a demanding peer or predecessor operate up close often raise their own standards without a single directive being issued. A team without that kind of visible example tends to settle for whatever effort has always been normal there.
A new manager inherits a team where showing up and getting by has been the unspoken standard for years, and nothing in the daily rhythm signals that harder, more deliberate effort is possible or welcome.
This month, make one piece of unusually careful work — yours or a team member's — visible to the whole team, and say specifically what made it good.
Ask someone to watch you lead, not just hear about it
A leadership book or a survey score can't catch the exact habit that's undermining you in real time. A coach, a trusted peer manager, or a skip-level who actually sits in your meetings and tells you precisely where you lost the room will sharpen you faster than any amount of reading or unguided practice.
Practicing your hardest conversations in real time and protecting your team's trust in your judgment can pull against each other — a visibly fumbled hard conversation costs credibility, and credibility is slow to rebuild once it's shaken. Rehearse the difficult version with a coach or a peer manager first, working out the rough edges somewhere lower-stakes, and only then bring the sharpened version to your own team. Over time, as your team sees you handle harder situations well, the room for visible struggle in front of them actually grows.
Name one thing, honestly
What kind of conversation do you keep delegating or postponing because you're not yet confident running it?
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
This month, make one piece of unusually careful work — yours or a team member's — visible to the whole team, and say specifically what made it good.