Pomodoro and Atomic Habits for meeting-heavy weeks
Last updated: ยท Reviewed quarterly
Francesco Cirillo's timer assumes you own a stretch of the day to divide into 25-minute slices. James Clear's habit laws assume a life with stable cues in it. A meeting-heavy calendar breaks the first assumption and quietly satisfies the second, which is why one of these techniques needs resizing and the other needs almost nothing.
Pomodoro, resized to the gaps you actually have
The standard technique: pick a task, work 25 minutes with no interruptions, break for 5, and take a longer break after four rounds. Its real mechanism is not the number 25. It is that a timer converts an unbounded task into a bounded one, and that a bounded task is far easier to start — which is why Pomodoro works on procrastination as much as on focus.
The failure on a meeting-heavy calendar is arithmetic. Four uninterrupted pomodoros need two hours, and a day with calls at 10:00, 11:30, 1:00 and 3:00 contains no such run. The usual response is to conclude the technique doesn't apply here. The better response is to notice that the gaps between those meetings are already pomodoro-shaped containers with a hard external stop — the next meeting — which is a stronger commitment device than any timer.
So invert it. Don't carve pomodoros out of the day; treat each gap as one, and size the task to the box:
| Gap | Treat it as | Put in it |
|---|---|---|
| 5–10 min | The break, not a pomodoro | Closing out the meeting you just left, then away from the screen |
| 20–30 min | One pomodoro | A single task chosen before the gap starts, no switching inside it |
| 50–60 min | Two, with a real break between | Two slices of the same task; the break is what protects the second one |
| 90 min+ | Three, or one long block | The one task per week that genuinely cannot be sliced |
Three adjustments make this hold up. Choose the task before the gap opens, because a 25-minute gap spent deciding what to do is a gap spent on nothing. Start the timer for the actual remaining time rather than a nominal 25, so the box matches the wall clock. And give the first five minutes after a meeting to closing that meeting out, not to the new task — attention residue from an unclosed meeting is the most reliable way to waste the pomodoro that follows it. More on defending those gaps in protecting focus between meetings.
The four laws, applied to meeting follow-up
Clear's model is that a habit is a loop of cue, craving, response, reward, and that you build one by making it obvious, attractive, easy, and satisfying. The habit worth building in a meeting-heavy role is narrow and specific: writing down what was decided before you leave the meeting behind. Almost everyone knows they should. Almost nobody does it consistently, and the four laws explain exactly why.
- Make it obvious. The cue is not "later" or "when I have time." It is the meeting ending — an event that happens six times a day whether you plan it or not, and one of the most reliable cues available in any working life.
- Make it attractive. The framing that works is not diligence, it is relief: this is how you stop carrying the meeting in your head into the next one. The reward is the load coming off, and that is a real feeling you can notice.
- Make it easy. This is where the habit usually dies. If the response is "write up the meeting," it takes twenty minutes and will not survive a back-to-back day. If the response is one line, it survives.
- Make it satisfying. Keep the log in one visible place. Watching a decision log grow across a quarter is the immediate reward for a practice whose real payoff arrives months later, when someone asks why you chose that.
Habit stacking: one sentence to set up
Clear's stacking formula is "after [current habit], I will [new habit]." The current habit has to be something that already happens without effort, and a meeting-heavy calendar supplies those all day.
- After a meeting ends, I will write one line: the decision and its owner. One line, not notes. If nothing was decided, write "no decision" — that is itself worth knowing when a series of them accumulates.
- After my last meeting of the day, I will look at tomorrow's calendar and name one task per gap. Two minutes, and it is what makes the pomodoro half of this page possible.
- After my Friday afternoon slot, I will read the week's decision lines. The lowest-energy hour of the week, spent on the one review that needs no energy.
Start with the first one alone. Three simultaneous new habits is how people end up with none, and the first is the one the other two depend on.
The two-minute rule, on a fragmented day
Clear's version of the two-minute rule is about scaling a habit down until it is trivially startable: "read before bed" becomes "read one page." Allen's older version is about disposal: if it takes under two minutes, do it now rather than filing it. Both apply here, and they apply to different things.
Use the disposal version on the five- and ten-minute gaps: the reply that confirms a decision, the calendar invite, the one-line answer that unblocks someone. These are the tasks that otherwise pile into an evening and are ideally suited to a gap too small for anything else. Use the scaling-down version on the habit itself: on a day when writing the decision line feels like too much, write the decision without the owner. A habit performed badly is still performed; a habit skipped is a habit that decays.
The trap to avoid is letting the small stuff colonize the 25-minute gaps too. Two-minute tasks are infinite — there is always another one — so they will consume any container you give them. Keep them in the small gaps by rule, not by judgment in the moment.
Why the follow-up habit fails, and the part you can remove
Clear is blunt that friction beats motivation over time. The friction in the follow-up habit is not writing the line — it is recalling what to write. Reconstructing the decision, who agreed to it, and what the caveat was takes ten minutes at the end of a meeting-heavy day, and a habit with ten minutes of friction in front of it does not survive a bad week.
Removing that friction is what makes the habit stick, and it is a capture problem rather than a discipline problem. Earkeep records mic and system audio continuously while it runs and transcribes locally on your device, so by the time a meeting ends the record already exists — no bot to invite, no start/stop to remember. Meetings are defined afterwards by selecting a span on a timeline, or automatically from a connected calendar; audio is processed only in memory and never written to disk. The response in the habit loop shrinks from "remember and reconstruct" to "read and confirm," which fits in the gap you actually have.
The format for the line itself, and what to do with a quarter of them, is in never leave a meeting empty-handed.
Make the follow-up habit easy enough to keep
Download Earkeep free for macOS and take the reconstruction step out of the loop.
14-day full trial, no account, no card required.