Why Big Projects Stall Before They Start
The project sits at the top of your list for a week.
You open the document. Read the brief again. Close it.
Not because you’re avoiding the work. Because there’s no obvious first move.
A vague project doesn’t get worked on. It gets postponed.
Big Isn’t the Problem. Undefined Is.
“Redesign the onboarding flow” isn’t a task. It’s a category.
Your brain can’t start a category. It can only start a task with a clear next action.
Until the project has been broken into something small enough to finish in an afternoon, stalling isn’t a discipline problem. It’s the correct response to an unclear instruction.
Why “Just Start” Doesn’t Work
Motivation advice says to just begin. Momentum will follow.
But you can’t build momentum on a task you can’t picture finishing.
What actually breaks the stall is structure, not willpower.
Breaking It Down Properly
Three questions turn a stalled project into a working one:
- What are the actual sub-tasks, not the category?
- What depends on what?
- Where is this most likely to stall again?
Answer those honestly, and the project stops being one big unclear thing. It becomes a sequence of small, finishable ones.
That’s the whole method behind the Task Breakdown Worksheet: turning a category into a queue.
The First Move Is Always Small
Not the whole project. Just the next piece.
Small enough to finish today.
That’s how big work actually starts.
