What Leaders/Managers Can Learn from From Strength to Strength
Dana had run the regional sales division for eleven years, promoted originally for her uncanny ability to spot a winning account strategy before anyone else. Lately her fastest read on a new market came a beat slower than her director of analytics, a hire twelve years her junior. She still delivered results, but the quickness she had built her reputation on now took visible effort, and she covered the gap with longer hours. Her boss praised her steady judgment in a recent review, which she took, oddly, as a quiet demotion. Was steadiness worth less than speed, or had she just never been taught to value it?
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
Reading the curve in your own leadership arc
The book's account of an early peak in fast, innovative thinking applies directly to leaders who rose through individual brilliance before ever managing a team. The skills that got someone promoted, quick pattern recognition and rapid analysis under pressure, are not the skills that make someone excellent at developing others over the long run. Recognizing this shift as a normal pattern, not fading competence, lets a leader stop measuring current value against their younger self and ask what the role now calls for.
Some technical leadership roles genuinely require staying hands-on and fast for far longer, so context matters more than a fixed timeline.
Ask a trusted colleague where your judgment has visibly improved over three years, and where your speed has slowed.
Trading solo brilliance for multiplied output
The heart of a manager's transition is moving from having the best answer to helping a team generate its own best answers. That means investing time in coaching, structuring decisions so others practice judgment rather than executing yours, and treating synthesis across a team's work as worth as much respect as one sharp insight. Leaders who make this shift well often find their teams outperform what they could have produced solo, precisely because they stopped trying to be the fastest mind in every meeting.
A team in crisis sometimes needs a leader's direct expertise immediately, not a coaching moment.
In your next team decision, ask two clarifying questions before offering your answer.
Letting go of being the smartest person in the room
Status anxiety runs deep in leadership culture, where being visibly the sharpest thinker built the very career now at stake. Watching a rising manager solve a problem faster than you can trigger real envy, and the instinct is to reassert dominance rather than sit with the discomfort. Loosening this attachment does not mean abdicating standards; it means redefining what makes you valuable, from fastest answer to best judgment about which answers matter.
Some organizational cultures genuinely punish leaders who appear to step back from technical mastery.
Name one recent meeting where you spoke first to prove competence rather than to help the group think.
Leading from a fuller life
Arthur C. Brooks's argument that lasting satisfaction comes from relationships and purpose beyond individual achievement applies directly to leaders whose identities have long fused with their titles. Investing in colleagues, family, and whatever gives meaning beyond the org chart, whether spiritual practice, community, or deeper friendships, builds a foundation that survives any reorg. A title changes; the people you helped along the way tend to remember it long after the title does.
The urge to loosen your grip on being the sharpest person in the room can undercut a team that still relies on your fast judgment during a real crisis. Leaders who overcorrect toward mentorship too quickly can leave gaps only they were positioned to fill. Holding both ideas means choosing moments deliberately: step back to develop others when the situation allows it, and step in when it does not, without treating either move as a referendum on your worth as a leader.
Name one thing, honestly
- When did you last feel envious of a faster or younger colleague, and what did you do with it? - What would change if your review measured who you developed instead of what you produced? - Which part of your leadership identity is tied to speed rather than judgment?
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
Name one recent meeting where you spoke first to prove competence rather than to help the group think.