Setting Up Projects for Success

The leadership, governance and organisational conditions that shape successful delivery performance

Gareth Mills

Independent viewpoint paper | Version 3.0 | August 2026

Overview

The conditions established during the front end of a project influence the quality of thousands of subsequent decisions. Yet pressure to demonstrate progress can encourage organisations to mobilise people, commission work and establish reporting before purpose, accountability, governance, capability and relationships are sufficiently aligned.

This paper examines project setup as an organisational and leadership problem rather than a purely procedural stage. Drawing on my professional experience coupled with research on major-project initiation, it proposes eight interdependent foundations through which sponsors and project leaders can assess whether a project is merely starting or is developing the conditions required for effective delivery.

The paper argues that successful setup is not a one-off initiation event, nor a guarantee of outcome. It is a continuing discipline of establishing alignment, making uncertainty discussable and adapting the project system as knowledge develops.

1. Introduction

Major projects do not begin with a blank sheet. They begin within organisations that already possess strategies, histories, relationships, constraints and expectations. Early choices about purpose, authority, leadership, commercial strategy and organisational form therefore create path dependencies: they shape what later becomes possible, difficult or expensive to change.

The central question considered in this paper is: what conditions need to be established during project initiation to improve the likelihood of effective delivery?

This question is deliberately wider than whether a business case has been approved, a schedule produced or a project team appointed. A project may have started in an administrative sense while remaining unclear about its outcomes, decision rights, organisational capability, stakeholder system or approach to learning.

The paper takes a systems perspective. It treats a project as a temporary organisation in which formal structures, human behaviour and institutional context interact. On this view, project setup is concerned with the alignment of the whole delivery system rather than the completion of isolated initiation products.

2. The significance of the project front end

The front end of a project is the period during which need, scope, governance, delivery strategy and organisational capability are progressively defined. Decisions made during this period often have consequences disproportionate to the apparent maturity of the project. Once contracts, structures, expectations and behavioural routines harden, correction becomes slower, more political and more costly.

The UK Government's Project Initiation Routemap was developed in response to this challenge. It emphasises the wider delivery environment, the capability of the organisations involved and the need to identify and address gaps before delivery accelerates [1]. Government guidance on front-end loading similarly argues that investment in early definition and alignment can improve the conditions for delivery [2]. Association for Project Management guidance places sponsorship and governance at the centre of accountability for outcomes and benefits rather than at the edge of project administration [3][4].

A recurring difficulty is the confusion of activity with readiness. Mobilisation creates visible movement: people arrive, meetings begin, plans are produced and procurement progresses. These activities may be necessary, but they do not by themselves demonstrate that the project system is alignment. Unresolved questions are instead carried into delivery, where they may appear as delayed decisions, interface failures, contractual friction, repeated re-planning or suppressed risk information.

3. Projects as organisational systems and getting people to start to work together

A major project is not simply a technical task supported by management processes. It is a system of organisations, authority, knowledge, incentives, relationships and decisions. Performance emerges from the interaction of these elements. A technically credible plan can be weakened by ambiguous sponsorship; capable individuals can be constrained by unclear decision rights; and formally comprehensive governance can fail when difficult information cannot travel to those with authority to act.

This systems view changes the purpose of setup. The objective is not to eliminate uncertainty before delivery begins, which is neither possible nor desirable. It is to establish sufficient coherence for the project to make sound decisions, surface uncertainty, coordinate across boundaries and adapt as evidence develops. The relevant test is therefore not whether every component exists, but whether the components ( organizational teams) to start to work together.

4. A Conceptual Framework - Eight foundations of successful project setup

The following eight foundations provide a conceptual framework for examining the front end of a project. They are interdependent rather than sequential, and should not be treated as a compliance checklist.

4.1 Purpose and outcomes

The project requires a shared account of the need it addresses, the outcomes and benefits it is expected to create, its boundaries and the assumptions on which the current proposition rests. Purpose should be distinguished from a preferred solution. Where significant choices remain open, this uncertainty should be made explicit rather than obscured by premature precision.

4.2 Sponsorship and accountability

An active sponsor connects the project to the investing organisation and remains accountable for the continuing validity of the investment and the realisation of benefits [3]. Effective sponsorship depends on mandate, authority, capacity and access. The relationships among sponsor, governing body, project director and operational owner require particular clarity and agreement.

4.3 Governance and decision rights

Governance should enable direction, challenge, assurance and timely decision-making [4]. Its quality is not demonstrated by the number of forums or papers produced. It depends on whether consequential decisions are taken at the appropriate level, on the basis of relevant evidence, with clear escalation routes and understood delegated limits.

4.4 Leadership and key appointments

The collective leadership capability should match the project's scale, phase, uncertainty and relational demands. Technical pedigree alone is insufficient. Role boundaries, interfaces and behavioural expectations need to be considered alongside individual competence, particularly where authority is distributed across client, partner and supply-chain organisations.

4.5 Organisation, team and culture

