A sponsor can approve a transformation that satisfies governance requirements while the people who must use, fund, operate or trust the new system receive less value than expected.
Who is the customer of a transformation?
The answer often appears obvious when the project documents identify a sponsor, steering committee or Board as the authority that approves scope and accepts delivery. Yet authority to approve is not the same as receiving the value the investment exists to create.
This distinction matters because complex transformations affect several groups simultaneously.
A Board may want financial sustainability. Customers may want better service. Employees may need a workable operating environment. Regulators may require compliance. Partners may depend on reliability. Communities may care about social or environmental consequences. Operational leaders must inherit the new capability and make it perform after the program closes.
If governance treats the sponsor as the sole customer, the transformation can become optimised for executive acceptance rather than enterprise value.
The Strategic Context
Sponsors are essential.
They provide authority, secure resources, resolve escalated decisions and protect strategic intent. Without accountable sponsorship, major change drifts.
The mistake is not having a powerful sponsor. The mistake is confusing governance ownership with value ownership.
A hypothetical relocation program illustrates the problem. Imagine a transformation in which the Board and chief executive are listed as customers for several project objectives, including successful asset relocation, profitability and budget completion. Yet the same transformation also changes the experience of visitors, the working environment of employees, the welfare of animals, the obligations of government agencies, the interests of sponsors and the needs of researchers and partners.
The Board can accept the deliverables. It cannot personally experience every outcome.
That creates a governance challenge: the organisation needs a decision system that preserves executive accountability while representing value across the wider stakeholder system.
Related article: Stakeholder Engagement Is a Decision System, Not a Communication Plan
What Leaders Commonly Misread
The first common misread is assuming that the person who signs the acceptance document is the customer.
Acceptance is a control mechanism. Customer value is an outcome.
The second is assuming that stakeholders can be handled primarily through communication. Communication matters, but a stakeholder whose work becomes harder, whose access deteriorates or whose obligations increase does not have a communication problem. That stakeholder has an operating-model problem.
The third is treating stakeholder objectives as additive.
Leaders sometimes create long lists of stakeholder needs and assume the transformation should satisfy all of them equally. That is rarely possible. Different groups can want contradictory outcomes. Greater public access may increase operating complexity. Lower cost may reduce service features. Faster transition may increase disruption. Stronger control may reduce local flexibility.
Stakeholder governance therefore requires choices, not just inclusion.
The fourth misread is assuming that executive approval proves benefits.
A project can deliver every agreed output and receive formal acceptance while the expected customer behaviour, workforce adoption, commercial performance or social outcome fails to materialise.
Related article: A Better KPI Does Not Prove the Program Created Value
Reframing the Issue
Leaders should distinguish four roles that are often collapsed into the word "customer":
The sponsor owns authority and strategic accountability.
The beneficiary receives an intended advantage from the change.
The operator must use and sustain the new capability.
The affected stakeholder experiences consequences, whether or not they are direct beneficiaries.
One person or group can occupy several roles, but the roles are analytically different.
This distinction changes governance conversations.
Instead of asking, "Has the sponsor accepted the solution?", leadership asks:
- Does the solution still serve the strategic purpose?
- Are intended beneficiaries receiving value?
- Can operational owners sustain the capability?
- Are unacceptable impacts emerging elsewhere?
- Have stakeholder trade-offs changed enough to require a decision?
The purpose is not to give every stakeholder veto power. It is to make the value system visible before executive authority is exercised.
Value Is Distributed Across the Enterprise
Transformation value rarely appears in one place.
Financial value
Boards and funding authorities may focus on affordability, revenue, cost reduction, return on capital or financial sustainability. These are legitimate enterprise concerns, but they cannot be the only test where the organisation exists to produce broader public, customer or mission outcomes.
Customer value
Customers experience accessibility, quality, reliability, safety, convenience and trust. Their behaviour may determine whether a transformation becomes economically sustainable.
A new facility that satisfies construction requirements but reduces accessibility can weaken the very demand assumptions supporting the business case.
Operational value
Employees and operational managers experience workload, process friction, system usability, role clarity and capability gaps. Their perspective matters because benefits are realised through ongoing operations, not merely through project completion.
Related article: Benefits Are Realised in Operations, Not in the Program Office
Strategic and mission value
Some organisations must protect outcomes that are not reducible to near-term financial return: public safety, conservation, research, national capability, regulatory obligations or institutional legitimacy.
These outcomes can be strategically decisive even when they do not appear in a conventional customer-satisfaction measure.
Ecosystem value
Partners, suppliers, research institutions, sponsors, governments and communities can either strengthen or weaken the new operating model. Their support may determine access to resources, knowledge, funding or legitimacy.
The organisation therefore needs an explicit model of how these value dimensions interact.
Decision Framework
A practical approach is to create a Transformation Value Map with five questions.
1. Who authorises?
Identify the sponsor, Board, investment committee or accountable executive. Clarify what decisions they own and what evidence they require.
2. Who benefits?
Identify each intended beneficiary and the specific outcome expected for them. Avoid generic labels such as "stakeholders benefit". Define the change that should be observable.
3. Who operates?
Identify who will inherit the capability after delivery. If the operating owner is unclear, the benefit owner is usually unclear as well.
4. Who bears downside?
Identify groups that absorb disruption, cost, risk, reduced access, workload or other dis-benefits. Some impacts may be acceptable, but they should be conscious decisions.
5. What trade-off rules apply?
Define which value dimensions are non-negotiable and which can be balanced.
A simple governance table can make this concrete:
| Stakeholder role | Value sought | Potential downside | Decision owner | Evidence |
|---|---|---|---|---|
| Sponsor | Strategic outcome and investment control | Loss of confidence or capital | Board/executive | Portfolio and benefit evidence |
| Customer/user | Better experience or service | Reduced access, quality or trust | Service owner | Behaviour and experience measures |
| Operator | Sustainable capability | Workload, skill gaps, process friction | Operational executive | Readiness and performance measures |
| Regulator/public authority | Compliance and public-interest outcome | Control failure or external harm | Accountable executive | Assurance evidence |
| Partner/community | Reliable relationship and mutual value | Disruption or legitimacy loss | Relationship owner | Engagement and outcome evidence |
This does not replace executive judgement. It gives judgement a better picture of what is being traded.
From Strategy to Execution
Immediate action
Review project charters, benefit maps and acceptance criteria.
Where "customer" is used, replace the ambiguous term with the specific role: sponsor, beneficiary, operator, regulator, partner or affected stakeholder.
Then ask whether the current governance forums hear evidence from each role that materially affects value.
This does not require every stakeholder to attend every meeting. Representation can come through operational metrics, research, user testing, structured engagement, independent assurance or accountable executives.
Medium-term capability building
Create benefit ownership outside the project hierarchy.
Operational leaders should own the outcomes they must sustain. Customer or service leaders should own experience measures. Finance should test economic performance. Risk and assurance functions should test consequences that delivery teams may underweight.
The program should integrate these perspectives into decision points rather than report them as separate workstreams.
Related article: Program Governance Begins With Decision Rights, Not Committees
Leadership should also distinguish between consultation rights and decision rights. Stakeholders can be deeply affected without possessing formal authority. Governance needs a transparent method for considering their interests without creating confusion over accountability.
Long-term strategic positioning
After the transformation enters business as usual, the Board should review whether the original sponsor-defined success criteria still represent enterprise value.
Sometimes the most important evidence emerges only after use: changing customer behaviour, unanticipated employee impacts, new stakeholder expectations or benefits that prove weaker than assumed.
A mature organisation does not defend the original definition of success simply because it was approved. It updates its understanding when evidence improves.
Signals to Monitor
Watch for signs that governance has become sponsor-centric rather than value-centric:
- project reports dominated by cost, schedule and executive approvals;
- high formal acceptance but weak customer adoption;
- operational teams describing the delivered solution as impractical;
- benefits that have no accountable owner after project closure;
- repeated stakeholder objections being classified as communication issues;
- service measures deteriorating while delivery measures remain green;
- Board papers that describe affected groups collectively without distinguishing their interests;
- success criteria that can be achieved without changing user or organisational outcomes.
These signals indicate that governance is measuring whether the transformation was accepted, not whether it worked.
Questions for the Leadership Team
- Who receives the intended value, and are they the same people who approve the investment?
- Which operational leaders will inherit the new capability and own its benefits?
- Which stakeholders bear material downside without holding formal decision authority?
- Where do our current success measures privilege sponsor convenience over enterprise outcomes?
- What evidence would show that customers or users are worse off despite formal project success?
- Which stakeholder trade-offs require Board-level judgement rather than project-level resolution?
- How will we revisit the definition of success after the transformation enters normal operations?
Closing Perspective
Executive sponsorship gives transformation authority. It does not automatically give transformation insight.
The sponsor sees the investment from a position of accountability. Customers, operators, partners and affected stakeholders see different parts of the system. Good governance combines those perspectives without surrendering decision rights.
The central leadership task is therefore not to make every stakeholder equally satisfied.
It is to ensure that executive acceptance reflects a credible view of enterprise value.
A signed completion certificate can prove that governance has accepted the work.
Only outcomes can prove that the transformation deserved the investment.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.