Transformation Delivery for Financial Services

A Practitioner's Course

Session Nine

Implementation Summary

A consolidated checklist across governance, sponsorship, regulatory change, people, risk, framework choice, reporting, and handover. A working reference to return to

Disclaimer This course is provided for general information and education only. It is not legal advice. Legislation, rules and regulatory guidance change, sometimes quickly. Readers should confirm the current position and obtain jurisdiction-specific professional advice where needed. The views and experience expressed are Russel Fielding's own and do not represent any employer or client organisation.

Session Nine: Implementation Summary

This checklist draws together the eight sessions that precede it. It covers the questions sponsors, programme directors, and senior leaders need to answer before they can say a significant transformation or regulatory change programme is properly governed, deliverable, and ready to hand over. Use it as a working reference when reviewing a live programme, briefing a board, or scoping new delivery capability.

Who this session is for. This session is for readers who have worked through the preceding eight sessions and want a single working reference to take back into their own organisation.

Use the questions selectively. They are not a scoring model. Their value is in the quality of the discussion they force: who owns the issue, what evidence supports the answer, and what will happen next if the answer is weak.

Governance and sponsorship

• Is there an active executive sponsor with genuine accountability, not just a named sponsor who signed the business case?
• Does the sponsor understand the programme well enough to make informed decisions when it hits difficulty, and are they visible to the team and the wider organisation?
• Is the business case being used as a living reference throughout delivery, not filed after approval?
• Is there a steering committee with the right membership, a genuine decision-making mandate, and a cadence that matches the pace of the work?
• Is accountability for the business case and the benefits clearly assigned to one person with the authority to act on it?
• Are decisions being made at the appropriate level and at the appropriate speed, rather than deferred or escalated by default?

Regulatory change specifics

• Has the regulatory requirement been properly interpreted, with legal, compliance, operations, technology, and risk involved before the programme was designed?
• Is the programme tracking regulatory guidance actively and assessing the impact of new developments on scope?
• Is the deadline realistic given the scope and available resources, and have the consequences of missing it been assessed?
• Is operational readiness being planned and tested, not just technical delivery?
• Where this programme interacts with others in the portfolio, are dependencies and resource conflicts being managed at the portfolio level?

People and change

• Is change management integrated into the programme from the outset, not added as a workstream towards delivery?
• Has a stakeholder map been produced that identifies accountable senior managers, accountable persons, or equivalent named role-holders, alongside the wider affected population?
• Is training designed around what people need to be able to do, with substantive assessment and a documented response to failure?
• Is resistance being read as information and categorised accurately, rather than treated as an obstruction to be managed away?

Delivery, risk, and framework choice

• Is the delivery approach chosen deliberately, based on the shape of the work, rather than defaulting to a single house methodology regardless of context?
• Is the programme plan credible, with realistic estimates, identified dependencies, and appropriate contingency?
• Is the risk register focused on the risks that could genuinely compromise the programme, with active ownership and honest assessment?
• Are risks being escalated to the appropriate level promptly, in an environment where honest escalation is expected and valued?

Reporting and transparency

• Does the sponsor engage with the programme directly, at the working level, rather than relying solely on the status pack?
• Are reports written candidly, including the awkward parts, in a governance culture that treats amber as a working state rather than a personal failure?
• Is the gap between the plan and the actual work being surfaced honestly, rather than left implicit?

Handover and benefits

• Is there a planned overlap period during which operational owners run the new state while the build team remains available?
• Has the reasoning behind significant design decisions been written down, not just the artefacts themselves?
• Does every significant component of the new operating state have a named owner who can be asked today whether it is working?
• Is a monitoring mechanism already running and producing results before the build team disperses?
• Are benefits defined in measurable terms, baselined before the programme began, and tracked after go-live for long enough to show whether the outcome has held?
• Is there a genuinely honest post-implementation review, specific enough for the next programme to act on?

Common failure modes

Across the course, the same failure modes recur under different names. Sponsorship is nominal rather than active. Governance is built to receive reports rather than make decisions. A regulatory obligation is scoped away from the functions that understand its operational effect. Change management arrives after design choices are fixed. The risk register is maintained for audit rather than management. The delivery framework is chosen because it is familiar, not because it fits the work. Status reporting repeats what is easy to measure and omits what predicts success. Handover is treated as an administrative step, rather than the point at which the outcome has to survive.

None of these failure modes is exotic or specific to one organisation. They recur because the pressures that produce them are present in every large organisation: competing priorities, discomfort with honest escalation, and the temptation to declare a project complete and move on. Recognising the pattern is the first step to building the deliberate countermeasures this course has set out against each one.

What good looks like under the current framework

An organisation that delivers transformation and regulatory change well is not necessarily the one with the largest budget or the most sophisticated methodology. It is the one that sponsors its programmes actively, scopes regulatory obligations before design begins, treats change management as part of delivery, manages risk and benefits rather than merely documenting them, chooses its delivery approach deliberately, reports honestly, and treats handover to business as usual as part of the programme.

That standard does not require a single named methodology or organisational structure. It requires sustained attention from senior leaders, a willingness to engage with delivery as it is rather than as it appears in a status report, and the discipline to invest in the unglamorous work that determines whether an outcome lasts: handover, honest risk discussion, and properly scoped regulatory interpretation.

A final note This course has treated governance, sponsorship, regulatory change delivery, change management, programme risk, framework choice, reporting, and handover as separate disciplines. In practice, they reinforce or undermine each other. Active sponsorship makes honest reporting safer. Properly scoped regulatory interpretation makes operational readiness achievable. A deliberately chosen delivery framework makes genuine risk management possible. Taken together, these disciplines separate an organisation that delivers change well from one that simply produces the artefacts of delivery. That is the discipline this course has tried to set out, and the checklist above is the working reference to take back into the organisation.

Further reading and resources

This session draws together the sources cited across the preceding eight sessions. The full published guides behind this course provide the deepest treatment of each area.

Delivering Transformation in Financial Services. Governance, sponsorship, and board-level oversight of large transformation programmes. Available at araitika.com.

Regulatory Change Delivery in Financial Services. Reading the regulation, planning against a fixed deadline, and evidencing compliance during delivery. Available at araitika.com.

Change Management for Regulated Organisations. Stakeholder management, training, resistance, and embedding change in a regulated environment. Available at araitika.com.

Financial Services and Markets Act 2000, sections 66A and 66B. UK senior manager accountability provisions. Available at legislation.gov.uk.

Financial Markets Conduct Act 2013, Subpart 6A. The Conduct of Financial Institutions regime in New Zealand. Available at legislation.govt.nz.

Financial Accountability Regime Act 2023. Australia's individual accountability regime for APRA-regulated banking, insurance, and superannuation entities. Available from the Federal Register of Legislation, APRA, and ASIC.