The Project Fails Before Anyone Shows Up

Why the cheapest insurance in project management is also the one everyone skips

After 10 years running capital projects on factory floors and residential job sites, I’ve learned that most projects don’t fail in execution. They fail before anyone ever picks up a tool.

They fail in a fifteen-minute conversation that nobody bothered to have.

Here is the pattern I’ve watched play out more times than I can count: someone has a project idea. It sounds good. Leadership is excited. Everyone wants to move fast. So the team skips straight to planning — timelines, budgets, contractors — and nobody stops to ask the boring questions.

• What problem are we actually solving?

• Who needs to sign off on this?

• What does “done” even look like?

Six months later, the project is over budget, behind schedule, and half the stakeholders are asking why nobody told them about the electrical work. That’s not a planning failure. That’s an initiation failure. And it’s almost always preventable.

Initiation is the cheapest insurance you’ll ever buy

In project management, there are five process groups: Initiation, Planning, Executing, Monitoring & Controlling, and Closing. Everyone loves talking about Executing — it’s where the visible work happens, where you can point to progress. Nobody wants to slow down for Initiation, because on paper it looks like paperwork.

But Initiation is where you define the project and identify who actually has a stake in it. Skip it, or rush it, and you’re not saving time — you’re just moving the cost of that shortcut downstream, where it gets more expensive to fix.

I learned this the hard way on a garage addition early in my career. The scope felt “obvious” going in. It wasn’t. Halfway through, we discovered nobody had confirmed electrical loads with the client, and what should’ve been a two-day fix turned into a two-week delay. The cost wasn’t just money — it was trust.

The two documents that would have saved me

If I could hand my younger self one thing, it’d be a simple system for capturing project ideas before they become expensive mistakes. Two documents do almost all the work:

The Project Ideation Log. This is just a running backlog — every project idea in one place, with rough budget, stakeholders, and target dates attached. It doesn’t need to be fancy. It needs to exist. Whoever’s watching the business — a plant manager, a department head, a PM — should be able to glance at it and know what’s coming.

The Project Approval Form. One to two pages, max. Before anyone commits real time to a project, someone writes down the business case: why this, why now, roughly what it’ll cost. This gets reviewed by the people who control the budget. If the project’s not viable, you find out here — not three months in.

Only after a project clears that gate does it earn a full Project Charter: the document that nails down scope, budget, timeline, risks, and who’s responsible for what. Think of the charter as the contract everyone agrees to before the real work starts. It should answer the unglamorous questions up front — who needs to be notified, what happens if there’s an electrical scope nobody planned for, who’s paying for shipping, who signs off on the final result — so those questions don’t ambush you at week six.

The best scope documents tell a story

Here’s something that took me years to internalize: a good project scope isn’t a checklist. It’s a narrative. It should read like you’re walking someone through the project from start to finish, so clearly that a stranger could pick it up and understand exactly what “success” looks like.

The checklist still matters — the risks, the vendor terms, the safety equipment, the RACI chart defining who’s Responsible, Accountable, Consulted, and Informed. But checklists don’t build alignment. Stories do. If your stakeholders can’t picture the finished project from reading your scope, you haven’t finished writing it.

Walk the job before you price the job

One habit I’d tell any new PM to steal: walk the site with multiple contractors before you lock in scope. It’s not just about getting competitive bids — though that matters. It’s that every contractor who walks the job sees something you missed. A subject matter expert standing in the actual space will catch a constraint or a risk that never would have surfaced in a conference room.

The real lesson

None of this is about paperwork for its own sake. It’s about respecting the fact that a capital project — a new home, a factory line, a piece of equipment with a useful life measured in years, not days — deserves more than good intentions and a start date.

Slow down at the beginning so you don’t have to slow down, apologize, and re-explain yourself at the end. That’s the whole trade. It’s a good one.