What Leaders/Managers Can Learn from The Second Mountain
Daniel finally got the promotion to VP after eleven years of steady climbing. He had the title, the direct reports, the corner office he'd wanted since his first management job. At the all-hands where it was announced, the applause landed strangely flat, like it was happening to someone else. Driving home, he kept replaying a smaller memory instead: a junior analyst he'd mentored years ago, now thriving, who'd sent a note that week just to say thanks. That note had stayed with him longer than the promotion had. He couldn't explain why the thing he'd worked toward felt smaller than the thing he'd nearly forgotten. What had actually been the point of climbing?
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
The summit that isn't the point
Reaching a leadership title is exactly the kind of first-mountain achievement David Brooks describes: real, earned, and not automatically satisfying. The danger is mistaking the discomfort that follows for a sign the next title will fix it, when the actual signal is that authority was never the destination. Leaders who notice this early can ask a different question than "what's the next role," namely what the role is for. That shift doesn't require downsizing ambition; it requires redirecting the same drive toward people and outcomes rather than the next rung.
Dismissing ambition entirely can leave a leader coasting, under-delivering for a team that needs decisive direction.
After your next win, write down one person whose work life is better because of what you built, not just earned.
Leading as a calling, not a control tower
Management becomes a vocation when a leader defines success as the growth of people and mission under their care, not only numbers reported upward. Brooks's idea of calling reframes management from control into service, which changes daily behavior: who gets hard feedback, who gets developed rather than managed out, what gets protected when budgets tighten. This is not softness; it is a harder standard, since it makes the leader accountable for outcomes beyond their own metrics.
Framing every managerial act as "calling" can guilt leaders into absorbing dysfunction that needs structural fixes instead.
Pick one report this quarter, ask what their growth requires, and build one decision around that answer.
Being known by the people you lead
Leaders are trained to maintain distance, but Brooks argues that real commitment, including to colleagues, requires being known, not just respected. A team becomes a community in his sense when people trust the leader will stay present through failure, not only preside over success. That depth doesn't happen through offsites; it happens through leaders admitting uncertainty and letting a team watch them work through a hard call.
Oversharing can undermine the confidence a team needs from its leader during a real crisis.
In your next hard meeting, name one thing you're genuinely unsure about before asking the team for input.
The values behind the decisions
Every leader eventually faces decisions no dashboard can settle, and those moments reveal whatever philosophy actually governs them, whether inherited faith, secular ethics, or a personal code built over years. David Brooks describes his own grounding in Christian faith, but frames it as one path among many equally serious ones. Leadership needs not a specific creed but a genuine, examined framework, religious or not, strong enough to hold when incentives point the wrong way.
Vocation and relational depth collide constantly in leadership: the mission that justifies long hours also justifies missing a moment a team member needed real conversation. Brooks offers no formula for balance, only insistence that neither commitment should quietly cannibalize the other. A leader can hold both by treating specific relational commitments, like a weekly one-on-one or a kept promise, as structure the mission has to work around.
Name one thing, honestly
- Whose growth are you actually accountable for, beyond the dashboard numbers? - When did you last let a colleague see you uncertain, not just in control? - What decision this month would differ if it answered to something beyond the org chart?
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
In your next hard meeting, name one thing you're genuinely unsure about before asking the team for input.