How to Recognize When a Long Project Is Being Avoided Inside the SessionUpdated a month ago
"You lit the candle for the long project. The file is open. Time is moving. Nothing real is advancing. This is common. It is also fixable from inside the session, without drama. Use the flame as your frame. You are here to move the project one concrete step forward before it dies.
WHEN LONG PROJECT WORK STALLS
Long projects invite safe activity that looks like progress but avoids risk. Inside the 120 minutes, avoidance often hides as “getting ready.” It keeps you busy while the candle burns down. Notice it early and steer back to execution.
COMMON IN-SESSION AVOIDANCE PATTERNS
- Re-reading old drafts instead of producing the next section.
- Renaming files, cleaning folders, or re-tagging notes.
- Planning the next step in detail but not taking it.
- Collecting sources or “just one more” reference.
- Tweaking tools, templates, or settings.
- Polishing sentences you already wrote while the new material waits.
- Opening messaging or browser “for context.”
QUICK TEST: PREP OR AVOIDANCE?
Ask one question: Does this action create a new, countable unit for the project in the next 15 minutes?
- If yes, it’s preparation that serves execution. Example: outlining three bullet points you will immediately draft.
- If no, it’s likely avoidance. Example: reorganizing your entire notes archive “so drafting is easier later.”
RETURN-TO-EXECUTION TRIGGER
Use a simple, physical trigger to break avoidance:
- Close all nonessential windows.
- Put anything unrelated back on the shelf.
- Say out loud, “What am I making in the next 15 minutes?”
- Write one clear output target: “Draft paragraph on methods,” “Implement function X,” “Sketch slide 2.”
- Start a 3-minute ramp: fingers on keys, code compiling, pen moving. No switching. Produce a rough first pass.
If you stall again, repeat the question and set a new 15-minute output.
RITUAL ADJUSTMENTS MID-FLAME
- Re-ground in silence. If music or podcasts started creeping in, return to quiet.
- Phone stays away. If it left the shelf, put it back and out of reach.
- Shrink the scope. Large step too heavy? Carve a smaller unit that still counts.
- Time-box any necessary prep to 5 minutes, then move. When the box ends, you execute.
EXAMPLES IN PRACTICE
Writing: You keep re-reading chapter one. Trigger: “Write 150 new words on chapter two now.” No polishing for 15 minutes.
Research: You are collecting PDFs. Trigger: “Extract three findings into the draft table now.” No new downloads.
Design: You’re rearranging layers. Trigger: “Rough shape the header in grayscale.” No font hunting.
Engineering: You’re refactoring helpers. Trigger: “Write a failing test for feature Y.” Then implement.
WHEN PREP IS LEGITIMATE
- It is tightly bounded.
- It flows directly into making.
- You can point to a new artifact at the end: an outline, a test, a dataset slice.
If it soothes but does not ship, shelve it.
END THE SESSION CLEANLY
When the flame dies, stop. Note the concrete unit you finished. Park the next small step on top of the file. Put the tin on the shelf. This protects attention, builds trust, and makes the next lighting simpler.
If you find yourself avoiding project work inside a focus session, use the single question and the 3-minute ramp. Keep the ritual. Keep the promise. Produce the next unit."