One of the most damaging yet least discussed problems in project management is that most organizations lack a clear understanding of how to initiate a project.
Sure, they know how to announce one. They know how to assign people to it. They know how to make a PowerPoint deck, hold a kick-off meeting, and tell everyone how “critical” it is to the future of the company.
But proper initiation? A clear, disciplined process to validate whether the project is even worth starting? That part is missing in action.
Here’s what actually happens in most companies: someone in the leadership chain has a bright idea in the shower, sees a competitor doing something shiny, or hears a client complain about something once. It’s mentioned in a meeting, heads start nodding, and suddenly the phrase “Let’s projectize it” is thrown into the air. Without more than a few minutes of thought, people are assigned, budgets are estimated, and the wheels start turning.
And just like that (without a clear problem statement, without measurable goals, without alignment to the organization’s strategy), you’ve got a live project.
It’s a cultural sickness.
We’ve created environments where the speed of starting something is valued more than the quality of what we start. Leaders want to be seen as decisive. Teams want to be seen as responsive. The problem? Decisive and responsive without critical thinking is just another phrase for ‘reckless.’
Here’s the ugly truth: starting the wrong project is far more damaging than killing a good idea too early. Why? Because every project consumes resources (time, money, focus, people), and those are finite.
Every hour your team spends chasing a bad idea is an hour stolen from the good ideas that could have actually moved the needle.
Proper initiation isn’t red tape. It’s the filter that keeps garbage from ever hitting your team’s workload. Skipping it is the equivalent of leaving your front door open and wondering why you keep getting robbed.
Real initiation means slowing down before you speed up. It means asking hard, often uncomfortable questions like:
What exactly is the problem we’re solving, and is it even worth solving?
What happens if we do nothing? (Spoiler alert, often the answer is “nothing bad at all.”)
How does this align with our actual strategic priorities? Not the vague “vision statement,” but the real priorities that leadership is willing to resource.
Do we have the people, money, and authority to deliver this project successfully (without gutting other critical efforts)?
What’s the return on this investment? Not in feelings, but in measurable, tangible results.
If you can’t answer those, you don’t have a project. You have an idea. And ideas are cheap. They belong in a parking lot until they earn the right to move forward.
In the military, we don’t roll out of the wire just because someone had a “good idea” during chow. We planned missions with ruthless discipline. We confirmed the intel, defined the objective, assessed the risk, and verified that we had the resources, the authority, and the time to succeed.
If we skipped those steps, people got hurt. And here’s the connection most business leaders don’t see: in corporate projects, the “people getting hurt” are your teams, your customers, and your reputation. You may not be taking fire, but you are burning out your people, draining your budget, and damaging trust when you send your organization into a fight it can’t win.
In the Army, we also plan for no-go criteria: conditions under which we will not execute the mission, no matter how much someone wants it to happen. Why? Because discipline means knowing when to walk away.
Business projects need the same mindset. If your objective isn’t clear, your resources aren’t adequate, or the risk outweighs the reward, you don’t “push forward and hope for the best.”
You stand down, regroup, and spend your effort where it can actually make an impact.
But here’s the leadership challenge: killing bad projects early is one of the most valuable things you can do, and yet it’s one of the least celebrated. People will accuse you of being negative, risk-averse, or “not a team player.”
In reality, though, you’re protecting the organization’s focus, credibility, and budget from being flushed down the drain.
The best leaders I’ve worked with didn’t say “yes” quickly, they said “no” often, and with good reason. They understood that the work you don’t take on is just as important as the work you do. They knew that resources are finite, and that every project accepted is a project that displaces something else.
The takeaway? Don’t confuse initiation speed with leadership skill. The fastest way to fail is to start everything. The smartest way to succeed is to start only the right things, and start them correctly.
So, before you greenlight that next project: Validate the need. Challenge the assumptions. Test the business case. And if it doesn’t hold up, have the guts to walk away.
The project you don’t start might be the smartest decision you make all year.
