How do I avoid the trap of over-planning before starting?

Set a time limit on the planning phase. Give yourself one or two days to get clear on the outcome and the first few steps, then start. Planning beyond that point usually produces detail that becomes irrelevant once real work begins and reality pushes back.

Method

How to Start a New Project Well

Q: What should I do in the first week of a new project?

Clarify the outcome rather than jumping straight to tasks. What does done actually look like? What are the constraints on time, budget, and scope? Who else is involved and what do they need from you? Getting those questions answered early prevents a significant amount of rework later.

Q: How do I fit a new project into an already full week?

Before adding it to your weekly plan, be honest about what it will displace. A new project does not add hours to the week. It competes with what is already there. Deciding explicitly what gets less attention is a better approach than assuming you will find the time.

The first week of a new project sets more than you realise. The decisions made before real work begins shape how easy or difficult everything that follows will be.

22 July 2026 · 5 min read

Most projects fail quietly, long before the deadline. They fail because the outcome was never defined clearly enough, or the scope was agreed to without anyone checking whether the time existed to deliver it, or the first two weeks went in the wrong direction and nobody noticed until the correction became expensive.

A good project start does not prevent all of this. But it reduces how often it happens, and reduces how bad it is when it does.

Get clear on what done looks like before anything else

The most common source of project problems is starting without a shared understanding of what the finished thing actually is. This sounds obvious and it is, but it is also the step that gets skipped most often because people are keen to start working.

Before you open a document or book a meeting, write down in plain language what the project will have produced when it is finished. Not the steps. The outcome. What will be true that is not true now? What will someone be able to do or have that they cannot currently?

If you are working with other people, share that description and ask if they recognise it. Often they have a slightly different version in their head, and finding that out in week one costs far less than finding it out in week six.

Name the constraints upfront

Every project has constraints on time, scope, and resources. Most projects have them but do not name them, which means they get discovered the hard way partway through when something becomes impossible.

Spend an hour in the first week asking: what are the real limits here? What cannot change? What would cause this project to fail? What has gone wrong on similar projects before? These are not comfortable questions but they are much cheaper to ask early than late.

Plan the first two weeks, not the whole project

Detailed long-range project plans tend to become fiction within the first month. Reality pushes back, the scope shifts, something takes longer than expected. Planning further than you can see clearly is mostly an exercise in writing things down that you will have to rewrite.

A more reliable approach is to plan the first two weeks with real specificity and leave the rest at a high level. What needs to happen in the first fortnight to prove the project is on track? What questions need to be answered? What early output demonstrates progress?

After those two weeks, you have real information to plan the next phase with. That plan will be considerably more accurate than one made before the work started.

Decide what the project displaces

A new project does not add hours to the week. It competes with what is already there. One of the questions worth asking before you start is: what gets less attention because this exists? Which existing priorities move down the list?

This is not a reason not to take on new things. It is a reason to be honest about what is already there. Making the trade-off explicit prevents the slow accumulation of commitments that leads to everything taking longer than it should.

Your weekly planning session is a good place to work this out. When a new project enters the picture, the Sunday reset is where you decide how it fits alongside everything else, rather than assuming it will find its own room.

Common questions

What should I do in the first week of a new project?

Clarify the outcome before jumping to tasks. What does done look like? What are the constraints? Who else is involved and what do they need? Getting these answered early prevents significant rework later.

How do I avoid over-planning before starting?

Set a time limit on the planning phase. One or two days to get clear on the outcome and the first steps, then start. Planning beyond that usually produces detail that becomes irrelevant once reality pushes back.

How do I fit a new project into an already full week?

Be honest about what it will displace. A new project competes with what is already there. Deciding explicitly what gets less attention is better than assuming you will find the time.

See your full week before it starts

Weekly Reset includes a calendar review that helps you work out where a new project actually fits. Free forever.