Memory hook: Deliver, hand over, measure value, then learn.
Must remember
Track the business case throughout the project. Market, regulation, technology and organizational strategy can change the value of continuing. Reassess benefits and costs with the sponsor/governance body instead of completing obsolete work merely because money has already been spent. Sunk cost alone is not a reason to continue.
Organizational change needs stakeholder readiness, communication, training, support and feedback. A technically successful deployment can fail if users cannot adopt it. Consider sustainability across procurement, operation and disposal, balancing measurable environmental/social objectives with the project’s business requirements.
Agree transition criteria with operations: documentation, ownership, support model, monitoring, access, training, known issues and recovery arrangements. Obtain formal acceptance where required. Close contracts, reconcile finances, release resources, archive records and capture lessons. If a project ends early, controlled closure is still necessary.
Benefits can continue after project closure. Assign an operational/business owner, baseline, measurement frequency and review dates. Distinguish acceptance of deliverables from proof that intended benefits were realized. Share improvements back into organizational procedures, templates and future estimates.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Business case no longer viable | Escalate evidence and evaluate redirecting or ending the work. |
| Users resist a new system | Investigate needs/readiness and support adoption. |
| Project closes before benefits mature | Transfer benefit ownership and measurement to the responsible business owner. |
Traps
- Sunk spending does not justify future waste.
- Project closure does not necessarily end benefits measurement.
Active recall
1. What is a sunk cost?
A past cost that cannot be recovered by the current decision.
2. Why plan adoption?
Value often depends on people changing behavior, not only on technology delivery.
3. What should operational handover verify?
The receiving team can own, support and recover the service.
4. Who measures benefits after closure?
The explicitly assigned business/operational owner.
5. Why close a cancelled project formally?
To settle obligations, preserve knowledge and release resources responsibly.