Knowing When You Are Doing It Right: What Truly Matters for the Success of a Project or Programme

There is a question that deserves to be asked more often in project and programme environments, and which is asked far less than it should be: how do you actually know that things are going well? Not on paper, not in the status report, not in the confident tone of the last steering committee presentation, but genuinely, in reality, in the way that the people doing the work and the people receiving its outputs would describe it if asked honestly.

For many delivery professionals, the default answer involves three numbers: on time, on budget, on scope. The iron triangle, as it is known, has provided the framework for project success measurement for decades. It is not wrong, exactly, but it is insufficient. Programmes that complete on time and within budget while delivering outputs that nobody uses, that communities resist, or that damage the organisation's capacity to operate have not succeeded. They have completed. The distinction matters enormously, and the confusion between the two is one of the most persistent sources of waste in organisational life.

Understanding what truly matters for delivery success, and developing the discipline to monitor it in real time rather than after the fact, is one of the most important capabilities a delivery professional can develop and one of the most valuable contributions a consulting partner can make.

Beyond the Iron Triangle: Why Traditional Measures Are Necessary but Not Sufficient

The iron triangle of time, cost, and scope captures something real and important. Projects do need to be delivered within a defined timeframe, to an agreed budget, and to a scope that reflects what the organisation actually needs. These constraints create the discipline that prevents delivery from becoming an open-ended exercise in spending. They provide the basis for planning, for accountability, and for the governance conversations that keep a programme on track.

The problem is not with the iron triangle itself but with what is absent from it. Time, cost, and scope are all measures of input and process. They tell you whether the right activities are being completed in the right sequence at the right rate of expenditure. They say almost nothing about whether the outputs being produced are the right ones, whether those outputs will be adopted and used, whether the organisation that receives them is ready and willing to change the way it works, or whether the investment will ultimately generate the return that justified the business case.

A programme can be green on all three dimensions of the iron triangle while being simultaneously red on every dimension that matters to the long-term health of the organisation. This is not a hypothetical scenario. It is a recurring pattern in organisations that have conflated delivery performance with delivery success and that have built their reporting structures around the former while neglecting the latter.

What Truly Matters: The Dimensions of Genuine Delivery Success

If the iron triangle is necessary but insufficient, what should sit alongside it? The answer lies in a set of dimensions that together describe not just whether a programme is being delivered but whether it is being delivered in a way that will produce lasting, genuine value.

Benefits Realisation

The most fundamental test of programme success is whether the benefits articulated in the business case are actually realised, by whom, to what degree, and by when. Benefits realisation is not a post-project activity; it is a discipline that must be designed into the programme from the outset, with baselines established before delivery begins, interim measures tracked through delivery, and a governance mechanism that maintains accountability for realisation well beyond go-live.

The most reliable sign that benefits realisation is being taken seriously is the existence of a named benefits owner who is distinct from the project manager, who is measured on realisation rather than delivery milestones, and who carries accountability into the operational phase of the programme. Where that role does not exist, benefits realisation is at risk regardless of how well the technical delivery proceeds.

Stakeholder Confidence and Adoption

Delivery success requires that the people who will live with the outputs of a programme are ready, willing, and equipped to use them. This means that the receiving organisation has been involved in shaping the design, has been given the time and support to prepare, and has the capability to operate in the new way that the programme requires of it. It means that end users, whether internal staff or external customers and citizens, experience the change as an improvement rather than an imposition.

Adoption is the acid test of change readiness. If users are finding workarounds within weeks of go-live, if shadow systems are appearing alongside new platforms, or if the volume of support calls following launch suggests widespread confusion, these are not teething problems. They are evidence that the change management dimension of the programme was inadequate, regardless of what the delivery plan said about it.

Team Health and Psychological Safety

The condition of the delivery team is one of the most reliable leading indicators of programme health, and one of the most consistently underweighted. A team that is clear on direction, trusted to raise problems without fear of blame, adequately resourced, and led with consistency and honesty will outperform a team under sustained pressure, operating with unclear priorities and without the psychological safety to flag concerns early.

Psychological safety, the belief held by team members that they can speak up, ask questions, disagree, and raise risks without personal consequences, is not a cultural luxury. It is a functional requirement for early warning systems to work. Problems that are caught at team level cost a fraction of the problems that are caught at board level. The programmes that consistently deliver well are those where the distance between a concern being identified and a concern being acted upon is short, and where that distance is short because the team trusts that raising it is safe.

Sponsor Engagement and Decision Quality

The quality of a programme's sponsorship is one of the strongest predictors of its eventual success or failure, and it is a factor over which the delivery team has more influence than is often assumed. An active, engaged sponsor who makes decisions promptly, runs interference with the wider organisation, and communicates personal commitment to the programme creates conditions that accelerate delivery and build credibility. An absent, disengaged, or risk-averse sponsor creates conditions where decisions escalate unnecessarily, where political obstacles accumulate, and where the programme's authority in the organisation gradually diminishes.

Monitoring sponsor engagement means tracking not just whether the sponsor attends governance forums but whether they are making decisions when presented with them, whether their communications to the wider organisation are consistent with the programme's narrative, and whether they are visible to the delivery team as an advocate rather than a reviewer.

Governance Integrity

Governance is functioning well when the right decisions are being made by the right people, on the basis of honest and reliable information, at the right level of the organisation. These three conditions are each individually necessary and together insufficient if any one of them is absent.

The most dangerous governance failure is not the absence of committees or reporting structures. It is the presence of governance that looks functional but that operates on curated information. When programme teams present only good news to steering committees, when risks are downgraded to avoid difficult conversations, and when RAG ratings reflect political judgement rather than operational reality, the governance structure becomes an obstacle to delivery rather than an enabler of it. It creates the appearance of control while removing the organisation's ability to make the corrections that control exists to enable.

