Skip to content
DOL Coach Logo
  • Writing
    • Blogs and Newsletters
    • Books By Scott Kinder
    • Special Forces Brothers In Christ
    • No BS Change Management
    • No Bullsh*t Project Management Book
    • Frag Out! A Green Beret’s Guide To Winning in Life and Work
    • MTT: Military Transition Tips: As Given To Thousands of Veterans Over The Past Decade
    • FM 18-1 Achieving Your Vision
    • FM 18-2 A Green Beret’s Guide To Getting Out Of Debt and Living The Life You Deserve
    • The DOL Coach Recommended Book List
  • Courses
    • SOFPM Certification Course
    • From Projects To Programs Mastering Strategic Delivery
    • The DOL Coach Risk Management Deep Dive (TSCORE)
    • Productivity Deep Dive Course
    • Change Management Deep Dive Course
    • The Project Management Assessment and Certification (PMAC)
  • Links
    • Video Guides
    • The DAGR Group: Developing Authentic Generational Results
    • Contact Us
    • Scott Kinder (Founder and CEO)
    • All About Project Management Certification
    • PMP vs. CPP
    • Our Partners
    • DOL Coach Partner Application
    • Become a Licensed DOL Coach
    • Frequently Asked Questions (FAQ)
    • FREE Project Management Resources
    • Military Services
      • 5th Group PM Certification Scholarship Opportunties
      • The SOFPM Advanced Project Management Certification Course
      • Using The GI Bill for DOL Coach Certifications
  • Video Guides
  • Upcoming

Slow Your Roll!!

Slow Your Roll!!
  • View Larger Image

I’m going to say something that will irritate a lot of people in project management, leadership, and innovation spaces: most ideas should die quietly and quickly.

Not every thought deserves a kickoff meeting. Not every “wouldn’t it be cool if…” deserves a roadmap. And not every shower epiphany deserves to become a project that consumes time, money, and people.

Yet, here we are. Organizations are buried in projects that never should have existed in the first place. Projects that were doomed before the first task was created because they had no legitimate reason to be projects at all.

This isn’t a failure of execution. This is a failure of judgment. And it’s one of the most common, most expensive, and least talked-about problems in modern project management.

So let’s slow this thing down.

Ideas are easy. They’re free. They show up uninvited. They feel exciting. They make people feel smart.

Projects, on the other hand, are expensive, disruptive, and risky.

A project: Consumes real money. Ties up skilled people. Creates opportunity cost. Introduces unnecessary risk. Demands leadership attention. Competes with other priorities.

When you turn an idea into a project, you are making a commitment, whether you admit it or not.

Yet far too often, organizations blur the line between “This is an interesting thought” and “This deserves formal investment.”

That blur is where bad projects are born.

Let’s call this out directly. Bad ideas don’t become projects because people are stupid. They become projects because of human behavior and organizational dysfunction.

Here are the usual culprits:

Idea Addiction: Some leaders are addicted to novelty. New ideas feel like progress (even when nothing actually improves). They confuse motion with momentum.

Executive Drive-By Thinking: A senior leader casually mentions an idea in a meeting. No analysis. No validation. No context. Next thing you know, someone says, “Well… the boss mentioned it.” Boom. Project initiated.

Fear of Saying No: Middle managers don’t want to be the wet blanket. PMs don’t want to look “negative.” So instead of pushing back, they comply. Silence becomes approval.

Innovation Theater: Organizations want to look innovative. So they spin up initiatives that sound exciting but solve nothing. Innovation without intent is just noise.

Here’s the first hard truth: If you cannot clearly articulate the problem, you do not have a project. You have a thought.

Projects exist to solve problems or seize validated opportunities (not to entertain curiosity).

Ask yourself: What’s broken? What’s failing? What pain exists today? What measurable outcome are we trying to change?

If the answer is vague, emotional, or hypothetical, you are not ready for a project. “Because it seems like a good idea” is not a problem statement.

We love to dissect project failure at the end: Missed deadlines. Budget overruns. Scope creep. Low adoption. Disengaged stakeholders.

But in reality, many projects fail at conception, not execution.

They fail because there was no compelling business reason. The problem didn’t matter enough. The juice wasn’t worth the squeeze. The organization wasn’t ready. The cost outweighed the benefit from day one.

Execution can’t save a project that never deserved to exist.

Here’s the question that should be asked before a project charter is drafted: “What happens if we do nothing?”

