Project Failure Files: No Measurable Business Value

In Episode 53 of the Project Failure Files weekly webcast, our focus was “Deliverables That Don’t Deliver,” in which Sharon and I explored the hidden cost of holding onto projects and deliverables that no longer provide measurable value. We highlighted how work can be completed on time and within budget but still fall short of actual business outcomes. Whether it’s outdated features, misaligned solutions, or simply building something because it’s “in the plan,” this episode addressed how easily teams fall into the trap of confusing activity with impact.

Sharon and I dove into the cultural and organizational impacts of low-value work, including eroded stakeholder trust, demoralized teams, and wasted resources. We shared real-world stories of dashboards no one used, reports that collected dust, and post-launch features that lacked user adoption. We emphasized the danger of celebrating completion over results and the importance of revisiting project goals midstream.

To overcome these pitfalls, we offered actionable strategies like tying deliverables to KPIs, running midpoint “value checks,” and building user feedback loops early in delivery. We advocated for outcome-based metrics and business cases that evaluate whether a deliverable solves a real problem. The message is clear: if it doesn’t deliver results, it’s not worth delivering.

Enjoy the episode!

Be sure to tune in next Monday, June 23rd at 9am Pacific for Episode 54 of our weekly series as Sharon and I discuss “Skipping Project Closure.“ Hope you can join us on LinkedIn or YouTube.