3.6 Linking Projects to Organisational Objectives
Key Takeaways
- Projects must link to organisational objectives so investment, benefits, and priorities stay justified within the portfolio and strategy.
- Without a strategic link a project can succeed locally — on time, on budget, to specification — while failing organisationally.
- Strategic alignment gives governance the ability to stop or redirect work when strategy changes, protecting value.
- The link is maintained through the business case, sponsor accountability, portfolio oversight, gate reviews, benefits management, and change control.
- Alignment is not a one-off charter sentence; it must be revisited whenever context, benefits, or strategy change.
Outcome 2d is short to state and easy to under-value: understand the importance of linking projects to an organisation's objectives. It is the outcome that explains why everything else in this chapter exists. Governance structures, roles, and authority limits are the machinery; strategic alignment is what the machinery is for.
Linking Projects to Organisational Objectives
Learning outcome (d) requires understanding the importance of linking projects to an organisation’s objectives. Projects consume scarce money, people, and management attention. Without a strategic link they can succeed locally (on time, on budget, to specification) while failing organisationally (wrong change, duplicate investment, or benefits that nobody values).
Why the link matters
- Investment justification — the business case should show how outputs and benefits support strategic goals, not only technical completion.
- Portfolio prioritisation — when resources conflict, initiatives that better serve objectives should win; governance needs that line of sight.
- Benefits ownership — outcomes usually sit in operations; linking to objectives identifies which BAU leaders must own realisation after transition.
- Stopping power — if strategy changes, governance can stop or redirect projects that no longer fit, protecting value.
- Stakeholder alignment — shared objectives reduce political conflict by giving a common reference for trade-offs.
How linkage is maintained in practice
| Mechanism | How it keeps the strategic link alive |
|---|---|
| Business case | States strategic fit, options, costs, risks, and benefits; reviewed when material change occurs |
| Sponsor accountability | One senior owner keeps asking “does this still matter?” |
| Portfolio / programme oversight | Aligns multiple projects to strategic themes and capacity |
| Gate and review cycles | Re-test viability and priority before further commitment |
| Benefits management | Tracks whether intended outcomes appear and still map to objectives |
| Change control | Prevents scope drift that quietly disconnects work from strategy |
Scenario: who decides what?
A local authority runs a digital services programme. Strategy aims to improve citizen access and reduce cost-to-serve.
- A team member proposes a technically elegant feature that delights internal IT staff but has weak citizen impact.
- The product owner (iterative workstream) ranks backlog items by citizen value and cost-to-serve reduction, deprioritising the elegant feature.
- The project manager incorporates the revised priorities into the iteration plan, reports capacity and risk, and flags that a supplier contract change would exceed their £20k authority.
- The users (front-line service staff) validate whether the new journey is workable in real contact-centre conditions.
- The sponsor confirms the workstream still supports the corporate digital strategy and chairs the steering group decision to approve the contract change and reconfirm funding.
- The steering group rejects a parallel “shadow” project from another department that duplicates the same citizen journey, protecting portfolio alignment.
Who decides what? Technical how → team; value order within product vision → product owner; integrated delivery control → project manager; investment and strategic continue/change/stop → sponsor and board; fitness for operational use → users. That separation is governance working as intended.
Answer Pattern for Long-Response Questions
When asked about roles or governance decisions:
- Name the role with the correct accountability.
- State what that role should do now in the scenario.
- State what must escalate and to whom.
- Link the decision back to business case, authority limits, or organisational objectives.
That structure mirrors how APM PMQ awards marks for applied governance understanding rather than role-title recall alone.
How the link breaks
Alignment is rarely lost in a single decision. It erodes, and each mechanism below appears in PMQ scenarios as a symptom rather than a diagnosis.
| How alignment breaks | What it looks like | Governance response |
|---|---|---|
| Strategy moves, the project does not | A new corporate priority is announced; the project's objectives are never re-tested against it | Re-review the business case at the next gate; consider stop or redirect |
| Scope drifts feature by feature | Each approved change is individually reasonable; the sum no longer serves the original objective | Assess cumulative change against the business case, not only each request |
| Benefits are redefined downwards | The measure quietly changes to one the project can meet | Hold the benefit definition under change control; require sponsor approval to alter it |
| Local optimisation | A department gets exactly what it asked for, at the expense of an enterprise outcome | Portfolio oversight arbitrates between competing initiatives |
| Output substitutes for outcome | Delivery is reported as success because the deliverable exists | Report benefits position alongside cost and schedule |
| Sponsor disengagement | Nobody senior is asking whether this still matters | Re-confirm sponsorship; an unsponsored project has no alignment guardian |
Alignment in the answer, not just the theory
Scenario questions that touch strategic alignment usually give you a project performing adequately on cost and schedule while something about its purpose has changed. The structure that scores:
- Name the objective the project was funded to serve.
- State what has changed — strategy, benefits forecast, external context, or the portfolio around it.
- Identify who owns the judgement — sponsor for justification, board for investment, portfolio for prioritisation between initiatives.
- Give the options — continue unchanged, re-scope towards the objective that still holds, defer, or stop.
- Say what makes stopping legitimate — protecting value that would otherwise be spent on a change nobody now needs.
That last point is the one most candidates avoid. Recommending that a project stop is a professionally correct answer when the strategic link has genuinely gone, and examiners reward candidates who can say so with evidence rather than treating continuation as the only acceptable outcome.
A project is delivering outputs on time and on budget, but a strategy review shows the intended benefits no longer support organisational objectives. What is the most appropriate governance focus?
A department starts a project that duplicates a citizen journey already being delivered by another department’s programme. Which governance mechanism is best placed to identify and resolve the duplication?