Few situations are more frustrating in project management circles than watching a project lose credibility after weeks or months of productive work. The team has been meeting regularly, milestones and deliverables have been reached, and tangible progress has been made. Then, almost without warning, the conversation changes. Questions that seemed settled months ago suddenly return. Why are we doing this? How much will it cost? Is it worth continuing? Was this ever approved? Leadership begins asking for new cost estimates, timeline estimates, business cases, or even just an outright justification that everyone thought had already been established.
The natural reaction is to defend the project! Teams gather documentation, revisit estimates, explain technical decisions, and spend countless hours rebuilding information that once seemed obvious. The project itself is rarely the problem. The problem is that somewhere along the way, the organization, or certain individuals, lost confidence in the reason the project exists, or perhaps on the value the project delivers. Same thing, really.
Projects have a tendency to outlive the conversations that started them, and in some cases they outlive the people that planned them. People change roles, budgets are changed, executives join or leave the organization, and priorities evolve. Months after a project begins, the people asking questions may not be the same people who approved it. Even if they are, the context that existed at the beginning may have faded enough that the project no longer feels connected to the organization’s current direction.
This is why I believe every significant project needs a story that survives longer than the kickoff meeting.
The Project Management Institute describes the business case as the foundation for demonstrating a project’s ongoing value, not simply the document used to obtain initial approval. As projects progress, that justification should continue to be validated against changing business conditions and expected benefits. That ongoing connection between work and value is a critical part of effective project governance. (1 PMI, The Need for a Business Case.)
When that connection weakens, organizations often respond by asking for more detail. High-level estimates become detailed estimates, sometimes needing to be reverse-engineered. Summary documents become lengthy presentations. Teams spend weeks explaining work that has already been underway for months. Sometimes that effort is appropriate, but quite often it is treating the symptom rather than the cause.
What leadership is really trying to recover is confidence.
That confidence returns surprisingly quickly when the conversation shifts back to value. Does the project still solve an important business problem? Does it still support the organization’s strategy? Have the expected benefits changed? Has something happened that genuinely invalidates the original business case, or has the organization simply lost sight of it?
Those discussions are far more productive than debating individual tasks or defending every estimate. They reconnect the project to the reason it exists, allowing leaders to evaluate whether the work still deserves the organization’s investment.
The best recovery, however, is prevention.
Projects should not begin with a business case that is written once and forgotten. They should begin with a business case that is simple enough to revisit throughout the life of the project. Any executive, sponsor, or project manager should be able to explain, in a few minutes, why the project exists, what value it is expected to deliver, and how it supports the organization’s strategy. If answering those questions requires searching through months of meeting notes or rebuilding old assumptions, the project has already started losing its story.
PRINCE2 builds this idea into one of its core principles: a project should maintain continued business justification throughout its life. If the justification no longer exists, the project should be challenged rather than allowed to continue simply because work has already been completed.
Projects earn approval once.
They earn confidence continuously.
When that confidence begins to fade, resist the temptation to defend the schedule or the estimate first. Reconnect the work to the business value that justified it in the first place. Once people understand the story again, they usually find it much easier to support the project that’s telling it.
1 PMI, The Need for a Business Case https://www.pmi.org/learning/library/need-business-case-6730