And why nobody talks about the first ten days.
Preparation decides everything — in surgery as well as in projects.
Most people believe projects fail at the end.
When deadlines slip.
When budgets explode.
When coordination collapses.
When everyone is frustrated.
But the truth is different, and far more uncomfortable:
Projects do not fail in month six.
They fail in week one.
The collapse begins quietly, long before anyone sees the first Gantt chart.
Long before testing.
Long before rollout.
Long before steering committees and escalations.
It happens right at the start, in the phase that feels slow, boring, and “not productive enough”: the initiation.
And almost nobody protects this phase the way it deserves.
The silent failure: why the first ten days decide everything
If you analyse project failures honestly, the root causes are always the same:
- unclear goals
- poorly defined or shifting requirements
- misaligned expectations
- missing decisions
- wrong assumptions
- incomplete understanding of the starting point
- no structure
- weak stakeholder management
- missing or underestimated risks
By the time these symptoms show up, the project looks “in trouble”.
But the trouble was created months earlier.
The problems you see at the end are created in the beginning.
The illusion of clarity
Sponsors love high-level definitions.
“We need a new onboarding.”
“We need automation.”
“We need efficiency.”
“We need a new product.”
Clear, simple, elegant.
Until you ask real questions:
- For which customers?
- With which constraints?
- With which time horizon?
- With which quality expectations?
- With what level of flexibility?
- With which legacy system limitations?
- With which regulatory boundaries?
Suddenly, the “clear vision” becomes blurry.
Ambition is not a project plan.
And direction is not execution.
The gap between intention and reality is born right here.
The magic moment nobody protects
In every project, there is a short window, usually at the very beginning, where shaping the direction is still easy:
- decisions are inexpensive
- people listen
- assumptions can be challenged
- scope is still open
- alignment is possible
After this window closes, everything becomes harder.
Every adjustment becomes a negotiation.
Every correction causes friction.
Every change becomes expensive.
This is why:
If you miss the magic window, the project will punish you later, with interest.
Agile is not “don’t think, just start sprinting”
There is a widespread belief that this problem only applies to classic, plan-driven waterfall projects.
It doesn’t.
It applies equally, and sometimes even more, to agile projects.
Agile doesn’t save you from unclear goals.
Agile doesn’t save you from missing alignment.
Agile doesn’t save you from weak initiation.
And agile definitely doesn’t save you from poorly defined or shifting requirements.
One of the biggest misunderstandings about agile is the idea that you can:
- just start
- just sprint
- figure it out later
- discover the scope as you go
This is the fastest way to burn money.
Agile needs clarity too, just at a different level.
You do not need 100 percent detailed requirements at the start. But you do need:
- a clear product vision
- a clear problem statement
- a defined customer group
- a clear target outcome
- a high-level architecture
- boundaries, constraints and non-negotiables
- a shared understanding of what success looks like
Without this foundation, agile becomes exactly the opposite of what it was designed to be:
a machine that burns time, budget and resources, sprint by sprint.
Teams deliver work, but not progress.
Velocity goes up, but value goes down.
The backlog grows faster than the product.
And every sprint brings new surprises that should never have been surprises at all.
Why?
Because the team is only looking two weeks ahead instead of understanding the full shape of what needs to be built.
Iterative delivery still needs directional clarity.
Agile requires continuous refinement, yes.
But it also requires a strong top-down understanding of the product.
You can iterate the how.
You cannot improvise the why.
Without a clear destination, agile becomes motion without progress.
And then the same rule applies:
If you start unclear, you will stay unclear, just faster.
A real story: The project that was perfect… until it wasn’t
A couple of years ago, a large organisation rolled out a new automation system across its branch network.
Everything had been tested.
Integration had run smoothly.
The rollout team was ahead of schedule.
Confidence was high.
Until the evening of the first real rollout day.
Suddenly, during the day-end process, the first message came in from one of the branches.
The branch colleagues were in full worry:
Branch 1:
“Something is off with the system.”
Branch 2:
“Something in the process isn’t right.”
Branch 3:
“The program didn’t behave correctly, we have an issue.”
The messages kept coming. A pattern became visible.
Not a single technical error.
Not a single software defect.
Everything worked exactly as designed.
The real cause?
People did not fully understand how to operate the new workflow yet.
Rare scenarios were handled incorrectly.
Some process steps were not followed as intended.
Teams were not confident with edge cases.
Routine turned into uncertainty, fast.
And a perfect project suddenly became a crisis project.
The timeline had to be extended.
Workload increased.
Teams had to be trained again in detail.
The organisation recovered in the end, but at a price.
The lesson:
It is not always technology that fails. Sometimes change management fails even faster.
And change management is part of the initiation phase, not the end.
The real job of a project manager
People often confuse project management with:
- Strict deadlines
- Gantt charts
- Clear reporting
- Aligned templates
- Governance rituals
All important.
None decisive.
The real job is different.
1. Clarity
Define success in painful detail.
Not the vision, the execution reality.
2. Discipline
Ask the uncomfortable questions in week one.
The ones everyone avoids.
The ones that change the trajectory.
3. Communication
Not just reporting.
Not just status updates.
Real alignment.
Who does what.
By when.
Why.
What is risky.
What is changing.
What is non-negotiable.
This is what separates successful from struggling projects.
The hard rule nobody likes, but everybody learns the hard way
If I compress years of project experience into one sentence:
The quality of the first ten days determines the quality of the next ten months.
If you get the initiation right:
- clear scope
- strict alignment
- real understanding of the starting point
- defined success criteria
- honest risk assessment
- early team clarity
- a communication rhythm
- a structure that makes work parallelisable
you eliminate 80 percent of future problems.
If you skip it:
You will fight the consequences until the very end.
The quiet skill that separates amateurs from professionals
Most project managers rush into execution.
Professionals do not.
They cut through the noise.
They operate like surgeons.
They open the problem.
They see behind the lines.
They eliminate uncertainty.
They prepare the terrain for fast execution.
Because they know:
Speed without clarity is not speed.
It is noise.
The best project managers reduce noise.
Then they accelerate.
If you want a project to finish fast, do not start fast
This is the paradox of execution:
The more disciplined, rigorous and precise you are at the beginning,
the faster and more stable everything becomes afterward.
Protect the initiation phase.
Treat the first ten days like gold.
Ask the questions nobody wants to hear.
Challenge the assumptions that feel “obvious”.
Surface the risks others prefer to ignore.
Align with brutal honesty.
That is where projects succeed.
Not at the end.
At the beginning.
Because:
Projects do not fail at the end.
They fail at the start.
But if you master the start,
you win the entire project.