Why Most Projects Fail Before They Start
Project failure is rarely a surprise in retrospect. The root causes are almost always visible in the original plan — or the absence of one. A task list with dates and no scope statement. A timeline built before dependencies were understood. Ownership distributed across a team without a RACI to make it explicit. Risks that were discussed once in a kick-off meeting and never written down. These are not failures of execution. They are failures of planning that execution then has to absorb.
Research on project failure consistently identifies the same causes: unclear scope that allows requirements to expand indefinitely, unrealistic timelines built without understanding the full work, ambiguous ownership that creates gaps and duplications, and risks that were foreseeable but not mitigated. Each of these is a planning problem, not a doing problem — and each is preventable with the right framework applied at the start.
Paul — the KissMySkills project management agent — applies that framework in one intake session. The output is a complete project plan built from the methodology that experienced project managers apply: scope statement with explicit exclusions, work breakdown structure, milestone timeline on the critical path, RACI matrix, risk register with mitigation actions, and stakeholder communication plan. Built at the start, before a single task begins.
What a Complete Project Plan Actually Includes
Most documents called "project plans" are task lists with dates and a name at the top. A complete project plan has six components that the task list approach omits — each addressing a different failure mode.
A scope statement that defines what is in scope and, equally importantly, what is explicitly out of scope. Without explicit exclusions, scope expands to fill whatever time and budget are available, driven by stakeholder requests that are individually reasonable and collectively ruinous to the timeline.
A work breakdown structure that decomposes the project deliverables into workstreams, then into tasks, until every piece of work is assigned and sized. The WBS is the tool that surfaces the work that is always underestimated because it lives between the major milestones — the integration testing, the sign-off process, the documentation, the training, the transition activities.
A milestone timeline built on the critical path — the sequence of tasks where any delay delays the project end date. Most project timelines are built from a desired end date backwards, without identifying which path through the work is truly critical. When a non-critical task slips, it is a problem. When a critical path task slips, the entire project slips.
A RACI matrix that assigns Responsible, Accountable, Consulted, and Informed roles for every significant deliverable. The tool that makes ownership explicit before execution begins, rather than discovering at week four that two people thought the other was responsible for a deliverable that nobody completed.
A risk register that documents identified risks, rates their likelihood and impact, assigns mitigation actions, and names an owner for monitoring each risk throughout the project.
A stakeholder communication plan that specifies who receives what update at what frequency — so stakeholders are never surprised by project status and the project manager is never caught without a prepared update for an important meeting.
Scope Before Timeline: The Most Violated Rule in Project Management
Timelines built without clear scope are not timelines — they are estimates with false precision. The most common reason projects miss deadlines is not poor execution by the team. It is that the timeline was built before the full scope was understood, or before all the dependencies were identified, or before anyone had asked the questions that surface the work that does not appear in the initial requirements.
Paul asks about deliverables, dependencies, constraints, and explicit exclusions before building any timeline. The scope statement is the first output — confirmed and agreed before a single milestone date is set. Scope creep is significantly easier to prevent than to manage after it has started, and the explicit exclusions in the scope statement give the project manager the authority to say "that is out of scope" when new requests arrive. Without documented exclusions, every "that sounds simple, can we add it" conversation becomes a negotiation.
RACI: The Tool That Prevents the Diffusion of Responsibility
The diffusion of responsibility is the project management equivalent of the bystander effect: when multiple people are associated with a deliverable without clear ownership, each assumes someone else is handling it. The result is a deliverable that is nobody's problem until it is everyone's problem — discovered late, rushed, and blamed on the team.
A RACI matrix prevents this by making ownership unambiguous before execution begins. Responsible is the person doing the work. Accountable is the single named person who answers for the result — there can only be one. Consulted are the people whose input is required. Informed are the people who need to know the status. Paul builds a RACI for every significant deliverable across every workstream in the project, covering every stakeholder who has a role.
The RACI is designed to be walked through at the project kick-off meeting — not sent as a document for asynchronous review, but discussed as a team so every person confirms their role, understands their accountability, and has the chance to raise concerns before the project begins. Conflicts in the RACI discovered at kick-off take five minutes to resolve. Conflicts discovered mid-project take weeks.
Risk Register Built Before the Risks Materialise
The best time to build a risk register is at project initiation, when the team's attention is forward-looking and options are still open. Risks identified at the start can be mitigated. Risks identified when they are actively occurring can only be managed — and the options are narrower, the cost is higher, and the impact on the timeline is worse.
Paul produces a risk register with identified risks, likelihood and impact ratings (High/Medium/Low), specific mitigation actions for each risk, and a named owner for monitoring each risk throughout the project lifecycle. The risks identified include both the obvious ones — key resource availability, third-party dependency delays — and the category-specific risks that experience suggests are most common for this type of project.
For Projects Already in Trouble
Paul also diagnoses and recovers struggling projects — not just plans new ones. For a project that is behind schedule, over budget, or suffering from uncontrolled scope expansion, the intake questions surface the root cause: unclear original scope, an unrealistic timeline, ambiguous ownership, or risks that materialised without mitigation plans in place. The recovery plan addresses the actual cause rather than just compressing the remaining schedule — because schedule compression applied to a fundamentally flawed plan produces a different version of the same failure.
How to Start a Project Planning Session with Paul
Load the Paul skill file into Claude Projects. Paste the activation prompt. Paul asks intake questions about the project: the goal, the deliverables, the deadline, the team composition, known dependencies, and constraints. Answer specifically — the more detail provided about the actual project, the more accurate the plan. The full session produces a complete project plan in 30 minutes. Paul works with Claude, ChatGPT, or any AI chat that accepts system prompts.
The agent behind this guide. Give Paul your project and get a complete plan — scope statement, work breakdown, RACI, critical-path timeline, and risk register — in one session.