# How to Build a Pomodoro Schedule That Actually Works > The 25-minute pomodoro is a starting point, not a rule. Some people focus better in 50-minute blocks, some in 90. Some need 5-minute breaks, some need 15. Here is how to build a pomodoro schedule that fits your work, your energy, and your task type, and how to track what is working. URL: https://uttir.com/blog/how-to-build-a-pomodoro-schedule-that-actually-works Published: 2026-08-22 Author: Uttir Reading time: 6 min Tags: productivity, pomodoro, focus, developer-tools, workflow ## Quick answer Start with 25/5 (25-minute work, 5-minute break). After three or four pomodoros, take a 15-30 minute long break. After a week, look at which pomodoros felt too short (you were in flow when the timer went off) and which felt too long (you were checking your phone by minute 20). Adjust the work block to 15, 30, 50, or 90 minutes based on what you find. Use the [Uttir Pomodoro Timer](/pomodoro-timer) to run the schedule, and the [Stopwatch](/stopwatch) if you want to time your actual focus blocks to confirm the fit. The pomodoro technique is one of the most popular productivity methods in the world, and one of the most misapplied. People hear "25 minutes" and think it is a rule. It is not. It is a starting point. The 25-minute work block and the 5-minute break are heuristics that work for many people in many situations. They are not the only answer. For some tasks, for some people, for some energy levels, they are the wrong answer. This post walks through how to build a pomodoro schedule that actually fits the work you do. The principle is simple: start with the default, measure what works, adjust. ## What the default pomodoro schedule is Francesco Cirillo, who invented the technique in the 1980s, proposed this schedule: - **Work block:** 25 minutes of focused work on a single task. - **Short break:** 5 minutes. Stand up, get water, look out a window. Do not check email or social media. - **After 4 work blocks:** take a long break, 15-30 minutes. This is the recovery block. The short break is the most important part. The point is not to work 25 minutes and then do nothing for 5 minutes. The point is to give your brain a small recovery so the next work block starts fresh. The long break is more important still: it is the block where you consolidate, daydream, and let your subconscious process the previous work block. ## Why 25 minutes works (and when it does not) 25 minutes is short enough that it does not require a heroic act of will to start. Anyone can do anything for 25 minutes. Once you are 10 minutes in, momentum carries you through. The break is small enough that it does not break your flow state too deeply. After 4 blocks, you have 100 minutes of focused work and 30 minutes of breaks — a real morning's work. 25 minutes does not work for every task. Some tasks have a 20-minute warmup (debugging a complex system, writing a difficult section of code) and the actual productive work starts at minute 20. Cutting the block at minute 25 interrupts you just as you are getting into the productive part. For these tasks, longer blocks (50 or 90 minutes) work better. 25 minutes also does not work for every person. People with ADHD often find that 25 minutes is too long to maintain focus without medication or external support. People with high focus capacity often find that 25 minutes is too short — they are in flow at minute 22 and resent the interruption. The right length is whatever lets you do real work without burning out. ## How to find the right block length for you Start with 25/5. Use the [Uttir Pomodoro Timer](/pomodoro-timer) for a week. After each block, write down one of three things: "too short" (I was in flow when the timer went off), "just right" (I was ready for a break), or "too long" (I was checking my phone by minute 20). After a week, count the three categories. If most blocks are "too short", try 50/10. If most blocks are "too long", try 15/3 or 50/10 (a long block can also feel too long if the task is the wrong task). The right answer is not the average — it is the length that maximizes "just right". The [Stopwatch](/stopwatch) is useful for this experiment. Run it during a work block and check what time you naturally want to stop. If you always stop at 35-40 minutes, that is your natural block length. If you always push through to 60, that is your length. If you cannot make it to 15 without checking your phone, that is your lower limit. ## How to find the right break length for you 5 minutes is a starting point. The right break length depends on what you do during the break. Standing up and walking around needs 2-3 minutes. Getting a coffee needs 5-7. Stretching needs 5. Looking at your phone for "just a second" can become 15 minutes and ruin the next work block. The break should not include any of: email, Slack, social media, news, or anything that introduces new information. The break is for your brain to recover, not for your brain to process new input. If you want to scroll your phone, set a 3-minute timer. If the timer goes off and you are still scrolling, you have failed the break. If 5 minutes feels too short (you are still tired when the next block starts), try 10. If 5 minutes feels too long (you start doing other work during the break), try 3. ## How to find the right long break length 15-30 minutes is the standard. The right length depends on the time of day and the intensity of the work. For a morning of focused work, the first long break is usually best at 20-30 minutes. For an afternoon, 15-20 is enough. After a particularly intense block, longer (up to 45) might be needed. The long break is the right time for: a real coffee, a walk outside, a snack, a conversation with a friend, a quick stretch, a few minutes of reading (a book, not social media). It is not the right time for: errands, work email, anything that requires decisions. ## Adapting the schedule to task type Different tasks deserve different schedules. A common mistake is to apply the same 25/5 to every task. It does not have to be that rigid. **Deep work (writing, coding complex features, design work):** 50/10 or 90/20. Long blocks, long breaks. These tasks have a 15-20 minute warmup. A 25-minute block interrupts you at peak. **Shallow work (email, code review, admin, bug triage):** 25/5. Short blocks, short breaks. These tasks are easily resumed after a break. You are not in flow; you are in queue mode. **Creative work (writing, brainstorming, design exploration):** 25/5 with a twist. Use the break to switch context (look at a photo, read a paragraph from a book, walk to a window) rather than to rest. The break serves to "defocus" so the next block is fresh. **Meetings and calls:** pomodoro does not apply. A 30-minute call is a 30-minute call, not a "pomodoro of conversation". Schedule calls back-to-back or in blocks separated by at least 15 minutes. ## How to handle interruptions The most common pomodoro failure is the interruption. Someone messages you. An email arrives. A colleague stops by your desk. Each interruption breaks your flow and you have to start the next block from cold. Two strategies. The first is prevention: close Slack, turn off notifications, put your phone in a drawer, put a "do not disturb" sign on your desk. The second is acceptance: when an interruption happens, write down what interrupted you, finish the current work block (or break it if it is urgent), and restart. The pomodoro is a tool, not a religion; missing one block does not invalidate the day. For an interruption that will take less than 2 minutes (a quick Slack reply, a yes/no question), handle it immediately and restart. For an interruption that will take more, write it down, finish the block, and start a new block for the interruption. Do not let an interruption eat into the next scheduled block. ## How to track what is working A simple spreadsheet or a note in your daily journal: for each work block, the task, the block length, and the rating (too short, just right, too long). After a month, you have data on which tasks deserve which block length. The pattern is usually: coding = 50/10, email = 25/5, deep writing = 90/20, admin = 15/3. The [Uttir Pomodoro Timer](/pomodoro-timer) keeps track of the number of completed blocks, which is a useful daily metric. If you complete 8 blocks in a day, that is 200 minutes of focused work — a real day's work. If you complete 2, something is wrong (interrupts, wrong block length, wrong task selection). ## When to skip the pomodoro Some days are not pomodoro days. If you are sick, if you are in a meeting-heavy day, if you are doing low-energy admin work, the pomodoro is overhead. The technique exists to help you focus, not to make you feel guilty about not focusing. Use it when it helps. Skip it when it does not. ## Related tools - [Pomodoro Timer](https://uttir.com/pomodoro-timer) — A Pomodoro timer with 25/5/15 defaults. Focus, short break, long break, and session counter. Customizable phase lengths. - [Stopwatch](https://uttir.com/stopwatch) — A clean online stopwatch with laps, millisecond precision, and keyboard shortcuts. Runs in your browser. - [Countdown Timer](https://uttir.com/countdown-timer) — Count down to a specific date and time. Set a target, watch the days/hours/minutes/seconds tick down live. - [Reading Time Calculator](https://uttir.com/reading-time) — Estimate how long it takes to read or speak a piece of text. Adjustable words-per-minute for fiction, non-fiction, or speech. --- For the full HTML article, visit https://uttir.com/blog/how-to-build-a-pomodoro-schedule-that-actually-works. This file is the markdown rendering at https://uttir.com/blog/how-to-build-a-pomodoro-schedule-that-actually-works.md. See https://uttir.com/llms.txt for a site-wide summary.