Why transformation governance problems are discovered too late
Ownership Before Mobilisation | Part 1 of 3
Cato Rockne-Meyer
4 September 2026
Cato Rockne-Meyer
4 September 2026
Transformation programmes often begin with a strong focus on scope, technology, budgets and delivery plans. Yet some of the hardest problems emerge later from unresolved ownership, unclear decision rights and insufficient client-side capacity. This first article in the Ownership Before Mobilisation series explores why these issues are so often deferred until delivery is already under way.
Transformation programmes usually begin with considerable attention to scope, technology, delivery plans, budgets and milestones. Yet some of the decisions that later prove hardest to resolve are much more fundamental:
Programmes often do not realise how important these questions are until they need an answer. A design decision cannot be completed because nobody has clear authority to approve it. A data migration exposes disagreement over which business function owns a critical data set. Different operating units have competing definitions of the same process. Responsibility for delivering a benefit sits somewhere between technology, operations and finance, but no single person is clearly accountable.
These are governance and ownership problems that have surfaced through technology delivery. By the time they become visible, design and delivery may already depend on resolving them. What might have been a relatively straightforward governance discussion during mobilisation can become a programme dependency involving senior stakeholders, competing interests and decisions that are increasingly expensive to change.
- Who owns the business process?
- Who owns the data?
- Who has authority to decide where standardisation ends and local variation begins?
- Who is accountable for the benefits once the programme has delivered the technology?
Programmes often do not realise how important these questions are until they need an answer. A design decision cannot be completed because nobody has clear authority to approve it. A data migration exposes disagreement over which business function owns a critical data set. Different operating units have competing definitions of the same process. Responsibility for delivering a benefit sits somewhere between technology, operations and finance, but no single person is clearly accountable.
These are governance and ownership problems that have surfaced through technology delivery. By the time they become visible, design and delivery may already depend on resolving them. What might have been a relatively straightforward governance discussion during mobilisation can become a programme dependency involving senior stakeholders, competing interests and decisions that are increasingly expensive to change.
Early decisions are often driven by strategy and principles. Later choices can become increasingly tactical, local and reactive, sometimes compromising the overall outcome.
The programme operating model is not the TOM
Another distinction is easy to overlook: the programme operating model and the target operating model are not the same.
The target operating model describes how the organisation intends to operate once the transformation has been implemented. The programme operating model is temporary. It exists to govern, coordinate and deliver the transition.
That temporary model still needs to be designed deliberately. A transformation therefore involves an important intermediate state:
Another distinction is easy to overlook: the programme operating model and the target operating model are not the same.
The target operating model describes how the organisation intends to operate once the transformation has been implemented. The programme operating model is temporary. It exists to govern, coordinate and deliver the transition.
That temporary model still needs to be designed deliberately. A transformation therefore involves an important intermediate state:
Transformation moves deliberately from the as-is through the programme operating model to the target operating model.
Each transition raises its own governance questions:
The right people are usually the hardest to release
The people best placed to take key programme roles are often the people the business can least afford to release. Roles such as Product Owner, Business Lead or Subject Matter Expert require more than availability. They require deep knowledge of how the organisation works, where the exceptions sit, which compromises have accumulated over time and which decisions carry operational consequences.
The ideal candidates are therefore often fully embedded in important business-as-usual roles. Hiring externally is not always an immediate solution because the future operating model may not yet have been agreed. If the organisation has not defined the target roles, responsibilities and capabilities it will need, there may be no permanent role into which a new person can sensibly be recruited.
Backfilling can help, but mainly where the existing business role is sufficiently well understood and can be transferred without losing critical knowledge or creating additional operational risk.
- Who has authority during the programme that they would not normally hold in business-as-usual operations?
- Which decisions move temporarily into programme governance?
- How are business owners involved without creating parallel accountability?
- When does ownership transfer from the programme into the enduring organisation?
- What capabilities must be in place for a safe transfer into the programme operating model and later into the target operating model?
The right people are usually the hardest to release
The people best placed to take key programme roles are often the people the business can least afford to release. Roles such as Product Owner, Business Lead or Subject Matter Expert require more than availability. They require deep knowledge of how the organisation works, where the exceptions sit, which compromises have accumulated over time and which decisions carry operational consequences.
The ideal candidates are therefore often fully embedded in important business-as-usual roles. Hiring externally is not always an immediate solution because the future operating model may not yet have been agreed. If the organisation has not defined the target roles, responsibilities and capabilities it will need, there may be no permanent role into which a new person can sensibly be recruited.
Backfilling can help, but mainly where the existing business role is sufficiently well understood and can be transferred without losing critical knowledge or creating additional operational risk.
Why ownership decisions get deferred
Ownership is often still being worked out when a transformation programme reaches mobilisation. By that point, the organisation may already have spent months aligning senior stakeholders, shaping the business case, engaging vendors and systems integrators, estimating costs and timescales, and securing approval to proceed.
Attention has naturally been concentrated on getting the transformation approved and funded. Detailed questions about who will own future processes, products, data, benefits and decisions can therefore remain unresolved until delivery begins.
1. Approval comes first
The early stages of transformation are usually dominated by executive alignment and investment approval. The Board, Finance, CEO, COO, CTO and other senior stakeholders need to agree on the need for change, the programme objectives, the scope and scale of investment, and the level of risk they are prepared to accept.
Once a sponsor is appointed, the focus shifts to the business case and feasibility, suppliers, indicative solutions, delivery timescales, costs and funding. Ownership questions can consequently lag commercial and delivery planning.
2. The right people are already busy
Transformation programmes depend heavily on people with deep business knowledge. Product Owners, Business Leads and SMEs need to understand current processes, exceptions, dependencies and operational consequences. Releasing the strongest candidates from critical business-as-usual roles creates an immediate capacity problem.
Many organisations also operate under tight FTE and operating-cost constraints, so business functions may be reluctant to give up experienced people or add new headcount. The situation becomes more sensitive where the transformation is expected to change roles, team structures, reporting lines or staffing levels. Reduced FTE may itself be part of the business case.
Managers and individuals therefore have understandable reasons to protect scarce resources and existing positions while the future remains uncertain.
3. The future organisation is still emerging
The target operating model may also be incomplete or confidential. Because it can affect jobs, reporting lines, spans of control and management responsibilities, TOM development is often restricted to a small group.
The delivery team may spend much of the programme without full visibility of the future organisation it is expected to enable. A Product Owner may be appointed before product boundaries are settled. A business lead may be asked to make decisions before enduring accountability is clear. Temporary programme responsibilities may emerge simply to keep delivery moving.
These arrangements may be necessary, but they increase the risk that important process, data and design decisions are made before future ownership has been resolved.
4. Mobilisation can increase the demand
Once the preferred systems integrator is selected, the internal resource requirement can increase further. As contracts, statements of work and delivery plans are developed, additional client-side roles may emerge, including Product Owners, SMEs, architects, test leads, environment support, data owners, change leads and governance support that were not fully visible during the earlier business-case stage.
The SI may also introduce its preferred delivery model and ways of working. What began as an agile transformation can expand into a large, complex programme involving hundreds of people, multiple workstreams and significant coordination overhead.
Scale can create the opposite of the speed it was intended to provide. Scarce SMEs become stretched, decision-making slows, governance forums multiply, and legal, procurement, contracting, hiring and finance can all become constraints.
At the same time, the organisation may need to build new internal competencies in areas such as product management, platform ownership, enterprise data, architecture governance or commercial management. Developing those competencies takes time, executive support and sustained effort. If they are not built early enough, dependence on the SI and vendors can deepen, creating a power imbalance and making future transition harder.
Attention has naturally been concentrated on getting the transformation approved and funded. Detailed questions about who will own future processes, products, data, benefits and decisions can therefore remain unresolved until delivery begins.
1. Approval comes first
The early stages of transformation are usually dominated by executive alignment and investment approval. The Board, Finance, CEO, COO, CTO and other senior stakeholders need to agree on the need for change, the programme objectives, the scope and scale of investment, and the level of risk they are prepared to accept.
Once a sponsor is appointed, the focus shifts to the business case and feasibility, suppliers, indicative solutions, delivery timescales, costs and funding. Ownership questions can consequently lag commercial and delivery planning.
2. The right people are already busy
Transformation programmes depend heavily on people with deep business knowledge. Product Owners, Business Leads and SMEs need to understand current processes, exceptions, dependencies and operational consequences. Releasing the strongest candidates from critical business-as-usual roles creates an immediate capacity problem.
Many organisations also operate under tight FTE and operating-cost constraints, so business functions may be reluctant to give up experienced people or add new headcount. The situation becomes more sensitive where the transformation is expected to change roles, team structures, reporting lines or staffing levels. Reduced FTE may itself be part of the business case.
Managers and individuals therefore have understandable reasons to protect scarce resources and existing positions while the future remains uncertain.
3. The future organisation is still emerging
The target operating model may also be incomplete or confidential. Because it can affect jobs, reporting lines, spans of control and management responsibilities, TOM development is often restricted to a small group.
The delivery team may spend much of the programme without full visibility of the future organisation it is expected to enable. A Product Owner may be appointed before product boundaries are settled. A business lead may be asked to make decisions before enduring accountability is clear. Temporary programme responsibilities may emerge simply to keep delivery moving.
These arrangements may be necessary, but they increase the risk that important process, data and design decisions are made before future ownership has been resolved.
4. Mobilisation can increase the demand
Once the preferred systems integrator is selected, the internal resource requirement can increase further. As contracts, statements of work and delivery plans are developed, additional client-side roles may emerge, including Product Owners, SMEs, architects, test leads, environment support, data owners, change leads and governance support that were not fully visible during the earlier business-case stage.
The SI may also introduce its preferred delivery model and ways of working. What began as an agile transformation can expand into a large, complex programme involving hundreds of people, multiple workstreams and significant coordination overhead.
Scale can create the opposite of the speed it was intended to provide. Scarce SMEs become stretched, decision-making slows, governance forums multiply, and legal, procurement, contracting, hiring and finance can all become constraints.
At the same time, the organisation may need to build new internal competencies in areas such as product management, platform ownership, enterprise data, architecture governance or commercial management. Developing those competencies takes time, executive support and sustained effort. If they are not built early enough, dependence on the SI and vendors can deepen, creating a power imbalance and making future transition harder.
The key mobilisation question is broader than whether the SI can deliver the proposed plan. Can the client organisation absorb, govern and sustain the delivery model required to make that plan work?
Unless this is tested early, nominal ownership can easily be mistaken for effective ownership.
What comes next
Deferred ownership rarely stays contained within governance. It reappears in delivery as slower decisions, workarounds, scaling problems and increasingly fragile assumptions. Part 2 looks at how those governance gaps surface during delivery and how they can gradually change the economics of the transformation and the credibility of the business case.
What comes next
Deferred ownership rarely stays contained within governance. It reappears in delivery as slower decisions, workarounds, scaling problems and increasingly fragile assumptions. Part 2 looks at how those governance gaps surface during delivery and how they can gradually change the economics of the transformation and the credibility of the business case.