PRODUCTIVITYDays to result

The Complexity Regulation Rules

Keep tasks in the motivational sweet spot by breaking down or combining

Problem it solves

low productivity

Best for

Anyone who procrastinates on large tasks, gets overwhelmed by project scope, or wastes time on trivial micro-tasks that never move the needle

Not ideal for

Highly creative exploratory work where task boundaries are genuinely unknown, or environments where task sizes are externally dictated and cannot be restructured

Overview

Why this framework exists

The Complexity Regulation Rules are two simple but powerful sizing constraints from the Pomodoro Technique that keep all tasks in a motivational and estimable sweet spot. Rule one: if a task would take more than 5-7 Pomodoros, break it down into smaller activities. Rule two: if a task would take less than one Pomodoro, combine it with similar tasks until they fill at least one Pomodoro.

These rules serve multiple purposes simultaneously. They make estimation more accurate (smaller, well-defined tasks are easier to predict). They sustain motivation by ensuring you complete multiple meaningful tasks each day rather than grinding endlessly on one monolithic project. They reveal simpler solutions by forcing you to think incrementally about how to deliver value in smaller units. And they prevent the cognitive overhead of tracking tiny fragments of work.

The deeper insight behind these rules is that complexity is not just a project management problem; it is a psychological one. Tasks that feel too large trigger avoidance and procrastination. Tasks that feel too small feel meaningless and fail to engage focused attention. The Pomodoro sizing rules keep everything in the zone where work feels challenging but achievable, which Maslow and other psychologists identify as the optimal state for sustained motivation and performance.

Core principles

5 total
  1. If it takes more than 5-7 Pomodoros, break it down into incremental activities that each deliver a bit of value.
  2. If it takes less than one Pomodoro, add it up by combining with similar tasks.
  3. The goal of breaking down is not division for its own sake but identifying incremental paths with the lowest possible complexity.
  4. Smaller activities are more understandable, easier to estimate, and reveal simpler solutions.
  5. Completing several challenging but manageable tasks daily is the optimal recipe for sustained motivation.

Steps

4 steps
  1. Estimate the Task in Pomodoros
    Before planning your day, assign a Pomodoro estimate to each task in your Activity Inventory. Use your best judgment for how many uninterrupted 25-minute intervals the work will require.
    Pro tipIf you genuinely cannot estimate a task, it probably needs exploration first. Allocate a fixed number of Pomodoros to research and planning before estimating the real work.
  2. Apply the Break-It-Down Rule for Large Tasks
    Any task estimated at more than 5-7 Pomodoros must be decomposed into sub-tasks. Each sub-task should be an incremental activity that delivers some value on its own, not just an arbitrary slice of the larger work. Write each sub-task as a separate line in your Activity Inventory with its own estimate.
    Pro tipAsk: 'What is the smallest meaningful deliverable I can produce toward this goal?' Each sub-task should answer that question.
    WarningSimply splitting a task into arbitrary halves is not the same as incremental decomposition. Each sub-activity should make sense as a standalone accomplishment.
  3. Apply the Add-It-Up Rule for Small Tasks
    Tasks estimated at less than one Pomodoro should be combined with similar or complementary tasks until the group fills at least one Pomodoro. Alternatively, leave the task without an estimate and plan to combine it with other small tasks on the To Do Today Sheet.
    Pro tipChoose to combine tasks in the Activity Inventory when the activities are very similar or complementary. Leave them separate when you want flexibility in how you group them at planning time.
  4. Select Tasks That Fit Your Available Capacity
    With all tasks properly sized between 1 and 5-7 Pomodoros, select a set of tasks whose total estimated Pomodoros does not exceed your available daily capacity. Write them on your To Do Today Sheet in priority order.
    Pro tipIf the total estimate exceeds available Pomodoros, drop the lowest-priority tasks. Never plan to work more Pomodoros than your timetable allows.

Checklist

Saved in your browser

Examples

2 cases
Lucy Combining Phone Calls into One Pomodoro

Lucy had three tasks each estimated at well under one Pomodoro: calling Laura to invite her to a seminar, calling Mark about a laptop, and calling Andrew about concert tickets. Individually, none justified a full 25-minute interval. She combined the two most similar calls (Mark and Andrew) into one estimated Pomodoro, and planned to batch Laura's call with another small task later.

OutcomeBy combining complementary micro-tasks, Lucy maintained clean estimation units and avoided fragmentary tracking. Each Pomodoro represented a meaningful chunk of completed work rather than a collection of unrelated scraps.
Breaking Down a Multi-Day Writing Project

A writer estimates that producing a 10-page article will take approximately 12 Pomodoros total. Rather than planning '12 Pomodoros of writing,' he decomposes incrementally: research and outline (2 Pomodoros), draft the introduction (2 Pomodoros), develop each main section (2 Pomodoros each for 3 sections = 6 Pomodoros), and edit and condense (2 Pomodoros).

OutcomeEach sub-task was independently estimable and deliverable. The writer could finish each component, assess quality, and adjust the plan before moving on. Estimation accuracy improved because each 2-Pomodoro chunk was far easier to predict than the original 12-Pomodoro monolith.

Common mistakes

3 traps
Breaking Down Tasks by Size Instead of by Value
The most common mistake is splitting a large task into arbitrary equal-sized chunks (e.g., 'write pages 1-5' and 'write pages 6-10'). The correct approach is incremental decomposition where each sub-task delivers value independently. A better breakdown might be: 'draft the introduction and thesis,' 'develop the first supporting argument with evidence,' and so on.
Leaving Large Tasks Intact Because Breaking Down Feels Like Overhead
People resist decomposition because it takes effort upfront. But the payoff is immediate: better estimates, less procrastination, clearer thinking, and the motivational boost of completing tasks throughout the day. The cost of not breaking down is consistently worse estimation, delayed starts, and a feeling of being stuck.
Combining Unrelated Small Tasks
When grouping sub-Pomodoro tasks, combine similar or complementary activities (all phone calls together, all email replies together). Combining unrelated tasks (a phone call, a code review, and desk cleaning) creates a disjointed Pomodoro that reduces focus and makes tracking less meaningful.

Origin story

How this framework came to be

Cirillo developed these rules through years of observing how task size affected both estimation accuracy and motivation. He found that activities exceeding 5-7 Pomodoros were reliably harder to estimate and more likely to trigger procrastination. Conversely, sub-Pomodoro tasks created fragmented tracking and planning. He drew on Abraham Maslow's work on motivation (accomplishing several activities daily that are neither too simple nor too complex) and Tom Gilb's principle that breaking down activities should aim for incremental paths with the lowest possible complexity, not merely smaller arbitrary chunks.

Source

Traced to primary
Source · BOOK
The Pomodoro Technique
Francesco Cirillo · 2006
Open source →

Related frameworks

Browse all Productivity →