Opportunity Management and Risk in the Wider Project Lifecycle
Managing opportunity
Opportunities are positive risks and deserve the same rigour as threats: identify, assess, plan a response (exploit, enhance, share, accept, escalate) and monitor. Common failure is treating opportunities as "nice to have" and never assigning an owner or action. Exploit means taking action to ensure the opportunity is realised; enhance means increasing its probability or impact; share means partnering with another party better placed to capture it.
Risk across the lifecycle
Risk profile changes through the lifecycle: early phases carry high uncertainty and high opportunity (design freedom), later phases carry lower uncertainty but higher cost of change. Risk management must be front-loaded - the cheapest time to influence risk is early. At stage gates, risk is reviewed to decide whether to proceed, pause or stop. Lessons learned and post-project reviews feed future projects.
Programme and portfolio context
Risks may be escalated to programme or portfolio level, and aggregated - individual low risks can combine into significant programme exposure. Risk at one project can be another's opportunity (e.g. shared resource release).
Traps
- Ignoring opportunities or treating them as automatically acceptable without analysis.
- Assuming risk management stops at delivery; it continues through closure and benefits realisation.
- Failing to aggregate risks across projects.
- Believing early-phase risk is low because little has been spent - uncertainty is actually highest then.
Worked example
A project identifies that a new tool could cut testing time by 20%. Response: exploit - assign an owner, pilot the tool, and schedule its adoption; then monitor adoption and measure the actual saving. If the tool requires a partner, share the opportunity through a joint arrangement.
Rule of thumb
Front-load risk effort: uncertainty and opportunity are greatest early, and change is cheapest then.