How to Break Large Tasks Into Pieces That Fit One SessionUpdated a month ago

"Large projects feel vague until you name what “done” looks like and cut the work into 120-minute pieces. Your candle gives you the container. Your job is to make each flame produce a specific, finishable output.

DEFINE THE FINISH LINE

Write the final deliverable in one sentence. Make it concrete and visible.

- “Submit 12-page grant proposal with budget and letters.”

- “Ship v1 landing page with working form and analytics.”

If you cannot describe the finish line, start with a scoping session as the first piece.

WORK BACKWARDS INTO 120-MINUTE UNITS

Trace the path from finish line to now. Look for natural outputs you can complete before the flame dies. Think in verbs and artifacts:

- Outline, draft, edit, compile, test, decide, package.

- Brief, list, sketch, stub, proof, query, export.

WRITE A SESSION-SIZED OUTPUT

Before you strike the match, set a single session output with a clear stop state:

- “Outline three sections with bullet points in the doc.”

- “Implement signup form POST and handle success/fail locally.”

- “Select final 12 sources and capture quotes into notes.”

If it cannot be unambiguously finished in 120 minutes, it is still too big.

USE CLEAN EXAMPLES

For writing a report:

- S1: Decide structure. Produce a one-page outline.

- S2: Draft Methods section to full length.

- S3: Draft Results with two figures placed.

- S4: Edit for clarity and trim 10%.

- S5: References formatted and checked.

For a landing page:

- S1: Write copy for hero, features, CTA in one doc.

- S2: Build hero section in code with styles.

- S3: Build features section and mobile layout.

- S4: Hook form to backend and validate.

- S5: Add analytics snippet and test events.

PROTECT THE BOUNDARY

Follow the rules: strike the match, put the phone away, work in silence. Do not chase side ideas. Park them on a note. Your only job is the named output before the flame dies.

CHAIN SESSIONS ON THE SHELF

After each session, label the empty tin or its card with the output you completed. Line them up on the shelf in order. This creates a visible arc from idea to finish. It also makes it easier to restart after a missed day: look at the last labeled piece and choose the next one.

WHEN A PIECE IS STILL TOO BIG

Shrink scope, not standards:

- Reduce breadth: draft two subsections, not five.

- Fix depth: implement the interface, stub the backend.

- Timebox exploration: “Find three viable options and pick one.”

END-OF-FLAME CHECK

When the flame dies, stop. Mark done or not done. If not done, rewrite the next session output to a smaller slice. This is how you learn how to break big tasks for focus sessions and keep promises to yourself, one quiet candle at a time."