Form
Daily tracker (notebook or digital) with date, chosen frog of the day, status (done/partial/deferred), short cause note for deferral, and weekly review with frog count and blocker patterns.
RunsheetOperations
Eat the Frog
ComplexityLow
Time15-90 min täglich
Participants1
FormatAsync
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Task manager or notebook; calendar with an uninterrupted morning slot; evening preparation ritual; list of current projects and accountabilities.
People / roles
Solo practice. Optional accountability buddy to receive the day's frog notification in the morning.
Pre-read
Current projects with deadlines; known procrastination topics (which tasks have been postponed for weeks); day type (usually a meeting-light or meeting-heavy morning); energy curve over the day.
Time needed
15-90 min daily
Setup
Establish an evening ritual: choose tomorrow's frog in 5 min. Protect a morning slot from 08:00 or 09:00 for the next 5 days. Keep the frog visible (note on the desk).
02
Core question
The one question this method answers
Which one task, if completed by late morning today, would make the rest of the day noticeably easier?
03
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
1Night before, 5 min | 5 min | Choose one task for tomorrow: important, unpleasant, or deferred. Formulate it concretely (for example, "Client Meyer tax return 2025 position 14 to clarify"), not as a topic. | Choose in the evening, not in the morning. In the morning, distance is missing; people pick the easiest task and call it the frog. |
2Morning, 0-5 min | 5 min | Read the frog before the first meeting, open materials, keep Slack/mail closed. Notify the buddy optionally ("Today's frog: X"). | Whoever opens email in the morning has already lost the frog. Reactive mode replaces proactive start; execution in the first 5 min decides whether the method sticks. |
3Morning, 15-90 min | 15-90 min | Work on the frog without switching tasks. If interrupted, note it and return. If frog < 90 min, finish before noon. | If the frog is not feasible within 90 min, it is too large. Split: today one partial frog, tomorrow the next one. Ensure at least one clear partial completion. |
4Before lunch, 5 min | 5 min | Document the frog (done, partial, blocked). Report to buddy. Rate the day (frog done: success marker; otherwise note causes). | Reflection without judgment. People who miss frogs should gather data on causes (appointments, energy, wrong selection), not guilt. |
04
Artifact
What comes out at the end
Versioning / ownership
One weekly review. If patterns appear (always missing on Wednesday, always tax-return frogs), discuss adaptation rather than silent resignation.
Tool alternatives
- Notion database with daily entries
- Things 3 with today highlighting
- Bullet journal with frog icon
- Plain-text file per week
eat-the-frog-working-template.md
Compact working template for Eat the Frog with context, input, output artifacts, and next step.
Eat the Frog Working Template
Goal
Prioritizes the most important or least pleasant task early in the day.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Priority Task:
- Completion Note:
- Daily Focus:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
05
Example output
Concrete filled scenario, fictional example
eat-the-frog-beispiel.md
Concrete filled scenario, fictional example
Eat the Frog — Week 20, 11-15.05.2026 (Sabine)
| Day | Frog | Status | Notes |
|---|---|---|---|
| Mon | Client Schmidt VAT declaration | done 09:50 | Buddy notified |
| Tue | Drafting 2027 fee agreement | partial 50% | Unexpected 11:00 appointment, split for Wed |
| Wed | Client Meyer fee agreement finished | done 10:30 | - |
| Thu | DATEV training module 3 | not done | Morning appointment came up unexpectedly, slot too short |
| Fri | Clarify client Meyer follow-up questions | done 09:15 | - |
Weekly review: 4/5 frogs completed. Wednesday appointment was not planned in the calendar, lesson: block mornings until 10:00 from Monday. Next week: maximum frog size 60 min, otherwise split it the evening before.
06
Pitfalls
Recognize symptoms and steer against them
Trap
Frog is chosen in the morning
Symptom
Under time pressure the lightest task is chosen in the morning and called the frog, reducing method value.
What to do
Treat evening selection as non-negotiable. If morning selection is necessary, the evening step was skipped; identify the root cause.
Trap
Frog is too large
Symptom
After 90 min the frog is still not done; the day feels like failure even though much was completed.
What to do
Split the frog into partial frogs. Define one clear partial completion per day. Tie success marker to partial completion, not to full completion.
Trap
Email before frog
Symptom
Emails are checked first in the morning, so the frog gets buried behind reactive tasks.
What to do
Keep mail closed until the frog is done or at least 45 min of frog work is completed. Put yourself in focus mode. For true emergencies, explicitly allow the break, otherwise keep discipline.
Trap
Wrong task choice
Symptom
The frog is always of the same type (for example operations), while strategically hard tasks never become frogs.
What to do
Use the weekly review: what is repeatedly avoided? If strategic frogs do not appear for four weeks, the choice process is not honest.
Trap
Escalation to burnout
Symptom
The frog is made harder every day, energy decreases, and the system feels punishing.
What to do
The frog is one concrete uncomfortable task, not the hardest possible day. Choose realistically, manage energy, and respect breaks.
07
Stop criteria
Done signals checkable in under a minute
Work is primarily externally driven (for example support shifts), so the morning slot is not sustainable.
Person has no autonomy over appointments; the morning window is constantly overwritten.
The task list has no real frogs (all routine work), so the method has no added value.
Morning focus is not possible because of shift work or health reasons, and the method becomes demotivating.
The method replaces missing prioritization; without Eisenhower/goal system, too many competing frogs appear.
The method feels punitive for the person; a small-win setup would fit better.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.