Stop Measuring Success by Delivery And Start Measuring Value

If I asked ten project managers to define success, I’d probably hear the same three answers over and over: “Delivered on time.” “Delivered on budget.” “Delivered within scope.” And while those things matter… None of them is actually the point. Because a perfectly executed project that creates no value is still a failed project.

Read that again. You can hit every milestone. You can close every action item. You can have green status reports for months… and still completely miss the reason the project existed. That’s because project success and project value are not the same thing.

Today, I want to talk about one of the most misunderstood concepts in project management: Value.

Value is the excess of financial and nonfinancial benefits over the investment gained from achieving the goals of a project. That definition matters. Because value is not revenue. Value is not cost savings. Value is not activity. Value is benefit minus investment. And those benefits can be financial… or not.

If you don’t understand that distinction, you’ll spend your entire career optimizing projects that shouldn’t exist.

Projects naturally create outputs, and most teams focus on delivering outputs instead of outcomes.  Some examples of outputs are software, buildings, training, policies, products, processes, or reports.

Outputs are tangible. Value is often intangible. That creates a problem. Teams become obsessed with what they can see. Executives ask: “How many features shipped?” Instead of: “Did customers adopt them?” Managers ask: “Did training complete?” Instead of: “Did behavior improve?” Project teams ask: “Did we finish?” Instead of: “Did anything get better?”

That’s dangerous, because outputs are easy to measure. Outcomes are harder. Value is hardest. But value is the only thing anyone actually remembers. Nobody celebrates a project charter ten years later.

People remember: Revenue generated. Lives improved. Risk reduced. Time returned. Capability created.

One mistake I see constantly is reducing value to money. Of course, money matters. But value is broader. I teach teams to think in four categories.

1. Financial Value: This is the obvious one. Examples: Increased revenue, reduced operating cost. Lower maintenance expense. Improved margins. Better utilization. Easy to measure. Dangerous to over-focus on. Because not all important projects immediately create dollars.

Example: A cybersecurity initiative may generate zero direct revenue. But avoiding catastrophic loss creates enormous value.

2. Strategic Value: Some projects exist to position the organization. Examples: Market expansion. Digital transformation. New capability creation. Competitive advantage. Innovation. These often look expensive early. That doesn’t mean they lack value. Innovation frequently appears inefficient until outcomes appear.

Remember: Innovation is successful change. Projects are how innovation gets delivered.

3. Operational Value: Operational value improves execution. Examples: Faster cycle times. Reduced defects. Improved efficiency. Better decision-making. Less rework. These projects often get ignored because they don’t create flashy headlines. But operational improvement compounds.

Saving ten minutes per employee per day across 1,000 people becomes massive.

4. Human Value: This category gets ignored far too often. Examples: Employee engagement. Reduced burnout. Customer satisfaction. Improved retention. Better communication. Increased trust.

People roll their eyes at this one. Until attrition spikes. Until customers leave. Until teams stop caring. Then suddenly everybody wants culture. Human value isn’t soft. It’s delayed.

The definition above matters: Benefits minus investment.

That means: A project producing $100,000 in benefit for a $50,000 investment may outperform one generating $1M on a $2M investment.

Bigger isn’t always better. Efficiency matters. Organizations fail here constantly. They ask: “What’s the biggest opportunity?” Instead of: “What produces the greatest value?”

The biggest project often wins political battles. The smartest project wins organizational outcomes.

Most projects don’t fail because execution collapses. Most projects lose value long before delivery. Here’s how.

Problem 1: Nobody Defined Value. Ask five stakeholders: “What does success look like?” Get seven answers. If nobody agrees on value… you cannot optimize for it.

Problem 2: Measuring Activity Instead of Impact. Meetings held. Documents completed. Requirements approved. Training delivered. Those are activities. Not value.

Problem 3: Scope Becomes Sacred. Teams become emotionally attached to deliverables. Nobody asks: “If we removed 30% of this project, would the value remain?” Sometimes less scope creates more value. That makes people uncomfortable. Too bad.

Problem 4: Value Changes. Markets move. Customers change. Technology evolves. Projects continue. If value assumptions change… the project must adapt. Otherwise, you become highly effective at delivering irrelevance.

Here are some questions that every project manager should ask.

At initiation: What value are we creating? Who receives it? How will we measure it? What assumptions exist?

During planning: Which work contributes directly to value? What creates noise? What is optional?

During execution: Are we seeing leading indicators? Is adoption happening? Has value changed?

During closure: Did outcomes occur? What value was realized? What should we sustain?

If your project doesn’t answer those… you’re managing activity. Not projects. I use a brutally simple exercise. Ask: “If we canceled this project tomorrow, what would happen?” Answers reveal reality. If people say, “We’d lose market position.” That’s value. If people say, “We’d continue manually.” That’s operational value. If people say: “Nothing.” You may have your answer.

Another test: “If successful, who notices?” Nobody? That’s worth discussing.

Project teams love lagging indicators. Revenue. Savings. Final adoption. Completion. But value appears earlier.

Leading indicators include: Engagement, Usage, Decision speed, Participation, Defect trends, Cycle reduction, Retention, and Customer sentiment.

Lagging indicators tell you what will happen. Leading indicators tell you where you’re heading. Great project managers monitor both.

Some of you are delivering projects nobody needs. Some of you inherited projects that should have died months ago. Some of you are spending millions protecting sunk costs. That isn’t project management. That’s administration.

Project management requires courage. Courage to ask: “Why are we doing this?” Courage to recommend stopping. Courage to redefine success. Courage to protect value over ego. The goal is not to finish. The goal is to improve reality.

Projects are temporary. Value is what remains. Nobody remembers your Gantt chart. Nobody frames your risk register. Nobody talks about your status report five years later.

People remember: What changed. What improved. What became possible. That’s value. And if your project doesn’t create more benefit than investment (financially or non-financially)… you didn’t deliver success. You delivered motion.

This week, pick one active project. Ask your stakeholders one question: “What value are we actually trying to create?” If the answers are different… your next meeting just became obvious.