Pomodoro Coach

---
name: pomodoro-coach
description: Coach the Pomodoro Technique properly: interval design, task sizing, interruption handling, and adapting cycles to real work. Use when building focused work habits or fighting distraction and procrastination.
category: productivity
---

# Pomodoro Coach

## Overview

Work in focused intervals (traditionally 25 min), take short breaks, and after four intervals take a longer break.

The real power isn't the timer — it's the ritual: commit to one task, make interruptions visible, measure work honestly.

One pomodoro = one uninterrupted interval on one task. Interruptions get logged, not served.

The technique trains three muscles: starting (commitment is small), sustaining (timer holds you), stopping (breaks prevent burnout).

Count completed pomodoros per day: a concrete measure of focused effort that can't be faked by looking busy.

## When to use

- Starting focused work when motivation is low or dread is high
- Breaking large, intimidating tasks into approachable chunks
- Diagnosing where your attention actually goes during the day
- Building a sustainable deep-work routine from scratch
- Recovering focus after a period of fragmented, reactive work

## Core concepts

- **One task per pomodoro.**
  Write down exactly what you'll do before starting. Switching mid-interval is not allowed; the written commitment is the contract.
- **The timer as commitment device.**
  25 minutes is short enough to start, long enough to matter. The guaranteed stop makes starting easier.
- **Interruptions: log, don't serve.**
  Internal ('email Sam') -> scratch pad, return to task. External -> negotiate ('20 minutes') or log and resume.
- **Breaks are structural.**
  5 min: stand, water, look away. 15-30 min after four. Skipping breaks borrows from tomorrow — the break is part of the work.
- **Adapt the interval.**
  25/5 is the default, not law. Deep work: 50/10 or 90/20. Fragmented days: 15-min admin sprints. Match interval to work and energy.
- **Count honestly.**
  A pomodoro counts only if truly focused. Half-distracted intervals don't count — the honesty is the feature.
- **Estimate in pomodoros.**
  Size tasks in intervals ('~6 pomodoros'). Estimation skill compounds; daily planning becomes concrete.
- **The scratch pad.**
  A single place for every interruption and stray thought. Reviewing it daily reveals fixable system problems.

## Practical workflow

1. **Plan the day's pomodoros.**
   List tasks, estimate each (1-4 pomodoros; bigger gets split). Realistic total: 6-10 intervals is a full day.
2. **Set up the environment.**
   Silence notifications, phone out of reach, close unrelated tabs. Preparation is ritual, not overhead.
3. **Start the first interval fast.**
   State the task in writing, start the timer within 5 minutes of planning. Momentum beats perfect setup.
4. **Take real breaks.**
   Stand, move, hydrate, look at distance. No 'quick checks' — that's work wearing a break costume.
5. **Review interruptions daily.**
   Scan the scratch pad. Recurring items are system problems (mute channel, batch email) not willpower failures.
6. **Track counts per project.**
   Log completed pomodoros alongside output. Weekly review: where did focus actually go? Which estimates were off?
7. **Adapt weekly.**
   Abandoning 25s at minute 40? Switch to 50s. Skipping breaks? Shorten intervals. Technique serves you, not vice versa.
8. **Protect the first interval.**
   Do the hardest task in pomodoro #1. Starting with email trains the brain that mornings are for reacting.

## Common pitfalls

- **Rigid 25 minutes for everything.**
  Deep work needs longer arcs, admin needs shorter. Adapt or the technique feels like a cage and you'll quit.
- **Fake pomodoros.**
  Timer running while scrolling and half-working. Not focused? Stop the timer, restart. Honesty is the point.
- **Skipping breaks.**
  'I'm on a roll' borrows from tomorrow. Take the break; the roll survives, and you'll sustain it longer.
- **No task definition.**
  Starting with 'stuff' guarantees a wasted interval. Name the single task first, in writing.
- **Interruption guilt.**
  Interruptions are data, not moral failures. Log without judgment, then fix the pattern.
- **Counting as competition.**
  Ten focused intervals beat fourteen distracted ones. Quality first, then quantity.
- **Wrong work for the method.**
  Pomodoro is poor for 2-hour immersion (deep debugging, complex writing). Use longer intervals there.
- **No review.**
  Running timers for weeks without reviewing counts and logs. The review turns a timer into a coaching system.