Project organisations are formed across institutional boundaries and often under time pressure. Early norms concerning candour, inclusion, constructive challenge and accountability can become self-reinforcing. A 'one team' aspiration is credible only when structures, incentives and visible leadership behaviour support collaboration in practice.

4.6 Stakeholder and system alignment

Projects operate within wider systems of customers, communities, regulators, funders, operators, delivery partners and political interests. Stakeholder analysis should therefore inform project strategy and decision-making rather than being treated only as communication after decisions have been made.

4.7 Delivery strategy, controls and interfaces

The intended delivery model should be compatible with project complexity and with the client's ability to integrate, assure and govern the work. Procurement, packaging, commercial incentives, requirements, schedule, cost and assurance should form an aligned strategy. Particular attention is required at interfaces, where responsibility can be divided while consequences remain shared.

4.8 Risk, knowledge and learning

Setup must create ways to surface uncertainty, test assumptions, protect critical knowledge and learn from relevant experience. A risk register is useful only to the extent that people are willing and able to contribute uncomfortable information. Historical evidence and comparable-project experience can also provide an outside view that challenges optimism in internal forecasts [5][6].

5. Interdependence and coherence

The eight foundations derive much of their value from their interaction. Weakness in one area creates load elsewhere. Unclear purpose makes governance less decisive because decision criteria remain unstable. Weak sponsorship leaves the project director carrying organisational conflicts that exceed delegated authority. An unsuitable delivery model can distort incentives and make collaboration structurally difficult. A culture that penalises challenge prevents risk and assurance processes from revealing the true position.

For this reason, maturity within individual disciplines is not sufficient. A project may possess strong controls, experienced leaders and detailed stakeholder plans while still lacking coherence across them. Reviews of setup should therefore examine relationships and contradictions: whether authority matches accountability, whether commercial incentives support desired behaviours, whether reporting serves actual decisions and whether retained client capability is sufficient for the chosen delivery model.

6. Implications for sponsors and project leaders

Project setup should be understood as a continuing leadership discipline rather than a single gate or workshop. The front end deserves concentrated attention, but setup decisions should also be revisited as scale, knowledge and interdependence increase. Arrangements that were proportionate during initiation may become inadequate during procurement, mobilisation or transition into delivery.

Sponsors and project leaders should create deliberate opportunities to compare perspectives across organisational and professional boundaries. This is particularly important where apparent agreement may conceal different interpretations of purpose, success, authority or risk. Independent challenge can be valuable when it improves the quality of inquiry rather than merely adding another assurance layer.

Finally, uncertainty should be treated as information rather than as evidence of weak management. The quality of setup depends partly on whether incomplete, ambiguous or politically uncomfortable information can reach those able to act. A project that appears certain but cannot question its own assumptions may be less prepared than one that openly recognises what it does not yet know.

7. Questions for critical reflection

Do senior stakeholders describe the project's purpose and intended outcomes in materially consistent terms?
Where does authority sit when organisational interests or accountabilities conflict?
Does the chosen delivery strategy match the project's complexity and the client's retained capability?
Which early assumptions are becoming embedded as facts without sufficient evidence?
What information might people currently be reluctant to raise or escalate?
Which decisions made during the next 90 days would be particularly expensive to reverse?
What are we not seeing?

8 Conclusion

Setting up a project for success does not guarantee a successful outcome. Major projects remain exposed to uncertainty, external change and the limits of prediction. Strong setup does, however, improve the quality of the organisational system that must respond to those realities.

The central distinction is between commencing activity and establishing the conditions for effective delivery. Purpose, sponsorship, governance, leadership, organisation, stakeholder alignment, delivery strategy and learning must be considered as an interconnected whole. The practical value of the eight foundations lies not in confirming that each exists, but in examining whether they are sufficiently aligned to support confident action, constructive challenge and adaptation.

The most important question is therefore not simply, 'Are we ready to start?' It is, 'Have we established the conditions that will allow this project to succeed?'

References

[1] Infrastructure and Projects Authority (2020) Improving Major Project Delivery: The Project Initiation Routemap. London: Cabinet Office.

[2] Infrastructure and Projects Authority (2020) Setting Up for Success: The Importance of Front-End Loading. London: Cabinet Office.

[3] Association for Project Management (2025) What is project sponsorship? Guidance based on the APM Body of Knowledge, 8th edition. Princes Risborough: APM.

[4] Association for Project Management (2025) What is governance? Guidance based on the APM Body of Knowledge, 8th edition. Princes Risborough: APM.

[5] HM Treasury (2026) The Green Book: Central Government Guidance on Appraisal and Evaluation. London: HM Treasury.

[6] Flyvbjerg, B. and Gardner, D. (2023) How Big Things Get Done. New York: Currency.

[7] Infrastructure and Projects Authority and HM Treasury (2014) Infrastructure Procurement Routemap: A Guide to Improving Delivery Capability. London: HM Treasury.

[8] Project Management Institute (2015) Project Sponsorship. Newtown Square, PA: PMI.

Download the paper