'Context Comes Before Control: Why Project Decisions Begin Outside the Project'

The project plan may define the work, but the surrounding system determines whether the work will still matter when it is finished.

Executives often meet a project when it has already been translated into scope, milestones, budget and resources. At that point, management attention naturally shifts toward control: Are we on schedule? Are costs within tolerance? Are risks being managed? Are resources available?

Those questions matter, but they can arrive too late. A project can be well controlled and still be based on assumptions that the market, workforce, regulator, customer or organisation has already invalidated.

The supplied MPM416 material places economic, social and environmental context around the project rather than treating it as background information. It also identifies a wide range of external influences, including competition, legislation, economic change, labour markets, social change and trends, alongside internal influences such as organisational culture, administrative structures, technology, history, corporate structure, employee attitudes, strategy and stakeholders. The implication is more important than the list itself: project performance is produced by a system larger than the project.

For senior leaders, contextual analysis is therefore not an academic preface to planning. It is part of the investment decision.

The Strategic Context

Early project-management thinking was strongly associated with engineering, construction and defence settings in which planning, scheduling and control were central. The supplied teaching material characterises this as a relatively "hard" perspective: goals can be defined, work decomposed, resources scheduled and progress measured. Techniques such as PERT and CPM remain valuable because disciplined planning is still necessary.

The problem appears when leaders assume that what can be scheduled is what determines success.

The same course material describes the later expansion of project management into settings where social interaction, organisational change and stakeholder expectations are central. A project is not only a technical system. It is also a temporary organisation operating inside a permanent organisation and interacting with customers, employees, suppliers, regulators, communities and other constituencies.

This wider view matters because most significant initiatives are responses to something outside the plan. Competitors move. Customer expectations shift. Technologies alter what is possible. Regulation changes the cost or legitimacy of an operating model. Labour and skills become constrained. Suppliers disappear or become strategic dependencies. Community expectations change. Economic conditions alter the value of the original business case.

Context therefore influences at least four executive decisions before detailed control should dominate:

1. Whether the initiative is still strategically necessary.
2. Whether the proposed solution is still the right response.
3. Whether the organisation can absorb the change.
4. Whether the expected value remains credible under changing conditions.

Related article: Strategic Flexibility: Match the Management System to Environmental Turbulence

What Leaders Commonly Misread

A common mistake is to treat "the environment" as a one-time scan performed during strategy development. The project is then approved, the environment section disappears into the business case, and delivery is governed as if the organisation had entered a closed system.

The supplied change-management notes make the opposite point. An open organisation recognises changes in its general and specific environment and uses that information to develop strategy. Environmental uncertainty arises precisely because future conditions cannot be assessed with confidence. Complexity is affected by the number and interaction of relevant elements; dynamism reflects the rate and predictability of change.

A second mistake is to equate stakeholder analysis with communication planning. The pluralistic-society material shows why that is inadequate. Organisations operate among multiple groups with different interests, values and sources of influence. Customers, government, employees, investors, suppliers, professional bodies, labour groups, media and communities can all affect the organisation, while the organisation also affects them.

That changes the management problem. The objective is not always to optimise a single variable. Leaders may need to negotiate acceptable trade-offs among legitimate interests while protecting the organisation's primary purpose.

A third mistake is assuming that internal and external influences can be separated neatly. They interact. A regulatory change may expose a capability gap. A technology shift may change workforce requirements. A competitor move may force a portfolio reprioritisation. A social expectation may alter reputation risk and therefore investment criteria. An internal culture may determine whether the organisation can respond to an external opportunity quickly enough.

Reframing the Issue

The better question is not, "What risks could affect this project?" It is:

What system is this project entering, what is changing in that system, and which assumptions must remain true for the investment to create value?

That reframing moves environmental analysis from risk-register input to strategic decision architecture.

The project should be understood as a temporary intervention in a larger operating system. Its purpose is normally to change something in the permanent organisation: a process, asset base, capability, customer proposition, technology platform, regulatory position or business model. The permanent organisation then has to use that change to produce benefits.

This distinction is visible in the supplied project/operations diagram: projects consume resources to create outputs; the permanent organisation uses resources and assets through operations to produce benefits and performance. Portfolio management sits upstream because leaders must choose which changes deserve investment.

The consequence is clear. A project should not be approved merely because its deliverables are feasible. It should be approved because the organisation has a credible pathway from context to change to operational benefit.

Strategic Analysis: Read the System Before You Commit Capital

