.png)
A Financial Services Organisation Gains Clarity and Confidence to Scale a Critical Customer Platform
A New Zealand-based financial services organisation was entering a critical growth phase after being appointed as a default KiwiSaver provider.
​
This introduced a step-change in customer volume, regulatory obligations, and operational complexity. At the same time, the organisation’s technology environment had evolved organically, with limited integration, heavy reliance on manual processes, and no formal architecture capability.
​
Leadership needed confidence that their systems and processes could support this next phase of growth—without introducing unacceptable risk.
Date: 2021 | Client: Financial Services Organisation | Sector: Financial Services
The Challenge.
​
This was not simply a technology uplift. The organisation needed to scale quickly, while continuing to deliver in-flight initiatives and meet strict compliance requirements.
​
Key challenges included:
​
-
A fragmented technology landscape with limited visibility of systems, dependencies, and risks
-
Heavy reliance on manual processes and file-based integrations, creating scalability and data integrity concerns
-
Legacy and non-standard technologies, introducing key person risk and limiting flexibility
-
No formal architecture governance or decision-making framework, leading to inconsistent and reactive decisions
-
The need to support a critical, time-sensitive initiative, without slowing delivery
Without intervention, the organisation risked service disruption, compliance exposure, and an inability to scale effectively
What we did (together).
​
Cyma partnered closely with the organisation to bring clarity, structure, and practical direction, without disrupting ongoing delivery.
​
Our work included:
​
-
Conducting targeted stakeholder interviews to understand how systems, processes, and data worked in practice
-
Developing a Business Capability Model to define what the organisation needs to deliver
-
Creating a centralised Application Catalogue and Application Landscape, bringing fragmented knowledge into a single, coherent view
-
Identifying and mapping technology risks across systems, integrations, and processes, linked to business impact
-
Providing architectural guidance alongside the KiwiSaver default rollout, ensuring the environment could support increased scale
-
Introducing the foundations of an architecture practice, including:
-
Practical architecture principles
-
Lightweight governance and decision-making approaches
-
Delivering clear, actionable recommendations focused on:
-
Reducing manual processing
-
Improving integration approaches
-
Managing legacy and scalability risks
Most importantly, we shifted the conversation from: “What systems do we need next?” to “How well does our current environment support the business, and where are the real risks?”
Created clarity where complexity had built up
Brought a fragmented, manual-heavy technology environment into a single, trusted view the business could understand and act on.
​
​
Designed for safe growth, not theory
Focused on enabling KiwiSaver scale‑up while managing real regulatory, operational, and delivery risks.​
​
​
Worked shoulder‑to‑shoulder with the client team
Embedded alongside leaders and delivery teams to listen, guide decisions, and support a critical initiative without slowing progress.​
​
Delivered high-impact outcomes pragmatically
Introduced just enough structure, governance, and architectural thinking to reduce risk and build confidence, on time and without unnecessary cost.
The Result.
​
The organisation gained a clear, structured understanding of its technology environment and the confidence to scale safely.
​
The work delivered:
​
-
A consolidated, reliable view of the technology landscape, reducing reliance on tribal knowledge
-
Clear identification and prioritisation of key technology risks, linked to business impact
-
A foundation for more informed, consistent decision-making, guided by agreed principles
-
A practical pathway to reduce operational risk, particularly in manual and integration-heavy processes
-
Improved alignment between business and technology through a shared capability-based view
-
A stronger foundation to support increased customer volumes and regulatory requirements
-
Establishment of the foundations for an architecture capability, not just one-off artefacts
Why it worked.
​
Cyma approached the engagement with pragmatism, clarity, and a strong understanding of delivery realities.
​
What made the work successful:
​
-
Working as an embedded partner, not an external reviewer
-
Balancing immediate delivery pressures with longer-term architectural thinking
-
Simplifying complex environments into clear, usable artefacts
-
Introducing “just enough” structure and governance without slowing progress
-
Focusing on actionable next steps, not theoretical perfection
The result was a clear, defensible understanding of the current environment and a practical path forward that enabled confident growth.