University of Canterbury
Keeping a university-wide transformation coherent at delivery pace
The Challenge
When a university replaces the systems it runs on, it commits some of the largest capital it will see in a generation, while most of the relevant expertise sits with its vendors. The University of Canterbury, midway through that replacement, needed its own judgement in the room.
The Solution
Independent architecture, held inside the programme as a governance capability. Judgement free of delivery incentives, applied at the pace decisions were made: recommendations tested before they became commitments, the work structured so assurance could keep up, contested decisions settled on evidence.
The Impact
The programme kept its schedule and the university kept its judgement. Decisions stand up to the scrutiny a public institution answers to, a consequential legacy transition was settled on evidence, and the university now carries an architecture capability of its own.
The Challenge
When a university replaces the systems it runs on, it makes one of the largest administrative investments it will see in a generation. The University of Canterbury was midway through such a programme, built on Workday, when a familiar asymmetry became visible. The programme’s scale had grown past what any one reviewer could hold, the specialist knowledge sat largely with vendors, and the university’s own architecture function was newly formed.
The asymmetry matters because of how delivery is structured. A systems integrator is engaged to move quickly, and its recommendations arrive with delivery incentives attached. Assurance functions review what they can see, and on a programme this size, what any one function can see is a fraction. The institution’s interest, coherence across the whole and value for the money, had no dedicated owner.
Universities know this problem from research governance: expertise must be independent of the interests it reviews. The question was how to apply that principle to a transformation, at the pace a transformation moves, without slowing delivery to the speed of committee.
The Solution
The university's answer was to treat independent architecture as a governance capability and place it inside delivery. FromHereOn architects, engaged through a standing partnership and carrying no stake in build or licensing decisions, held a single accountability: whether each decision continued to serve the university's strategy and its money. Independence usually sits outside a programme and reviews it after the fact. Placed inside, at the pace decisions were made, it protected the schedule instead of taxing it.
In practice the capability did three things. Vendor recommendations were tested against intent before they became commitments. The programme's decision surface was structured into coherent, consistent parts, so assurance work, security review included, could proceed at delivery pace and conclude. And contested decisions were settled on evidence: for the most consequential legacy transition, four viable pathways were laid out, two eliminated early, and the remainder argued on where the logic should sit and how to sequence it, until the decision no longer depended on who held the strongest view.
The same period established a capability the university keeps. Its architecture team, newly combined and largely remote, took a structured baseline of its strengths and gaps through EA Pulse, giving its leadership an evidence base for development conversations. The partnership is designed for transfer: the models, decisions and review discipline remain the university's, and each engagement begins from the accumulated context of the last.
“I get a safe pair of hands. Somebody coming in who is autonomous. I don’t want to have to sit there and go, what are they doing the whole time.”
Paul Mattingly
Principal Enterprise Architect and Transformation Lead, University of Canterbury
The Impact
The value holds at three levels of the institution: its governance, its investment, and its people.
Together, we worked to:
Keep independent judgement in the room where decisions were made, so the programme’s choices withstand the scrutiny a public institution answers to.
Hold the schedule without accepting go-live risk, because assurance kept pace with build.
Test vendor recommendations against value for money before commitment, protecting the university’s capital through its largest administrative change.
Settle a legacy transition carrying real organisational weight on evidence, with a sequencing the institution could live with.
Establish an architecture capability the university owns, baselined through EA Pulse and developing, carrying the discipline beyond the programme.
The partnership continues, and its accumulated context makes each engagement start further ahead than the last. What the university keeps is the harder thing to buy: confidence that work handed to a partner is being done in its interest, without supervision.
If your institution is entering its own once-in-a-generation change, the question is where independent judgement will sit while the decisions are made. From here on, the future looks brighter. Get in touch.