For years, project success has been measured by two things: finishing on time and staying on budget. But even when both targets are met, many projects still fall short of delivering what really matters: meaningful results. Hitting deadlines and cost goals is important, but it doesn’t always equal value.
This gap between finishing a project and actually succeeding with it matters more today than ever. Technology, competition, and customer expectations are moving faster than ever before, pushing organizations to rethink what success truly means. The Project Management Institute (PMI) calls this shift a move toward value-driven delivery, focusing less on output, and more on outcomes.
At Therefore, we’re embracing this change. We’re evolving how we plan, build, and measure projects so that every one of them delivers lasting value — not just a finished deliverable. That means staying accountable long after launch, and making sure what we create genuinely benefits the business, its people, and its customers.
This article explores what value-driven delivery means, the practices we’re putting in place, and why this shift matters for every organization aiming for long-term success.
Before any work begins, everyone needs to agree on what success looks like. That means defining how it will be measured and what kind of value it should create. We call this the Desired Future State.
Value looks different for every organization. For some, it’s higher profits. For others, smoother operations or a stronger reputation. Whatever form it takes, our focus is to make value the guiding principle from start to finish.
In agile development, the Dynamic Systems Development Method (DSDM) uses an inverted project triangle; time, cost, and quality are fixed, while features are flexible. Instead of delivering every single feature no matter what, this model prioritizes what matters most. Less-important items can be dropped or delayed so the essentials stay strong.
Now imagine adding Value as a guiding principle alongside Quality. Quality is part of value, of course, but not the whole story. Economic return, user satisfaction, and strategic alignment all matter too.
When value is fixed as a constant, project teams start thinking differently. When challenges arise or requirements shift, stakeholders can adjust less-critical features without losing sight of the bigger goal — delivering real value.
This mindset helps projects create outcomes that last — whether through better performance, happier users, or stronger business impact.
With so many moving parts, it’s not always obvious what to tackle first. Traditional tools like the MoSCoW method (Must, Should, Could, Won’t) help, but they can still feel subjective. To bring more clarity, we’re adding a simple “value versus effort” lens. It starts with two questions:
Answering these questions helps focus energy and investment on what truly counts; the ideas and features that create the biggest difference for clients and customers.
This approach does take effort. It requires clear communication and honest discussion about what value really means to everyone involved. But when teams reach that shared understanding, decision-making becomes faster, smarter, and far more aligned.
This idea extends naturally into testing. We shouldn’t just ask, “Does it work?” We should also ask, “Does it add value?”
Comprehensive testing costs time and resources, but skipping it costs more. Value-driven quality assurance (QA) focuses effort where it matters most, ensuring every test adds confidence and return.
Keeping track of value means staying connected through regular communication, clear metrics, and flexibility as new information emerges. It takes structure and collaboration, but the payoff is clear. When teams stay focused on value, every part of a project contributes to something bigger.
And the evidence backs it up: according to PMI, tracking value throughout a project can double the chance of success.
Many benefits take time to appear, but the PMI suggests a way to measure value earlier — the Net Project Success Score (NPSS), inspired by the familiar Net Promoter Score (NPS).
The NPSS asks a simple but powerful question: did the project deliver value worth the effort and investment? Teams can use this score to compare projects, spot opportunities for improvement, and stay aligned with stakeholder expectations.
We take it one step further by measuring value in increments — what we call Releases. Each release gets its own NPSS rating, informed by regular stakeholder feedback and Continuous Discovery research with users. This creates a feedback loop that keeps value visible, actionable, and adaptable throughout development.
Success isn’t a single finish line, it’s a journey. Rather than viewing a project as done once it launches, we measure progress release by release, recognizing that each step builds toward a larger goal.
Websites, for instance, are never truly “finished.” They evolve with the business and its audience. By evaluating each release against key dimensions, we can track progress over time and ensure every step delivers measurable value.
A radar-style framework helps visualize that growth, showing how each release contributes to:
Reviewing these questions after every release creates a living record of progress, turning project management from a sprint into a steady, strategic climb toward lasting value.
While we continue refining how we measure value-driven delivery, one thing is already clear: the process of measuring value is itself a source of it.