Look at the attendance list for your largest programme board. Count the people whose own results move if the benefits fail to arrive. In most organisations the answer is one, and they are also paying for it.
A programme board typically contains three kinds of people. There is someone representing the money — a sponsor, an executive, whoever signed the funding. There are people representing the build — the delivery lead, technical directors, major suppliers. And there are attendees: interested parties, subject matter experts, a representative from the affected business who comes when the agenda concerns them.
That third group is the one worth examining. The benefits of the programme will be realised, if they are realised at all, by people in the operational business changing how they work. Those people are represented on the board by someone who is present but not seated — consulted, informed, occasionally asked to comment, and holding no formal position in the structure that governs the thing.
This is not an oversight. It reflects an assumption that runs through most governance design: that the board's job is to get the thing built, and that using it is somebody else's problem, later.
The Strategic Context
There is a governance structure that does not make that assumption, and it is worth examining even though its particular expression is now two decades old.
Rankins, comparing two project management methods [SOURCE DETAILS REQUIRED — no venue or date is printed on the paper; file metadata indicates 2007 and the filename of a second supplied copy indicates an Australian Institute of Project Management conference, neither of which confirms the citation], describes a board with three named interests. A Project Executive represents the interests of the business funding the project. One or more Senior Suppliers represent those who will be creating the specialist products. And one or more Senior Users represent the interests of those who must take the products delivered by the suppliers and deliver benefits to the organisation.
Two qualifications are essential and are frequently dropped when this structure is cited. First, the three seats are not equal. Rankins frames the design as a requirement for a single point of accountability — the Executive — with the Senior User and Senior Supplier as supporting roles. This is not a committee that votes. It is one accountable person with two constituencies formally represented alongside them.
Second, the structure is lighter than its formality suggests: only one board meeting is formally mandated in the method he describes, to approve the initiation document and the first stage plan. Every other board decision may be reached through an informal process at the board's discretion. The design is about who is constituted, not about how often they convene.
The method also asks something specific of the people occupying these seats. Rankins notes that the full benefit of the approach cannot be realised if board members do not act like board members — which is a polite way of saying that the structure fails if the seats are filled by delegates reporting back rather than by people exercising judgement.
What Leaders Commonly Misread
The first misreading is that a user representative is a stakeholder. The distinction is between being consulted and being constituted. A stakeholder is someone whose interests should be considered; a seated interest is someone whose representative sits in the governing structure and whose acceptance the structure requires. Classifying people by their influence over what a programme is for is a genuinely useful discipline with its own logic, treated in [Related article: Drivers, Supporters and Observers: Who Is Allowed to Change What Your Programme Is For]. That is a mapping exercise. This is a constitutional one, and the two answer different questions.
The second misreading is that the sponsor already represents the benefits. The sponsor represents the business case, which is not the same thing. The business case contains benefits, but the sponsor's exposure is typically to the investment — did we spend what we said, did we get what we bought. The exposure to whether the benefit actually materialises sits with the operational leader whose service, cost base or capability was supposed to improve, and that person is frequently not the sponsor.
The third misreading is that this is solved by naming a benefit owner at initiation. Naming the receiving function and its accountable leader at the outset is a genuine and necessary remedy, and it is the one already argued in [Related article: The Hidden Cost of Putting Work Into Project Form]. Naming and seating are different acts. A named benefit owner who does not sit in the governing body finds out about decisions that shape their future operating environment after those decisions are made. The delta this article addresses is narrow and specific: not who owns the benefit, but whether that owner has a seat while the choices that determine the benefit are being taken.
A fourth misreading concerns what a programme is. The teaching material behind this dataset defines a programme as something that contributes a specific group of deliverables to meet business unit goals — an aggregation of outputs. Morris and Jamieson report that most of the companies they studied considered programme management to emphasise the management of business benefits, alongside the ideas of product, brand or platform management. The first definition makes the board's job to assemble deliverables. The second makes it to produce an outcome. A board constituted for the first will not spontaneously do the second.
Reframing the Issue
The reframing is to treat board composition as a statement about what the programme is accountable for, and to read it as such.
A board of money and builders is a board accountable for delivering a thing on terms. That is a coherent accountability and many programmes need nothing more — a substation replacement, a regulatory implementation with a defined output, a plant relocation. Where the benefit follows automatically from the existence of the deliverable, the composition is correct.
The composition becomes wrong precisely where the benefit depends on behaviour. A case management platform for a local council delivers no benefit from existing. It delivers benefit when caseworkers use it in place of their current workarounds, which they will do if the design accommodates how the work actually runs and will not if it does not. Every decision that determines this is taken during delivery, in trade-offs about scope, sequencing and configuration, at a table where the caseworkers' representative attends when invited.
Two consequences follow.
The seat should be filled by exposure, not by seniority. The right occupant is the person whose own operational results move if adoption fails — usually a service or operations leader two levels below the executive sponsor. Filling the seat with a more senior person who is not exposed reproduces the original problem with better attendance.
Representation is not a veto. This is where the structure must be reconciled with the principle that a stop decision needs a single owner, argued in [Related article: Sponsorship Is an Office, Not an Endorsement]. That article is right, and the reconciliation is the one the source itself makes: the Executive holds the decision and is the single point of accountability; the Senior User holds a seat, a voice and a formal role in acceptance. A three-seat board is not a committee with three votes. It is one decision-maker who cannot avoid hearing two constituencies.
Strategic Analysis
What the seated user actually changes
Three things, in practice.
Trade-offs get made with the operating consequence in the room. When a scope reduction is proposed at month fourteen — as one always is — a board of money and builders will assess it on cost, schedule and technical risk, all of which they can see. The item most likely to be cut is the one that is expensive to build and whose value is diffuse, which is frequently the part that makes the thing usable. A seated user changes what is visible at that moment.
Acceptance means something. In the structure Rankins describes, the board formally accepts the products. Where the user interest is seated, acceptance carries the judgement of someone who will have to live with the result. Where it is not, acceptance is a signature from people who will not, and it degrades into a completeness check against a specification.
The receiving organisation prepares. A seated representative spends a year watching the thing take shape. That is a year of preparation the operational business would not otherwise have — of adjusting processes, planning training, warning their own people. The value of this is difficult to quantify and easy to observe in its absence.
The seat is also a channel
A seated user representative spends a year watching the work take shape, which makes them the best-placed person in the structure to notice that a premise in the business case has stopped holding. Whether the organisation has anywhere to send that observation is a separate question, examined in [Related article: What Your Projects Know That Your Strategy Doesn't]. The seat generates the finding; something else must be able to receive it.
The business case as the instrument the three seats share
Rankins describes the business case in the method he examines as updated at each management stage boundary with actual costs to date, better estimates of future costs, and better estimates of benefits expected. His stated reason is that corporate or programme management will hold the board members accountable for delivery of the commitments in that case — both costs controlled and benefits realised.
That is the mechanism that makes the third seat consequential rather than decorative. If the board is answerable for benefits as well as costs, then the person who understands whether the benefit remains achievable is not an optional attendee. And note what is being said about accountability: the board members, plural, are held to the case. Not the delivery leader.
What that revised case is then used to decide — whether the initiative continues — is a separate instrument with its own logic, examined in [Related article: What a Stage Gate Is Actually For]. The point here concerns only who is accountable for the numbers in it.
Note also what the board is renewing at each of those boundaries. The authority it grants the delivery leader is itself bounded and expiring, and the mechanics of that grant are examined in [Related article: Authority With an Expiry Date]. Composition determines who assesses the renewal; the instrument determines what the renewal actually is.
The failure mode of the structure
The structure fails in a predictable way, and Rankins names it: board members who do not act like board members. In practice this means a Senior User who attends as a delegate, reports back to their own management, and brings no judgement of their own; or a seat filled by someone with no authority to commit their function to anything.
This failure is common enough that it is worth designing against. The seat needs someone who can say my function will be ready and make it true. If the occupant must consult before every commitment, the seat has been filled by a messenger and the board has gained an attendee rather than a constituency.
Where the composition is genuinely optional
Not every initiative needs three seats. Where the deliverable's value is realised on acceptance — an asset that simply has to exist and work — the user interest and the funding interest are effectively the same, and a two-part structure is honest rather than deficient.
The test is whether anyone has to change what they do for the benefit to arrive. Where the answer is no, seat two interests. Where the answer is yes, the third seat is not a courtesy.
Decision Framework
Five steps for any programme above a material threshold.
1. Ask whether the benefit requires behaviour change. If no, a two-interest board is correct and this framework stops here. If yes, continue.
2. Identify who is exposed. Name the individual whose own operational results deteriorate if adoption fails. Not their director; the person carrying the number.
3. Seat them, and say what the seat carries. Formal representation, a voice in trade-off decisions, and a role in acceptance — not a vote on continuation, which belongs to the accountable executive. Write this down, because in its absence the seat will be interpreted as either decorative or as a veto, and both interpretations cause trouble.
4. Test whether the occupant can commit. Ask them directly whether they can commit their function to a readiness date without consulting. If not, either give them that authority or seat someone who has it.
4a. Check that the commitment is deliverable. A readiness commitment is a capacity commitment, and in matrix organisations the people required are usually already allocated elsewhere — see [Related article: There Is No Such Thing as Half a Project Manager]. A seat occupied by someone who can commit but whose function has no spare capacity produces a confident promise and a missed date.
5. Make the shared instrument explicit. One document — the business case or its equivalent — carrying costs and benefits, revised at each decision point, with all seated interests accountable for it. If benefits appear only at approval and never again, the third seat has nothing to hold.
From Strategy to Execution
Immediate. Take the programme with the largest behavioural dependency and check its board composition against step two. In most organisations the exposed operational leader is either absent or attends without a defined role, and establishing which takes one look at the terms of reference.
Medium term. Change the programme charter template to require a named user interest with a stated seat, for any initiative where benefit depends on behaviour change. This is a small structural amendment and it does more than any amount of engagement planning, because it changes who is present when trade-offs are made rather than who is informed afterwards.
Long term. Build the expectation that operational leaders serve on programme boards as part of the job rather than as an imposition. This is a cultural change and it is slow, and the argument that carries it is not about governance. It is that the operational business is going to live with the result either way, and the only question is whether it gets a say while the result is still being determined.
Signals to Monitor
- Acceptance signed by people who will not use the thing. Check the last three acceptance records. If no signature belongs to the receiving function, acceptance is a completeness check.
- Scope reductions that fall disproportionately on usability. Track what gets cut at the mid-programme squeeze. A consistent pattern of cutting adoption-critical scope indicates who was in the room.
- Readiness commitments made on the operational function's behalf. Where the delivery team states when the business will be ready, the business is not represented.
- Benefits absent from the board pack after approval. If the case's benefit numbers are never revisited, the third seat has no instrument.
- User representatives who consistently take items away. A seat filled by a messenger. Worth addressing directly with the individual's own management rather than treating as a personal failing.
- Post-implementation reviews that discover well-known problems. Where the review surfaces issues the operational business knew about during delivery, the information existed and the structure had no way to receive it.
Questions for the Leadership Team
- On our largest programme, who sits on the board because their own results move if the benefits do not arrive?
- When scope was last reduced on that programme, who was in the room — and what got cut?
- Does our acceptance process require a signature from the function that will operate the result?
- Are the benefit numbers in our programme business cases revised at each decision point, or fixed at approval?
- If we seated an operational leader on each major programme board, what would they have to give up — and is that cost larger than the adoption failures we currently absorb?
- Do our board members act like board members, or like delegates carrying a brief from elsewhere?
Closing Perspective
Governance design is usually discussed as process — what gets reviewed, how often, against what criteria. Composition is treated as a logistical question, settled by who is available and senior enough.
But composition is the more consequential decision, because it determines what is visible at the moment a trade-off is made. A board that represents the money and the build will make excellent decisions about money and build, and will discover the adoption problem after the adoption problem has become permanent.
The structure that seats the user interest is not new, not complicated, and not expensive. It requires one additional person at the table and a written statement of what their seat carries. What it buys is that the organisation's most consequential trade-offs are made in the presence of someone who will have to live with them — which is, in the end, what a governing body is for.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.