What Leaders and Managers Can Learn from The Intelligent Investor
Derek's VP forwarded a newsletter about a competitor's "AI-first restructuring" with the note "we need this by next quarter." Within an hour, three directors had drafted proposals to redirect their budgets toward a flashy new tool nobody had piloted, afraid of being the department that didn't move. Derek felt the same pull: canceling a slow, unglamorous data-cleanup project his team had quietly run for months in favor of the initiative everyone else was suddenly excited about. He opened the budget spreadsheet and noticed he was comparing the two options by how urgent each felt in the room, not by what either would return once the excitement faded. He nearly reassigned his best engineer that afternoon, purely because standing still while everyone else moved felt riskier, even though he couldn't yet say what problem the new tool solved.
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
Evaluating the Initiative, Not the Announcement
Derek greenlights the flashy tool after two leadership meetings, based on the headline and a slick vendor demo, without asking his own team what problem it solves or what it costs to maintain. Three months in, adoption stalls because nobody can explain why it replaced the quieter project, and the team quietly reverts to old workflows while the budget line stays spent.
Before reallocating budget or headcount, require a one-page case describing the actual problem it solves, who owns outcomes, and what would have to be true for it to beat the project it replaces. If that case can't be written without citing what a competitor is doing, treat that as a warning sign, not a mandate.
Building Slack Before You Need It
Derek runs his team at full capacity every sprint because idle-looking capacity draws questions at planning reviews, so there's no headroom when a key engineer goes on leave mid-project. The launch slips, he pulls two people off another initiative to cover it, and that project misses its own deadline, cascading the shortfall through the quarter.
Deliberately staff projects below their theoretical maximum capacity, and defend that headroom as the cost of surviving a bad month, not inefficiency. Review the buffer quarterly and shrink it only after a genuine track record shows the team can absorb disruption without it.
Reading the Room Without Following It
After a rough all-hands where the CEO sounds alarmed about the sector, Derek freezes a hiring plan his team needs, purely to signal alignment, even though nothing about his project's numbers has changed. Two strong candidates take other offers during the freeze, and when the mood shifts back a month later he is rebuilding a pipeline that never needed dismantling.
Separate decisions about your team's plan from reactions to leadership's tone by asking whether anything concrete about your project has actually changed. If the honest answer is no, hold your plan and let the mood pass, updating only when new facts about your own work arrive.
Knowing Your Own Organization's Temperament
Every team has its own tolerance for change and its own memory of initiatives abandoned mid-flight. Leading well means being honest about what your team and leadership chain can sustain under pressure, not the pace you'd choose in a calmer world. A resourcing plan assuming more patience than your organization has ever shown is a plan you're implicitly agreeing to abandon later, and abandoning plans quietly damages trust more than choosing a slower one from the start.
The pressure to look responsive to leadership and competitors can fight the discipline of protecting slack and evaluating initiatives on their own merits. Moving fast earns short-term credit; holding a considered position when everyone else is reacting can look like inaction until it's proven right. Navigate this by separating your public communication from your actual decision: acknowledge a competitor's move without letting that acknowledgment substitute for reallocating real budget before the case is actually made.
Name one thing, honestly
Which of your team's current commitments would you keep exactly as they are if no one outside the team heard about them?
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
Separate decisions about your team's plan from reactions to leadership's tone by asking whether anything concrete about your project has actually changed. If the honest answer is no, hold your plan and let the mood pass, updating only when new facts about your own work arrive.