PMGT1860 · Project Initiation and Scope
Operations-Oriented Project Initiation
Week 9 looks past handover: how large inter-organisational projects should be initiated with the eventual transition to operations already in mind — across strategy, structure, process and people (Zhang et al. 2024). The distinction between delivery success and operational/whole-life success gives the literature review and group presentation a sophisticated lens, and 'delivered but unused' failure modes are a common quiz and discussion theme.
What this chapter covers
- 01Core question — traditional initiation asks 'can we deliver this?'; operations-oriented asks 'will it work in real life?'
- 02Projects (unique, temporary) vs operations (repetitive, ongoing); project vs operations management
- 03Delivery success vs operational success — completed on time/budget/scope vs useful, adopted, benefits realised
- 04Why delivered projects still fail after handover — wrong requirements, poor adoption, high operating cost, weak handover, limited benefits
- 05What operations-oriented initiation embeds — operational needs, user requirements, maintenance, transition planning, benefits realisation
- 06Translating operational questions into initiation decisions
- 07Whole-life value — narrow (capital cost/schedule) vs whole-life (operating cost, maintenance, staffing, UX, long-term benefits)
- 08Designing the transition (Zhang et al. 2024) — strategy, structure, process, people; handover as a process, not a document
Applied: diagnose a 'delivered but unused' project and fix it at initiation
- +1(a) Low clinician use is 'poor adoption' (people resist or work around the solution). The unexpectedly high running cost is 'high operating cost' (too expensive to staff, maintain or upgrade). The missing efficiency gains are 'limited benefits' (outputs exist but intended value is not realised).
- +1It may also reflect 'wrong requirements' — built to specification rather than to what clinicians actually need in their workflow.
- +1(b) For poor adoption: at initiation, involve users/operators early and scope the system through their user journeys and service needs. For high operating cost: add operability and maintainability requirements and take a whole-life-cost view, not just capital cost.
- +1For limited benefits: define benefit indicators and assign ownership at initiation, and link initiation to benefits realisation so someone is accountable for the value after handover.
- +1(c) Delivery success asks whether the output was completed on time, on budget and to scope with effective controls. Operational success asks whether the output is useful, can be operated and maintained, is adopted, realises benefits and creates long-term value. This project was a delivery success but an operational failure — the two are not the same.
Key terms
- Operations-oriented initiation
- An approach that embeds operational needs, user requirements, maintenance considerations, transition planning and benefits realisation into the earliest decisions about scope, stakeholders, risks, governance and success criteria — asking 'will it work in real life?', not just 'can we deliver it?'
- Delivery success vs operational success
- Delivery success = the output completed on time, on budget, to scope, with effective controls. Operational success = the output is useful, operable and maintainable, adopted by users, and realises benefits and long-term value. The two are not the same.
- Post-handover failure modes
- The five common ways a delivered project still fails once it enters operations: wrong requirements, poor adoption, high operating cost, weak handover, and limited benefits realised.
- Whole-life value
- Looking beyond capital cost and delivery schedule to operating cost, maintenance and upgradeability, staffing and training, user experience, and long-term benefits and disbenefits — 'a low-cost project can become an expensive operation'.
- Transition to operations (Zhang et al. 2024)
- Continuity between projects and operations designed along four elements — strategy, structure, process and people — with handover planned as a process, not treated as a final one-off document.
- Benefits realisation
- Ensuring the intended organisational or social value of a project is actually achieved after delivery, by defining benefit indicators and assigning ownership at initiation.
Operations-Oriented Project Initiation FAQ
Can a project be a success if it's delivered on time and budget but nobody uses it?
By delivery metrics yes, but by operational and whole-life measures no. Operations-oriented initiation argues that many 'delivery successes' are actually initiation failures, because the future operation was never properly understood at the start. A system delivered to spec but ignored by users, expensive to run, and delivering no benefits has failed where it counts — in use, not in handover.
What are the five reasons delivered projects still fail?
Wrong requirements (built to spec, not to need), poor adoption (people resist or work around it), high operating cost (too expensive to staff, maintain or upgrade), weak handover (incomplete responsibilities, data, training or documentation), and limited benefits (outputs exist but the intended value is not realised). Each traces back to a decision that should have been made at initiation.
What does it mean to 'design the transition to operations'?
It means planning handover as a process rather than a final document, and building continuity between the project and its future operation across four elements — strategy, structure, process and people (Zhang et al. 2024). Practically, you involve operators, maintainers and users early, add operability and maintainability requirements, define who owns the asset after handover, and link initiation to benefits realisation.
How does whole-life value change initiation decisions?
A narrow view fixates on capital cost, delivery schedule and initial scope; a whole-life view adds operating cost, maintenance and upgradeability, staffing and training, user experience and long-term benefits and disbenefits. Because a low-cost project can become an expensive operation, whole-life thinking pushes you to scope for operability, expand the stakeholder map to operators and maintainers, and include operational risks in the register at initiation.
Assessment move
Anchor this week on one contrast — delivery success versus operational/whole-life success — and be able to argue that a project can be the first without the second. Memorise the five post-handover failure modes and the operational-question→initiation-decision mapping, and practise applying them to a delivered-but-unused case (a hospital wing, a ferry service, a records system). Learn the four transition elements (strategy, structure, process, people) and 'handover as a process'. Add a journal line on a project that was delivered but never adopted, and confirm quiz timing on Canvas.
Working through Operations-Oriented Project Initiation in PMGT1860? Sia is AskSia’s AI Project Management tutor — ask any PMGT1860 Operations-Oriented Project Initiation question and get a clear, step-by-step explanation grounded in how PMGT1860 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
