How to Start a Project You Keep Delaying
A project is the hardest thing to start
A single task is easy to picture starting. You open the document, you make the call, you send the email — the first move is obvious, and the finish line is close enough to see. A project is different. It has no obvious first move and no finish line you can point at. “Start the side project.” “Finally write the book.” “Sort out the garden.” Where exactly do you begin? The project sits there for weeks, not because you don't care about it — you probably care a lot — but because “start” has no address. There is no door to walk through, only a field.
And unlike a task with a boss or a deadline, nobody is waiting. No one will ask where it is. A project you keep delaying is usually one nobody else knows about, with a deadline nobody else can see. That privacy feels comfortable. It is also exactly why the project never starts: there is no cost to another day of not starting, and no moment when starting becomes easier than waiting.
The two things a delayed project is missing
Most delayed projects are missing the same two things, and neither one is motivation. The first is a first visible result — something that exists in the world once you have started, even in rough form: a page of outline, a sketch, a paragraph, a list of the chapters. Until you can name that result, “start the project” means nothing your hands can do. The second is a deadline someone else can see. A private deadline is a wish; a deadline another person knows about is a commitment. You don't need a harsh deadline. You need one that exists outside your own head.
- A first visible result: what will exist, in the world, after the first hour of work? If you can't describe it in one sentence, the project isn't ready to start — the first move is.
- A deadline someone else can see: a date by which one other person will see the first result. Not the finished project — the first rough piece.
- A smallest move that produces the result: the one action that makes the first visible thing exist. Open the document and write the headings. Sketch the layout on paper. Record the first voice note.
Name the first visible result
Sit with the project for five minutes and answer one question: what is the smallest thing that would prove to you that this project has begun? For a book, it might be a single page of rough outline — not a chapter, a page. For a website, a one-paragraph description of what it does. For a room you're redoing, one corner cleared and measured. The result should be small enough to make in one sitting and visible enough that you can point at it afterwards.
This is the move that separates a delayed project from an overwhelming task. Breaking a task down is about making the work manageable. Naming a first visible result is about making the start real — giving the project a first object, a first piece of evidence that it exists outside your head. Once that piece exists, the project stops being an idea and becomes a thing with a shape. The second piece is always easier than the first, because now you are adding to something rather than conjuring it from nothing.
- Write the result down as a sentence: “After the first hour, I will have a one-page outline.”
- Make it small enough to finish in one sitting — if it takes a weekend, it isn't a first result, it's a milestone.
- Put it somewhere visible: on the desk, on the fridge, in the file. The project should have a place in the world, not just in your head.
Make the deadline real
A project with no deadline is a project that can always start tomorrow, and tomorrow never runs out of excuses. The fix is not to punish yourself with an impossible date. It is to make the date real by giving it to someone else: send a friend the first result by Friday, book a 20-minute review with a colleague, tell your partner you'll show them the outline on Sunday. The other person doesn't need to judge the work — they just need to expect it.
External check-ins work where private promises don't, because they move the deadline out of the part of your brain that negotiates with itself. You can always renegotiate with yourself; it is much harder to tell someone you simply didn't do the thing. Pick a check-in that is close — this week, not next month — and small: one person, one result, one date. When the check-in arrives, show what you have, even if it is rough. Rough is the point. The project is allowed to start badly; it is not allowed to stay invisible.
- Tell one person what they'll see and when — “I'll send you the outline by Friday.”
- Book the check-in in the calendar, not in your head — a date that exists outside your intentions.
- If the date slips, move it once and say so out loud. A moved deadline is still a deadline; a silent one was never real.
Where start/ish fits
start/ish is one option built for the minute before beginning — and a delayed project starts the same way any task does, with a first move that feels too big. You can unload what's circling in your head — the project, the fog around it, typed or spoken, messy is fine — and it hands back one small, editable next step you can begin in two minutes, with a gentle timer running. That step can be the project's first visible result itself: “Write the one-page outline” or “Sketch the layout.” Small enough to begin. Afterwards it asks how it went: kept going, made a dent, got set up, or need something smaller? Every honest answer counts.
Free to try, on the App Store for iPhone now, with a 7-day free trial on the yearly plan.