Modernising Super while Protecting Member Services

A member who needs help with their superannuation is unlikely to be thinking about the systems behind the answer. They need the fund to understand the request and deal with it reliably.

That expectation continues during a merger, a platform upgrade or a change in service provider. For the people leading transformation, the challenge is to understand what must keep working while the organisation changes.

A useful place to start is the member journey. Following a request across teams, platforms and providers can reveal dependencies that are easy to miss in a program plan.

Look at the systems around the registry

A registry may be central to an initiative, but member servicing can also depend on digital channels, case management, identity services, document handling and data shared between platforms. Changing one part can affect how the rest of the process works.

Consider a request that arrives digitally, requires supporting information, moves to a specialist team and generates a member communication. Where does the information sit? How does the next team know it is ready? What happens if a system or hand-off fails?

Mapping that journey provides a concrete basis for architecture and delivery decisions. It helps the business identify which dependencies need attention and which parts of the process may need to change together.

Make the transition operationally credible

A target operating model describes where the fund wants to get to. The transition needs to explain how work will happen along the way.

During a merger or platform change, some teams may use new processes while others still depend on existing systems. Data may need to move between environments. Exceptions may require temporary handling.

The plan should make ownership clear for those arrangements. It should also establish how teams will test them and what evidence will be needed before the fund proceeds to the next stage. This makes readiness a business discussion supported by technology evidence.

Use AI against a defined business problem

AI can be assessed within that same operational view. Start with the work that needs improvement and the information required to perform it.

For example, a fund could assess whether AI helps a service team prepare a case summary. The assessment would need to check whether the summary is complete, whether the person can access the underlying information and how errors will be detected before anyone relies on the output.

Define a baseline and measure the result. Does the task take less time? Is information easier to locate? How much checking remains? That gives the fund evidence for deciding whether to proceed, adapt the use case or stop.

Ask for evidence at the decision points

Executives need more than a report that the program is on schedule. They need to understand whether the fund is ready to operate the proposed change.

For a significant decision, the evidence might include a tested end-to-end member journey, confirmed ownership of transition processes, or resolution of a dependency that could interrupt service. The appropriate evidence depends on the initiative.

An independent review can help test the assumptions and give leaders a clearer view of unresolved issues before they commit.

Choose a practical next step

The next step does not always need to be a new program. It may be a focused review of a member journey, a map of critical dependencies or an assessment of one AI use case.

Starting with a defined business problem makes the work easier to scope and the result easier to assess. It also keeps the purpose of transformation visible: improving the fund’s ability to serve members through the change and beyond it.

Phil Yeardley will attend ASFA in Melbourne from 17–19 November 2026. To discuss your fund’s business and technology priorities, contact 9 Yards to arrange a conversation.


Next
Next

Experience, Judgement and the Right Expertise: Why Complex Change Needs More Than Additional Capacity