A project without visible boundaries forces your brain to rebuild the entire map of it, from scratch, every single time you approach the work. That reconstruction is invisible and it is expensive—by the time it is done, a meaningful share of the energy you had available for actually making something is already spent, and what is left over does not feel like enough to start with. From the inside, this reliably gets misread as low motivation or poor discipline. It is neither. It is a structural cost, paid over and over, for a project that has never been broken into anything smaller than itself.
Cognitive blocks: when the failure is in the process, not the person
This sits in what the research literature calls cognitive blocks—failures inside the working process itself, distinct from emotional or motivational causes. Mike Rose's 1980 research on writers identified one specific driver worth naming directly: rigid, self-imposed rules that get treated as unbreakable laws. "The introduction has to be finished before I write anything else." "Every session has to produce something usable." These rules feel like standards, but functionally they behave like locks—you cannot proceed until the rule is satisfied, and when two such rules quietly contradict each other, the result is a freeze that has nothing to do with willpower.
Robert Boice's 1985 work adds a second, closely related failure mode: planning problems in either direction. Over-planning drafts an ever-more-detailed structure and never actually starts building inside it. Under-planning dives into something genuinely complex with no scaffolding at all and hits chaos almost immediately, which then gets misread as a sign the whole project was a bad idea rather than a sign it needed a plan before it needed effort.
"Work on the project" is not a next action. It never was. 1
Premature editing eats the same budget from a different angle
There is a second cost stacking on top of scope: trying to generate and judge work in the same pass. These two operations compete for the same limited mental space, and the judging function nearly always wins the fight, which is one reason a large, ambiguous project can feel paralysing even to someone who is clearly skilled enough to do it. Separating drafting from editing into genuinely different sessions is one of the better-evidenced fixes across this entire research base, and it costs nothing beyond the discipline of doing it in that order.
Turn a project into a sequence
The practical response is to convert one enormous, undifferentiated project into a short sequence of small, well-defined ones. Define the actual outcome in concrete terms. Reduce the active scope to only what is being worked on this week, not the whole eventual thing. Expose the real dependencies—what has to happen before what—so the plan reflects the true shape of the work rather than an aspirational one. Separate decisions about direction from the daily act of making, since re-deciding the whole project every morning is its own quiet drain. And give every single work session a default entry point that requires no decision to start: not "work on the novel" but "revise pages twelve through fifteen."
None of this is about lowering the ambition. A good system does not make the work smaller or safer—it protects the limited attention you have for the parts of the project that genuinely require creative judgement, instead of spending that attention on reconstructing the map every time you sit down.
A project that has outgrown its structure sits in Structure & Workflow on our map. If you want help cutting one down to a workable sequence, that is what project support does.