Ownership before mobilisation: a practical readiness test
Ownership Before Mobilisation | Part 3 of 3
Previous in the series: Part 2: When governance gaps become delivery and business-case problems
Cato Rockne-Meyer
16 October 2026
Previous in the series: Part 2: When governance gaps become delivery and business-case problems
Cato Rockne-Meyer
16 October 2026
A governance chart can show every role filled and still leave a programme badly under-owned. The real test is whether named owners can exercise ownership in practice.
A useful way to test whether a programme is genuinely ready to mobilise is to look beyond whether key roles have been named.
The more important question is whether the organisation has established effective ownership across the areas that will shape delivery, transition and benefit realisation.
At a minimum, the programme should be able to identify clear ownership for the following.
Process ownership
The Process Owner should be close enough to the end-to-end process or value chain to understand how work is really performed, including dependencies, exceptions and cross-functional impacts. Their role is broader than representing one function. They should be able to protect the integrity and performance of the process across organisational boundaries.
Product ownership
The Product Owner needs a strong understanding of both the current and future business processes so they can shape the product around the intended operating model. This also requires clarity on what the product is. Product boundaries should be defined deliberately rather than inherited from existing organisational structures, systems or supplier delivery models.
System or platform ownership
The System or Platform Owner is accountable for the ongoing operation of the technology after the programme has delivered it. That includes maintenance, support, service performance, lifecycle management, operational resilience and the ability to evolve the platform over time. In some organisations, system and platform ownership may sit with the same person or function.
Data ownership
Data ownership is often more complex because the lifecycle of important data usually crosses several business functions. One practical approach is to appoint a sufficiently senior Data Custodian who represents the individual owners of different data sets. The custodian needs enough authority to resolve conflicts, establish common standards and hold individual owners accountable for their data responsibilities. Without that authority, data governance can become a forum for discussion rather than a mechanism for decision.
Benefit ownership
The Benefit Owner should sit where the new capability will be used to create ongoing value. The programme can enable the capability, but the enduring business must change behaviour, processes and performance to realise the benefit. Benefit ownership should therefore survive beyond programme closure.
Decision ownership
Major programme decisions will usually sit with the Executive Sponsor or the relevant governance board. The more important question is how decision rights are delegated below that level. Without explicit delegation, too many decisions escalate upwards, slowing delivery and weakening accountability lower down.
Risk ownership
Risk ownership should reflect the nature and potential impact of the risk. The named owner should have sufficient influence over the agreed mitigation and a clear escalation path where that authority is insufficient. At programme level, overall risk ultimately remains with the sponsor and governing board.
Accountability for automation and AI-supported decisions
Where business decisions are automated or supported by AI, accountability should remain with the owner of the underlying business process. Technology may execute or influence a decision, but it does not remove business accountability for the outcome. This becomes increasingly important as organisations introduce more autonomous capabilities into operational processes.
The more important question is whether the organisation has established effective ownership across the areas that will shape delivery, transition and benefit realisation.
At a minimum, the programme should be able to identify clear ownership for the following.
Process ownership
The Process Owner should be close enough to the end-to-end process or value chain to understand how work is really performed, including dependencies, exceptions and cross-functional impacts. Their role is broader than representing one function. They should be able to protect the integrity and performance of the process across organisational boundaries.
Product ownership
The Product Owner needs a strong understanding of both the current and future business processes so they can shape the product around the intended operating model. This also requires clarity on what the product is. Product boundaries should be defined deliberately rather than inherited from existing organisational structures, systems or supplier delivery models.
System or platform ownership
The System or Platform Owner is accountable for the ongoing operation of the technology after the programme has delivered it. That includes maintenance, support, service performance, lifecycle management, operational resilience and the ability to evolve the platform over time. In some organisations, system and platform ownership may sit with the same person or function.
Data ownership
Data ownership is often more complex because the lifecycle of important data usually crosses several business functions. One practical approach is to appoint a sufficiently senior Data Custodian who represents the individual owners of different data sets. The custodian needs enough authority to resolve conflicts, establish common standards and hold individual owners accountable for their data responsibilities. Without that authority, data governance can become a forum for discussion rather than a mechanism for decision.
Benefit ownership
The Benefit Owner should sit where the new capability will be used to create ongoing value. The programme can enable the capability, but the enduring business must change behaviour, processes and performance to realise the benefit. Benefit ownership should therefore survive beyond programme closure.
Decision ownership
Major programme decisions will usually sit with the Executive Sponsor or the relevant governance board. The more important question is how decision rights are delegated below that level. Without explicit delegation, too many decisions escalate upwards, slowing delivery and weakening accountability lower down.
Risk ownership
Risk ownership should reflect the nature and potential impact of the risk. The named owner should have sufficient influence over the agreed mitigation and a clear escalation path where that authority is insufficient. At programme level, overall risk ultimately remains with the sponsor and governing board.
Accountability for automation and AI-supported decisions
Where business decisions are automated or supported by AI, accountability should remain with the owner of the underlying business process. Technology may execute or influence a decision, but it does not remove business accountability for the outcome. This becomes increasingly important as organisations introduce more autonomous capabilities into operational processes.
The real readiness test
Assigning these roles is only the first step. A named owner may still be ineffective if they lack the authority to decide, the knowledge to exercise judgement, the capacity to perform the role, or the organisational standing to have their decisions accepted.
Is this person merely named as the owner, or can they exercise ownership?
Nominal ownership versus effective ownership
Test ownership effectiveness before mobilisation. At that point, the organisation is committing to scope, delivery pace, decision-making, client-side resourcing and the operating model required to support the transformation. If ownership is weak at mobilisation, those weaknesses are likely to appear later as delays, escalations, bottlenecks and unclear accountability.
A role can be clearly assigned on a governance chart and still fail in practice. Four dimensions provide a useful pre-mobilisation test.
Authority
Knowledge
Capacity
Organisational standing
Assess the arrangement, not just the individual
Consider these four dimensions together. A highly knowledgeable owner with insufficient capacity remains a weak arrangement. A senior executive with considerable authority but limited understanding of the underlying process may also struggle to make good decisions.
A simple maturity scale can help:
A low Capacity score may mean the right person has been appointed but has not been released sufficiently from BAU. A low Authority score may indicate poor delegation. A low Organisational Standing score may point to unresolved governance across business boundaries.
A role can be clearly assigned on a governance chart and still fail in practice. Four dimensions provide a useful pre-mobilisation test.
Authority
- Does the owner have the decision rights required by the role?
- Can they resolve conflicts, approve changes, enforce standards and commit or influence resources without repeatedly escalating routine matters?
Knowledge
- Does the owner understand the subject well enough to exercise judgement?
Capacity
- Has the organisation created enough space for the person to perform the role?
Organisational standing
- Will other stakeholders accept the owner’s authority?
Assess the arrangement, not just the individual
Consider these four dimensions together. A highly knowledgeable owner with insufficient capacity remains a weak arrangement. A senior executive with considerable authority but limited understanding of the underlying process may also struggle to make good decisions.
A simple maturity scale can help:
- Nominal: an owner is named, but ownership is largely symbolic.
- Emerging: some ownership is exercised, but important conditions remain weak.
- Functional: routine ownership works, but may break down under conflict, pressure or cross-functional complexity.
- Effective: the owner can make and sustain decisions across the relevant scope.
- Embedded: ownership is recognised, supported and resilient as part of the organisation’s normal way of operating.
A low Capacity score may mean the right person has been appointed but has not been released sufficiently from BAU. A low Authority score may indicate poor delegation. A low Organisational Standing score may point to unresolved governance across business boundaries.
Do our named owners have the authority, knowledge, capacity and organisational standing to do the job the programme is about to depend on them to perform?
If the answer is uncertain, that is a mobilisation issue to resolve before it becomes a delivery problem.
Test your ownership readiness
Use the Ownership Effectiveness Diagnostic to test whether your critical transformation owners have the authority, knowledge, capacity and organisational standing to exercise ownership in practice.
>> Run the Ownership Effectiveness Diagnostic
Test your ownership readiness
Use the Ownership Effectiveness Diagnostic to test whether your critical transformation owners have the authority, knowledge, capacity and organisational standing to exercise ownership in practice.
>> Run the Ownership Effectiveness Diagnostic
Sort out ownership before you leave the harbour
Once a transformation programme is under way, ownership becomes much harder to sort out. By then, delivery plans are active, suppliers are mobilised, decisions are being made, budgets are being consumed and dependencies are forming around the people already in place.
My experience at sea has taught me that the roles which keep a journey functioning are not always the ones that receive the most attention before departure. The cook is a good example.
Once a ship is underway, feeding and watering the crew becomes a critical operational responsibility. Mealtimes establish a routine people depend on. They provide a break from demanding work, an opportunity to socialise and share information, and help sustain morale over the course of the journey. It is easy to overlook the importance of that role while still in harbour. It becomes much harder to ignore once you are at sea.
Transformation programmes have similar dependencies. Some critical roles are obvious from the outset. Others become apparent only when delivery pressure exposes what the programme needs to function.
My experience at sea has taught me that the roles which keep a journey functioning are not always the ones that receive the most attention before departure. The cook is a good example.
Once a ship is underway, feeding and watering the crew becomes a critical operational responsibility. Mealtimes establish a routine people depend on. They provide a break from demanding work, an opportunity to socialise and share information, and help sustain morale over the course of the journey. It is easy to overlook the importance of that role while still in harbour. It becomes much harder to ignore once you are at sea.
Transformation programmes have similar dependencies. Some critical roles are obvious from the outset. Others become apparent only when delivery pressure exposes what the programme needs to function.
Why would you not want to identify and put those roles in place before leaving the harbour?
Pre-mobilisation is the point at which ownership should be properly tested. That means more than naming people on an organisation chart. The programme should know who owns the key processes, products, systems, data, benefits, decisions and risks. It should also know whether those owners have the authority, knowledge, capacity and organisational standing to exercise the role effectively.
Some gaps will remain. Target operating models evolve, suppliers introduce new demands, business cases change and new competencies may need to be built. The purpose of pre-mobilisation governance is to ensure the programme has the people, ownership, capability and decision-making strength needed to deal with uncertainty once the journey begins.
No two transformations are the same, but experienced leaders recognise common patterns, characteristics and behaviours.
Once the programme has set sail, every unresolved ownership question becomes harder to resolve and more expensive to fix.
Some gaps will remain. Target operating models evolve, suppliers introduce new demands, business cases change and new competencies may need to be built. The purpose of pre-mobilisation governance is to ensure the programme has the people, ownership, capability and decision-making strength needed to deal with uncertainty once the journey begins.
No two transformations are the same, but experienced leaders recognise common patterns, characteristics and behaviours.
Once the programme has set sail, every unresolved ownership question becomes harder to resolve and more expensive to fix.