I remember sitting in a windowless conference room about four years ago, staring at a Gantt chart that was so colorful it looked like a bag of Skittles exploded on the wall. The project manager, a high-priced consultant, was beaming. "We’re 92% complete on the milestones!" he announced. Everyone nodded.

But then the CFO asked one question that sucked the air right out of the room: "So, when do we actually see the $200,000 in savings we promised the board?"

Silence. Not the contemplative, "let me think about that" kind of silence. The "oh no, we forgot to actually connect the work to the money" kind of silence.

If I'm honest, I’ve been on both sides of that table. I’ve been the consultant who got too caught up in the "process" and I’ve been the leader wondering why I just spent five figures on a project that feels like it’s just moving digital paper around.

In the world of project management consulting, ROI (Return on Investment) isn't just a buzzword, it’s the only reason we should be doing this in the first place. But so often, it slips through our fingers. If you’re feeling like your consulting engagements are high on "activity" but low on "impact," you aren't alone.

Here is why it happens, and how we can actually fix it.

1. Failing to Define Clear (and Brutally Honest) Objectives

It sounds basic, right? "We want to improve operations." Great. What does that mean?

If you don't define exactly what "better" looks like before you sign the contract, you’re basically giving a consultant a blank check to do "stuff." I’ve seen projects fail simply because the objective was too vague. We like the idea of "improvement" but we’re scared to put a number on it.

How to fix it: Set quantifiable targets before the first meeting. If it’s an IT project, maybe it’s "reduce infrastructure costs by 20%." if it’s an operational shift, maybe it’s "cut order processing time by 48 hours." Align the ROI with the intent. Is this about speed? Quality? Cost? Pick one and stick to it.

2. The Missing "Before" Picture (No Baseline)

You cannot measure change if you don't know where you started. It’s like trying to prove you lost weight without ever stepping on a scale on Day 1.

In the rush to "fix things," we often skip the boring part: documenting the mess we’re currently in. I’ve done this myself... I’ve jumped straight into solutions because I was excited to help, only to realize six months later that I couldn't prove we’d improved because we didn't have the old KPIs.

How to fix it: Define a clear baseline. Use relevant key performance indicators to document your current state. This becomes your reference point. Without it, your ROI is just a guess (and your CFO hates guesses).

3. Confusing "Busy" with "Better"

This is the biggest trap in project management consulting. We mistake outputs (a 50-page manual, a new software implementation, 10 training sessions) for outcomes (higher profit, lower turnover, faster delivery).

A consultant can deliver 100% of their "deliverables" and still provide 0% ROI if those deliverables don't change how the business actually functions. (Yikes, but it's true.)

How to fix it: Focus on the "So What?" For every deliverable, ask: "How does this change the way we make money or save time?" If the answer is "it doesn't," it shouldn't be part of the project.

4. The "Hidden Invoice" (Underestimating Total Costs)

ROI is a simple math problem: (Gain - Cost) / Cost. The problem? We usually get the "Cost" part wrong.

We look at the consultant's fee and think that’s the investment. But what about the 20 hours a week your internal team spent in meetings? What about the software licenses? The hardware upgrades? The "productivity dip" while everyone was learning the new system?

How to fix it: Account for the "Total Cost of Ownership." Include internal labor, administrative fees, and any "collateral" expenses. When you have a realistic cost, your ROI calculation finally becomes honest.

5. Ignoring the "What-Ifs" (Risk Factors)

Projects don't happen in a vacuum. Markets shift. Key employees quit. (I once had a project stall for three months because the lead internal champion took a different job: we never saw that coming.)

When we calculate ROI, we usually look at the "best-case scenario." But real life is messy. If your ROI hinges on everything going perfectly, your ROI is probably a fantasy.

How to fix it: Conduct a risk analysis. Adjust your ROI projections to account for potential delays or scope shifts. It’s better to promise a 10% return and hit it than promise 40% and fail because of a "surprise" everyone should have seen coming.

6. The "Cash Only" Trap

Not every return is a dollar bill dropped directly into the bank account. Sometimes the ROI is strategic.

Maybe the project didn't save you $100k this year, but it gave you the organizational agility to pivot into a new market that will make you $1M next year. If you only measure "direct cost savings," you might be undervaluing your best initiatives.

How to fix it: Use a broader lens for ROI. Acknowledge strategic benefits like employee engagement, innovation, or brand reputation. If you're working on team dynamics, for instance, you might look at tools like DiSC Assessment Training to see how better communication reduces the "hidden cost" of conflict.

7. The Hand-off Ghosting

Consultants are great at delivering recommendations. But they (usually) don't run your company. If a consultant hands you a brilliant plan and your team puts it in a drawer to gather dust, the ROI is zero.

I’ve seen this happen so many times it breaks my heart. The "solution" was right there, but the execution was missing.

How to fix it: Measure adoption, not just delivery. Track whether the tools are actually being used three months after the consultant leaves. If you need help bridging that gap, looking into coaching or leadership development can ensure the changes actually stick.

8. Project Success vs. Business Success

A project can be a "success" (on time, under budget, all features included) and still be a business failure.

Think about it: You could build the world's most efficient system for a product that nobody wants to buy anymore. The project was managed perfectly, but the ROI was negative because it didn't align with the business's actual needs.

How to fix it: Use a "Three-Layer Outcome Framework." Connect every project milestone to a financial, operational, and strategic goal. If the project isn't moving the needle on the business's overall mission, stop the project.

9. Treating ROI Like a "One-Night Stand"

Most organizations check the ROI once: at the end of the project: and never look at it again. But real value often takes time to mature.

Strategic shifts are like wet cement... they take time to set. If you measure the ROI of a massive cultural or operational shift the day the consultant leaves, you’re going to be disappointed.

How to fix it: Track ROI over time. Establish "leading indicators" (small wins) for Year 1, and "lagging indicators" (the big money) for Year 2 and 3. Stay the course. (And maybe check our blog for more on operational rhythms to see how to maintain that momentum.)

10. The Attribution Ego Trip

Sometimes, things get better and the consultant takes all the credit. Other times, the consultant does all the work and the internal team takes the credit.

When you can't accurately attribute who caused the improvement, you can't accurately calculate the ROI of the consulting itself. You need to know if the value came from the consultant's expertise or just from your team finally having the permission to work on a specific problem.

How to fix it: Be objective. Assess what the consultant specifically brought to the table: was it a new framework? A specialized skill? Or just extra capacity? Understanding the "why" behind the win helps you decide if you should hire them again.

If I'm Being Honest...

I don't have all the answers. Even after years in project management consulting, I still find myself getting distracted by a cool new process or a fancy software feature. It’s easy to lose sight of the "Return" when you’re deep in the "Investment."

But I've learned that the most successful projects aren't the ones with the most complex charts. They’re the ones where everyone: the consultant and the leadership team: is obsessed with the outcome.

Leadership is messy. Operations are even messier. But when you start measuring what actually matters, the path forward gets a whole lot clearer.

If you're feeling like your current projects are spinning their wheels, I’d love to chat. Whether it's through strategic consulting or just a quick audit of your current processes, let's make sure your "Skittles chart" actually leads to some real gold.

What’s been your biggest frustration with ROI in your projects? I’d love to hear your stories: the good, the bad, and the "why did we do that?" moments. Reach out to us here and let's talk.