A project can be well controlled and still be strategically wrong because the assumptions outside its boundary changed first.
A familiar executive failure begins with a deceptively competent question: How quickly can we deliver this? The schedule is developed, the budget is refined, the governance structure is established and the delivery team begins to optimise execution.
The harder question often arrives too late: Should this initiative still exist in this form, in this environment, for these stakeholders?
Projects do not operate in isolation. They sit inside permanent organisations and are exposed to markets, regulation, technology, labour conditions, suppliers, customer expectations, community pressure, organisational culture and internal capability. The supplied MPM416 material treats social, economic and environmental analysis as part of understanding the project context rather than as an optional layer added after planning. That distinction is strategically important.
Control is necessary. Context determines what deserves to be controlled.
The Strategic Context
Traditional project management grew strongly around problems that could be decomposed, scheduled and monitored. Techniques such as PERT and CPM remain useful because time, sequence, dependencies and resources matter. But the source material also traces the expansion of project management into environments where social interaction, organisational change and stakeholder expectations become central.
This creates two simultaneous realities.
The first is the delivery system: work packages, resources, interfaces, cost, schedule, quality and risk. The second is the environmental system around the initiative: competition, legislation, economic change, technology, labour markets, community expectations, internal structures, organisational history, culture and stakeholder attitudes.
A project can be internally healthy while the environmental system is making its original business case obsolete.
A hypothetical manufacturer, for example, could have a disciplined automation project with stable engineering progress and good cost control. Yet if customer demand shifts, an environmental regulation changes, a critical supplier withdraws, or a different technology alters the economics, the correct executive action may be to redesign, defer or stop the initiative. Better project control cannot repair a strategic premise that no longer holds.
This is why environmental analysis belongs upstream of approval and throughout delivery.
What Leaders Commonly Misread
The first misread is treating context as a one-time planning input. Many business cases contain a market section, stakeholder list and risk assessment, then proceed as if those observations remain valid for the life of the initiative. In a changing environment, context is not a paragraph. It is a variable.
The second misread is treating external forces as more important than internal ones. Competition and regulation may trigger change, but the organisation's response is constrained by its own human resources, culture, administrative structures, technology, history and employee attitudes. An organisation may identify the right strategic move and still lack the capacity to execute it.
The third misread is reducing stakeholders to people who need communications. The pluralism material presents organisations as multi-constituency systems influenced by governments, investors, employees, customers, suppliers, communities, professional groups, labour organisations, education institutions and media. These parties do not simply receive messages. They can shape legitimacy, requirements, constraints, access to resources and the practical definition of acceptable value.
The fourth misread is assuming that a technically correct answer is automatically an organisationally viable answer. Projects increasingly sit at the intersection of technical systems and social systems. The more interdependent the initiative, the more dangerous it becomes to optimise one while ignoring the other.
Reframing the Issue
Environmental analysis is often framed as risk identification. That is too narrow.
For executives and portfolio leaders, the purpose is to understand what system the organisation is entering, what is changing within that system, and what those changes mean for investment choices.
The strategic question is not merely, “What could go wrong?” It is:
What has to remain true for this initiative to keep deserving capital, scarce capability and executive attention?
That reframing changes governance. Instead of approving a project and monitoring only delivery performance, leaders monitor both the project and the assumptions that justified it.
Strategic Analysis: Five Contexts That Can Change the Decision
1. Market and economic context
Competitive moves, customer preferences, price pressure, market structure and broader economic conditions can change expected demand, margins or timing. Their importance is not limited to commercial companies. The supplied change material also notes that public and non-commercial organisations can face competitive or comparative pressure from alternative service providers and public scrutiny.
The implication is straightforward: strategic alignment cannot be assessed only against an internal strategy document. Strategy itself is a response to an environment.
2. Regulatory and societal context
Legislation, safety expectations, environmental requirements and community concerns can redefine what is permissible or legitimate. A project that meets an old specification may become unacceptable even before a new legal requirement formally takes effect if stakeholder expectations move faster than regulation.
This makes regulatory scanning and stakeholder sensing related activities. Compliance asks what is required. Strategic context asks what may soon be expected.
3. Technology context
The source material describes continuous technological progress as a pressure on organisations, projects and professional capability. Digital communication, shared information environments and increasingly integrated tools change not only how projects are managed but also what products, services and operating models are feasible.
The executive issue is therefore not “Which tool should the project team use?” It is “Does technology change the economics, architecture, capability requirements or competitive logic of the initiative?”
4. Organisational context
Internal influences can be as decisive as external ones. An organisation may be constrained by skills, culture, governance, technology, administrative structure, history or attitudes to change. These are not soft issues in the sense of being secondary. They determine whether the permanent organisation can absorb the temporary project's outputs.
5. Stakeholder and pluralistic context
In a multi-constituency environment, an organisation rarely has complete freedom to optimise for one objective. Investors may seek returns, customers may seek affordability and quality, employees may seek safety and security, regulators may seek compliance, communities may seek acceptable impacts, and suppliers may seek commercial viability.
Leadership therefore becomes an exercise in explicit trade-offs. The task is not to satisfy every preference. It is to understand which interests are material, which are legitimate, which are negotiable and which create non-negotiable boundaries.
Related article: Stakeholder Engagement Is a Decision System, Not a Communication Plan
Decision Framework
A practical context test can be built around six questions.
| Test | Executive question | Decision implication |
|---|---|---|
| Strategic relevance | Does the initiative still address a priority that matters? | Continue, reshape or stop |
| External validity | Have market, regulatory, social or technology assumptions changed? | Revalidate the business case |
| Internal capacity | Can the organisation absorb the delivery and resulting change? | Sequence, reduce scope or build capability |
| Stakeholder legitimacy | Have material stakeholder expectations or constraints shifted? | Re-engage and revise design choices |
| Reversibility | Which commitments become difficult or expensive to unwind? | Delay irreversible moves until evidence improves |
| Option value | Can the initiative preserve useful future choices? | Prefer staged commitments where uncertainty is high |
The most important discipline is cadence. Context should be reviewed at decision points, not merely documented at initiation.
A portfolio committee could require each material initiative to identify three to five strategic assumptions alongside its usual delivery indicators. If those assumptions move beyond defined thresholds, the decision returns to the portfolio level.
This creates a healthier distinction between project governance and investment governance. The project team controls delivery. Leadership retains responsibility for deciding whether delivery remains worth pursuing.
From Strategy to Execution
Immediately, identify the external and internal assumptions embedded in major initiatives. Avoid vague statements such as “market conditions remain favourable”. Make assumptions observable: customer volume, regulatory pathway, supplier availability, workforce capability, technology readiness or stakeholder acceptance.
Over the medium term, connect environmental sensing to portfolio reviews. Strategy teams, risk functions, operations, commercial leaders and project teams should not maintain separate versions of reality. The organisation needs a mechanism for translating changes in the environment into funding, sequencing and scope decisions.
Over the long term, build the capability to treat projects as strategic options rather than fixed promises. Some initiatives should be accelerated when conditions improve. Others should be redesigned as assumptions weaken. A mature organisation is willing to stop work whose strategic logic has expired, even when delivery performance remains respectable.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
Signals to Monitor
Leaders should watch for signals that invalidate the original context rather than waiting for project metrics to deteriorate. Useful signals include:
- a material change in customer behaviour or willingness to pay;
- new regulatory proposals or stronger community expectations;
- a technology that changes cost, performance or time-to-market assumptions;
- supplier fragility or loss of critical capability;
- rising internal change saturation or workforce resistance;
- repeated stakeholder objections that indicate a design or legitimacy problem;
- widening gaps between the business case and actual operating economics.
A useful warning sign is when project reporting remains green while strategic assumptions are no longer being discussed.
Questions for the Leadership Team
- Which assumptions outside the project boundary are most important to the investment case?
- What has changed since this initiative was approved?
- Are we measuring the environment, or only the delivery plan?
- Which stakeholder groups can materially change the initiative's legitimacy or feasibility?
- What internal constraint could prevent the permanent organisation from absorbing the change?
- Which commitment are we about to make that will be difficult to reverse?
- If we were deciding today with current information, would we still fund the initiative in the same form?
References
Burgan, SC & Burgan, DS 2014, One size does not fit all: Choosing the right project approach, paper presented at PMI Global Congress 2014, Project Management Institute, Newtown Square, PA.
Silvius, G, Schipper, R, Planko, J & Planko, MJ 2012, Sustainability in Project Management, Routledge, Farnham.
Closing Perspective
Strong project control answers whether an initiative is being delivered as planned. Strong strategic leadership asks whether the plan still deserves to be delivered.
The environment will continue to move while projects are in flight. Executives therefore need governance that looks outward as well as inward, challenges assumptions as well as variances, and treats context as a continuing source of decision intelligence. The organisation that sees change first does not automatically win. The advantage belongs to the organisation that can translate what it sees into disciplined choices about what to continue, change, accelerate or stop.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.