Focus

Choose a sprint that matches the work.

A 25-minute session is a useful default, not a rule. The right duration depends on how clearly you understand the next action and how expensive it is to regain context after a break.

Use 10 minutes to find the next action

When a task feels vague, a long timer can create more avoidance. Use ten minutes to inspect the material, write down unknowns, and define the smallest visible next step. The goal is not to finish; it is to remove ambiguity.

Use 25 minutes for ordinary production

Writing a section, reviewing a small change, processing a group of messages, or practicing a familiar skill fits a standard session. Stop with enough energy to note where you will resume. That note reduces the restart cost after the break.

Use 45 to 60 minutes for deep context

Complex debugging, design, and analytical writing often need a longer ramp. A short session may end just as the mental model becomes useful. Choose a longer block only when notifications and interruptions can actually remain off.

Measure output, not endurance

A timer is a boundary for attention. It is not a score for how long you can stay seated. At the end of a session, record the artifact produced: a decision, paragraph, test, sketch, or resolved question. If several sessions end without a visible artifact, reduce the scope before increasing the duration.