What Leaders and Managers Can Learn from Eat That Frog
Answering easy messages first and leaving the one difficult personnel decision for later is the specific trap Eat That Frog names, and it's an especially easy one to fall into when a manager's day offers plenty of quick, low-stakes tasks to hide behind.
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
Identifying your frog
Your frog is the task that would have the biggest real impact on your team if you finished it, and it's frequently the exact task sitting untouched on your list.
A manager clears their inbox each morning while the one decision that would actually help the team goes untouched for another week.
Name the one task today that would matter most for your team if it got done, even if it's the one you'd rather avoid.
Prioritizing ruthlessly
A short list of priorities accounts for most of your team's real progress; most of what fills a typical day contributes comparatively little.
A manager treats every request as equally urgent, and the few priorities that would have actually moved the team get the same thin attention as everything else.
Sort today's list by real consequence to your team's goals, not by how urgent each request feels, and let that order decide what you do first.
Eating the frog first
Starting the day with your hardest, highest-impact task uses your freshest energy on what actually matters, before meetings and messages fill the day.
A manager takes meetings and answers messages first thing, and by the time they'd get to the frog, the day's energy is already spent.
Tomorrow morning, work on your frog before checking messages or taking your first meeting.
Single-handling until it's done
Starting your frog and staying with it until it's genuinely resolved produces better outcomes than starting it, getting pulled away, and returning to it days later.
Being available to your team and eating your frog first aren't opposites — doing the frog first, before the day's meetings and requests arrive, protects both.
Name one thing, honestly
What's the one decision or conversation you've been postponing that would matter most for your team? What would it take to handle it first tomorrow?
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
Tomorrow morning, work on your frog before checking messages or taking your first meeting.