Reading the Real-Time Signals: How to Know You Are Doing It Right

The dimensions described above are not easily captured in a single dashboard metric or a weekly status report. They require a different kind of attention: one that combines quantitative measures with qualitative intelligence, that values what the team says in informal conversations as much as what the plan says in formal reports, and that treats discomfort as a signal rather than a problem to be managed.

There are signals, however, that are reliable indicators of genuine delivery health when seen together. The following table sets out what those signals look like across the key dimensions of programme success, alongside the warning signs that indicate a dimension is under strain.

The Role of Honest Reporting in Delivery Health

Running through every dimension of genuine delivery success is a common thread: honesty. The organisations that deliver well are those in which honest reporting is valued, protected, and structurally enabled. The organisations that struggle are those in which the incentive structure, whether formal or informal, rewards the appearance of progress over an accurate account of reality.

Honest reporting does not mean pessimistic reporting. A programme that is genuinely performing well should be able to demonstrate that performance with confidence. But a programme that is performing well in some areas and facing genuine challenges in others should be able to present both halves of that picture without the challenging half being softened, deferred, or omitted.

The delivery professional's responsibility here is more than technical. It requires the courage to present difficult information to powerful audiences, the skill to frame that information constructively and with a clear account of the proposed response, and the confidence that the organisation's governance culture will treat honest reporting as an asset rather than a liability. Where that culture does not yet exist, building it is itself part of the delivery challenge, and it is one of the areas where experienced consulting support can make a material difference.

Redefining Success: The Difference Between a Programme That Completes and One That Delivers

There is a final and important distinction to draw between a programme that completes and one that genuinely delivers. Completion is a milestone: a system goes live, a report is published, a facility opens, a contract is signed. Delivery is a condition: the organisation is functioning better than it was, the intended beneficiaries are experiencing the promised improvement, and the investment has generated the return that justified it.

These two things can coincide, and the best programmes ensure that they do. But they are not the same thing, and treating them as synonymous is one of the most persistent sources of disappointment in organisational change. The difference between them is measured not at go-live but six months, twelve months, and two years afterwards. It is measured in whether the business case assumptions held, in whether the users who were supposed to benefit did benefit, and in whether the organisation has more capacity, more capability, or more resilience than it had before.

Organisations that consistently achieve this kind of genuine delivery success share a set of characteristics: they define success in outcome terms before the programme begins; they maintain accountability for benefits realisation beyond go-live; they invest in change readiness as seriously as they invest in technical delivery; they build governance structures that surface the truth rather than manage it; and they develop delivery cultures in which psychological safety, honest reporting, and continuous learning are operating norms rather than aspirational values.

Frameworks That Support Meaningful Measurement

Several established frameworks support a more complete approach to measuring and managing delivery success.

The Benefits Dependency Network

Developed within the Managing Benefits framework, the benefits dependency network maps the chain of causality between programme outputs, the business changes those outputs enable, and the ultimate benefits the organisation expects to realise. It makes the logic of the business case visible and testable, and it provides the basis for a benefits measurement approach that tracks not just whether outputs were delivered but whether the conditions for benefit realisation have been established.

Earned Value Management

EVM integrates scope, schedule, and cost performance into a single coherent picture of programme health. It enables delivery teams to distinguish between a programme that is on budget because it is progressing slowly and one that is on budget because it is genuinely efficient. Its limitations lie in what it does not measure, which includes quality, stakeholder sentiment, and benefits trajectory. It is a powerful tool when used alongside qualitative measures rather than instead of them.

OKRs in a Delivery Context

Objectives and Key Results, adapted for programme use, shift the measurement conversation from activity completion to outcome achievement. They provide a framework for expressing programme intent in terms that are meaningful to the receiving organisation and its end users, and they create a cadence of honest assessment against aspirational but grounded targets. They are particularly effective in programmes where the path to the outcome involves genuine uncertainty, and where rigid milestone-based reporting would create perverse incentives to deliver the plan rather than to respond to what is being learned.

The Five Case Model

Used widely in UK public sector investment appraisal, the Five Case Model structures the justification for investment across five dimensions: strategic fit (does it align with organisational direction?), economic value (is it the best use of public resource?), commercial viability (can it be procured and contracted effectively?), financial affordability (can it be funded?), and management achievability (does the organisation have the capability to deliver it?). Revisiting the Five Case Model at key programme milestones provides a structured mechanism for testing whether the original justification remains sound, whether assumptions have held, and whether the programme should continue, adapt, or stop.

The Hervey Dickens Perspective

The question of whether a programme is truly succeeding cannot be answered by looking at a Gantt chart or a budget tracker alone. It requires a broader, more honest, and more disciplined form of attention: one that holds benefits, people, governance, and organisational readiness in view simultaneously, and that is willing to hear difficult things early enough to respond to them effectively.

At Hervey Dickens Consulting, we work with leadership teams to build the delivery discipline that produces genuine success rather than the appearance of it. That means designing governance structures that surface reality rather than managing it, investing in change readiness as a first-order delivery concern, and maintaining accountability for benefits realisation well beyond the go-live date. Our digital services are built on the conviction that technology alone does not deliver outcomes: it is the combination of clear intent, disciplined governance, honest measurement, and genuine engagement that determines whether an organisation ends up better than it was before.

Knowing that you are doing it right is not a feeling. It is a set of observable conditions, present in the team, in the data, in the stakeholder relationships, and in the governance conversations, that together constitute reliable evidence of genuine delivery health. Building and sustaining those conditions is the work. Everything else is administration.