Stakeholder alignment is a structure, not a workshop
Chaos on a capital project is usually blamed on people. The research points elsewhere: unranked objectives, no written rule for conflicts, and nobody who owns the ranking. Here is how to test yours.
October 22, 2026 · 5 min read · Marcel Deurhof
When a capital project starts to feel chaotic, the first explanation on offer is usually a person. The contractor's project manager is difficult. Operations keeps reopening settled scope. Finance will not decide. That reading is comfortable, and it is almost always wrong. What gets called chaos is normally a structural problem, and the piece of structure that is missing is stakeholder alignment.
Alignment is a loaded word, so start with a definition from people who researched it. Griffith and Gibson describe alignment on capital projects as the condition where the appropriate participants are working within acceptable tolerances toward a uniformly defined and understood set of project objectives. Note what that does not say. It does not say everyone agrees. It says the differences are pointed at the same ranked objectives.
Disagreement about priorities is the normal state
Their study covered 20 industrial capital facility projects from 13 owner organisations, about 2.2 billion dollars of authorised cost, with input from more than 100 practitioners. The same paper reports an earlier study of 62 projects in which business managers, project managers and operations managers did not agree on the priority of the project goals. Not on the goals. On their order.
That is worth sitting with. On a project whose business case rests on an in-service date, the operations manager is protecting turndown and maintainability, the project manager is defending the estimate, and procurement is defending the award schedule. Nobody is behaving badly. Each of them is doing the job properly against a different first priority. From the inside, that friction looks exactly like a personality problem.
Alignment shows up in the data as structure
A 2008 TU Delft study built on Shell's project assurance database, which held 589 projects, 458 of them with assurance review data, tested a long list of front-end inputs against cost and schedule outcome indicators. Three inputs correlated with two or more of those indicators: the front-end loading index, the team development index, and the occurrence of major late design changes. Definition and team on one side, late change on the other. The author presents them as trends from one company, not proof.
The late change half of that pair is the expensive half. Ibbs, Nguyen and Lee set out the established position in their review of quantified change impacts: late project change damages labour productivity more than early change does. Misalignment is never free once it surfaces. It is only cheaper when it surfaces in a room than when it surfaces on a pipe rack.
What a ranked objective set looks like
Alignment is not a kickoff workshop, a charter slide or a set of shared values. It is three artefacts: a forced ranking of the objectives, a written rule for what happens when two of them collide, and a named person who owns the ranking. If those three do not exist in writing, the project is running on individual interpretation, and interpretation diverges under pressure.
Five questions worth asking in any review:
- Is there one dated document that ranks cost, schedule and operability against each other? Listing all three as critical is not a ranking.
- Does it state what happens when two of them conflict, with a value threshold and the name of the person who decides above that threshold?
- Were operations and maintenance in the room when it was written, or informed afterwards?
- When scope last changed, was the ranking the reference used to decide, or did the loudest stakeholder decide?
- Does the ranking still match the business case the funding was approved against?
The first question matters more than its plainness suggests. In a 2024 study of 66 engineers and project managers on Saudi road and pipeline projects, clarity of priorities between cost, schedule and project features was one of four alignment issues that survived into the regression model, together explaining about 72 percent of the variance in how respondents rated project success. That is self-rated success in one country and two project types, so treat it as a signal, not a benchmark.
A test you can run this week
Pick five people: the owner's project manager, the business or asset owner, the operations representative, the contractor's project manager, and the cost or procurement lead. Ask each of them separately, in writing, three questions. If only one objective could be protected, which one is it. Which document says so. Who decides when it is contested.
Two thresholds make the result actionable. If two or more of the five name a different first priority, the team is aligned on activity and not on direction, and every contested decision from here will be re-litigated. If three or more cannot name a document, the ranking exists only in the heads of whoever was at the last steering meeting, which means it will change when the attendance does. Neither finding is about the people answering, and both are repairable in days. It is the first structure we rebuild on a project already in execution, ahead of any replanning. The work behind that view is summarised at a glance.
Run the test on the project that feels chaotic right now, before the next gate or the next change order. The answers take an afternoon to collect, and they tell you which of the two problems you actually have.
Is your project in delay?
We bring structure to projects that have lost it.
More from M2DP
What belongs in a pre-FEED if you want to reach FID
Most projects that stall before the investment decision were underdefined two gates earlier. What a pre-FEED has to deliver, and which estimate class it can honestly support.
EPC Project Management Strategies That Actually Reduce Chaos
Most EPC project problems are visible long before they become expensive. This article sets out the strategies we apply on energy and industrial projects: governance that gets used, contracting strategies that fit the scope, and recovery.
Open book estimate: when it works, and when it does not
Opening the contractor's cost build-up gives you the right to see how a number was made. It does not tell you whether the number is reasonable, and those are two different capabilities.
If this article matches a project you are running, one email is enough to start.
Get in touch