If the honest answer is: “Not much.” “We’ll survive.” “It might be mildly inconvenient.” “We just won’t have this nice thing.”

Then congratulations: you just talked yourself out of a project. Projects should exist because inaction is unacceptable, not because action is interesting.

Idea parking lots exist for a reason. Every organization should have a safe place for ideas to live without becoming projects.

Not everything needs immediate action. Not everything needs a team. Not everything needs funding.

Some ideas need time to mature. Need validation. Need to die naturally. Need to be revisited later. Need to stay exactly where they are: theoretical

A mature organization doesn’t rush ideas into execution. It filters them.

If turning an idea into a project feels easy, painless, and friction-free, that’s a warning sign. Good project selection requires hard questions and discomfort. Trade-offs and honest/clear conversations. Data. Pushback

If no one is uncomfortable during project initiation, odds are that no one challenged the premise. No one counted the real cost. No one asked what would be deprioritized. No one owned the downside.

Projects should earn their right to exist.

Here’s the part most people ignore: Every project steals resources from something else.

Time spent here is time not spent there. People assigned here are unavailable elsewhere. Money allocated here cannot be spent again.

When you green-light a weak project, you’re starving stronger initiatives and diluting focus while burning out good people and creating noise instead of value.

Saying “yes” irresponsibly is leadership malpractice.

Project managers are often brought in after the damage is done. The decision has already been made. The project already exists. The expectation is execution, not judgment.

That’s a mistake. Strong PMs don’t just manage timelines. They challenge bad ideas early.

Your value is not just in delivery. It’s in discernment.

If you see a project with: No clear problem. No success criteria. No committed sponsor. No real urgency. No measurable outcome.

You have an obligation to say: “We need to slow this down.”

That’s not negativity. That’s professionalism.

Before anything becomes a project, it should answer (clearly and honestly) these questions:

What problem are we solving?

Who actually cares if this succeeds or fails?

What measurable outcome will change?

What happens if we don’t do this?

What are we willing to stop or delay to fund this?

Who owns the risk?

If those answers are fuzzy, emotional, or political, stop. Slow your roll.

High-performing organizations aren’t great because they do more projects. They’re great because they do fewer, better ones. They protect their people. They protect their focus. They protect their credibility. They understand that saying “no” is often the most strategic move available.

Enthusiasm is easy. Discipline is hard.

Anyone can have ideas. Anyone can start projects. Anyone can create noise.

Leaders, PMs, and organizations that win long-term are disciplined enough to pause, evaluate, and kill weak ideas early: before they metastasize into full-blown disasters.

So the next time someone says: “I have an idea…” Take a breath. Ask the hard questions. And remember: Just because you can make it a project doesn’t mean you should.

Slow your roll.

By Scott Kinder|2025-12-18T10:29:23-05:00December 18th, 2025|NO BS PM|

Share This Post With Others!

FacebookXLinkedInWhatsAppPinterestXingEmail

About the Author: Scott Kinder

I founded DOL Coaching in a desire to continue my service to others after decades of service in the federal government, military service, and civilian employ. I’m a Special Forces combat veteran (18C MOS), former civil servant and executive with roles across a multitude of industries (from Wall Street to internet startups to consulting). People who know me will tell you I’m passionate about helping those around me grow and prosper.

Related Posts

Your Project Isn’t Failing. Your Decisions Are.
Gallery

Your Project Isn’t Failing. Your Decisions Are.

July 14th, 2026
The Most Expensive Word in Project Management: “Assume”
Gallery

The Most Expensive Word in Project Management: “Assume”

July 7th, 2026
Scope Creep Usually Is Your Fault
Gallery

Scope Creep Usually Is Your Fault

June 30th, 2026
Theory vs Reality: The Moment Your Project Takes a Sharp Turn
Gallery

Theory vs Reality: The Moment Your Project Takes a Sharp Turn

June 23rd, 2026

DOL Coach Logo

DOL Coach is a veteran-owned and operated business built to fix execution. We help individuals and organizations solve real problems through practical, engaging project management training that actually translates to performance. No memorization. No wasted time. No nonsense.

Proud Platinum Educational Partner of the Center for Project Innovation.

  • Home
  • Scott’s Blogs
  • Upcoming Courses
  • Project Management Resources
  • The SOFPM Accelerated Project Management Certification Course
  • PMP vs. CPP
  • The DAGR Group: Developing Authentic Generational Results
COPYRIGHT dolcoach.com   |   Site by patskot
LinkedIn
Page load link
Go to Top