When a project misses its target, the post-mortem usually starts with delivery: the schedule slipped, ownership was weak or communication broke down. Those failures matter, but many are symptoms of decisions made before the first task was assigned.
A vague problem produces competing interpretations. Weak success criteria reward visible output instead of meaningful change. An untested assumption turns a confident plan into an expensive guess.
The brief is not the problem
“Build a customer portal” describes a solution. It does not identify whether customers struggle to find information, distrust the support process or simply prefer speaking to a person. If the real problem is unclear, the team can only optimise the proposed deliverable.
A project begins responsibly when the problem can survive questions before the solution consumes resources.
Three failures that happen before kickoff
The problem belongs to nobody specific
Broad claims such as “engagement is low” conceal who is affected, when the difficulty occurs and why it matters. Useful problem statements locate an observable gap.
Success is defined as completion
Launching on time proves that work was delivered. It does not prove that the condition improved. Define what should change after delivery and how soon evidence should appear.
The riskiest assumption is left untested
Teams often validate technical feasibility while assuming demand, adoption or organisational support. The most dangerous assumption is usually the one the plan treats as obvious.
Earn the right to execute
A short discovery phase is not delay when it can prevent months of disciplined waste. Interview the people experiencing the problem, inspect existing evidence and test the central assumption with the smallest credible experiment.
Good execution begins before the plan. It begins when leaders make it safe to question whether the project deserves to exist in its proposed form.