A useful contextual analysis should examine both directional forces and organisational response capacity.

External forces define the pressure

The source material identifies competitive moves, marketplace conditions, customer expectations, political and regulatory change, economic pressure, technology, globalisation, labour and supplier changes as recurring drivers. Their strategic significance lies in how they alter the value equation.

For a manufacturer, a new competitor may compress margin and make automation attractive. For a government agency, changing public expectations may make service redesign unavoidable. For a technology business, a platform shift may shorten the useful life of a planned system. The same project may therefore move from optional to urgent, or from attractive to obsolete, without its internal scope changing at all.

Internal conditions define the response

Internal influences such as culture, organisational structures, technology, history, employee attitudes and strategy determine whether the organisation can respond effectively.

Two organisations can face the same external shock and require different portfolios. One may already possess digital capability, supplier relationships and change capacity. The other may need foundational investment before attempting the same strategic move.

This is why benchmarking competitors can be misleading. The relevant question is not "What are they doing?" but "What conditions make that move rational for them, and do those conditions exist here?"

Context determines what success means

If the initiative exists to respond to a market, regulatory or social change, success cannot be defined only as delivery against the baseline. Success must include whether the organisation improved its position relative to the change that justified the investment.

A hypothetical example illustrates the distinction. Suppose a business approves a two-year customer-service platform because customers increasingly expect digital self-service. The project could finish on time and on budget. But if customer behaviour shifts again toward integrated mobile ecosystems and the delivered platform cannot connect to them, delivery discipline has not protected strategic value.

The project did what it was asked to do. Leadership asked it to solve yesterday's problem.

Decision Framework

Before approving or materially recommitting to an initiative, test six contextual questions.

This framework should not become another template completed once. Its value comes from repeated use at investment reviews, major design decisions, contracting commitments and transition points.

Where uncertainty is high, leaders should separate stable assumptions from fragile assumptions. Stable assumptions can support normal planning. Fragile assumptions should influence option design, contractual flexibility, sequencing and governance thresholds.

Related article: Tailor the Project, Not the Standard of Accountability

From Strategy to Execution

Immediate action: For major active initiatives, revisit the original strategic trigger and list the external and internal assumptions on which the business case depends. Identify any assumption that has materially changed since approval.

Medium-term capability: Build contextual review into portfolio governance. Project dashboards should include leading signals from markets, regulation, customers, workforce, suppliers and technology where those variables materially affect value. The purpose is not to create more reporting; it is to identify when a strategic decision needs reconsideration.

Long-term positioning: Develop organisational sensing and strategic flexibility as capabilities. Strategy, portfolio and delivery functions should not operate as sequential silos. Information discovered in projects and operations should feed back into strategic decisions, while changes in strategy should alter the portfolio before delivery resources are consumed by obsolete priorities.

Signals to Monitor

Watch for signs that control is becoming disconnected from context:

• projects remain green while the underlying business case deteriorates;
• competitors or customers change faster than portfolio review cycles;
• regulatory or social changes appear only as project risks rather than strategic triggers;
• projects are approved because peers are doing similar work without testing organisational fit;
• major assumptions are undocumented or owned by nobody;
• operational teams are expected to realise benefits without having shaped the change;
• portfolio decisions respond slowly to new information because stopping or redesigning work is culturally difficult.

Questions for the Leadership Team

1. What external or internal change is each major initiative actually responding to?
2. Which assumptions in our current portfolio are most vulnerable to market, regulatory, technological or social change?
3. Where are we managing delivery performance more closely than strategic relevance?
4. Which stakeholders can materially change the value or feasibility of our initiatives even though they sit outside the formal project structure?
5. Do our portfolio reviews have authority to redesign or stop work when context changes?
6. What information from operations should reach strategy earlier than it does today?

Source References

• University of South Australia, MPM416 Economic, Social and Environmental Analysis, Week 1 and course-introduction teaching materials supplied for this synthesis.
• University of South Australia, Study Notes: Tailoring Project Management and Change, supplied course material.

Closing Perspective

Projects do not fail only because plans are weak. They also fail strategically because organisations control the work more closely than they observe the world around it.

The discipline is not to abandon schedules, budgets or governance. It is to place them in the correct hierarchy. Context determines the decision. Strategy determines the desired change. Portfolio governance determines where to invest. Project management controls the intervention. Operations realise the benefit.

When leaders reverse that order, excellent execution can simply make the organisation arrive efficiently at the wrong destination.