What Entrepreneurs Can Learn from Leaders Eat Last
Optimizing every decision for the fastest visible win is the specific trap Leaders Eat Last names, and it's an easy one to fall into when a young company's survival can feel like it depends on this quarter's numbers alone.
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 3 selected
The core lessons, applied to you
Building a circle of safety
A team that trusts you'll protect them from internal politics and blame spends its energy competing against the market, not against each other.
A founder publicly blames an employee for a missed deadline that was really a resourcing failure, and the team starts protecting themselves individually instead of solving problems together.
The next time something goes wrong, absorb the initial blame yourself before assigning any, and see how it changes what people are willing to tell you next time.
Short-term reward versus long-term trust
A quick individual win, like taking credit for a team's result to impress an investor, feels good immediately but quietly erodes the trust that produced the result in the first place.
A founder takes sole credit for a launch that was a team effort, and the team's enthusiasm for the next launch is noticeably lower.
The next time you're tempted to take credit alone, name specifically who else made the result possible, publicly, before you talk about your own role.
Leading by absorbing risk first
Taking on the harder, riskier, or less glamorous part of a task yourself, rather than delegating only the risk downward, is what makes people willing to take real risks for you later.
A founder delegates a difficult client conversation without warning, and the employee learns that the founder passes risk down rather than shares it.
The next time a task involves real risk or discomfort, take the hardest part yourself and delegate what's left, rather than the reverse.
Protecting trust as things scale
As your company grows past the size where you personally know everyone, real trust starts requiring deliberate structure (small teams, regular direct contact) rather than happening automatically.
Hitting an urgent fundraising milestone and protecting your team's trust in you aren't opposites — a milestone won by quietly overworking or blaming your team usually costs more in turnover than the milestone was worth.
Name one thing, honestly
The last time something went wrong on your team, did you absorb the risk first, or pass it down?
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
The next time a task involves real risk or discomfort, take the hardest part yourself and delegate what's left, rather than the reverse.