One Project, Two Countries: Deploying Across ANZ

ANZ IT deployment programs get structured one of two ways. Either Australia and New Zealand run as one program with local execution, or NZ becomes a satellite project, different provider, different report, different standard, that lands on an executive's desk as a surprise every quarter. Networks that trade on both sides of the Tasman keep learning the same lesson: the estate is one estate, and the program should match.

What "one program" means structurally

One wave plan. NZ sites slot into the master sequence on the same logic as everywhere else, logistics, trading priority, readiness, with their own freight and customs lead times built in. Auckland is a wave, not an appendix.

One playbook, localised. The install method, evidence standards and sign-off criteria are identical in Newmarket and Newtown. What localises is the compliance layer: NZ trade measurement certification where lanes weigh, NZ electrical and safety requirements, local holiday calendars. The NZ-specific details.

One dashboard. Executives see the whole ANZ estate in one view, same statuses, same evidence, same exception clocks. The moment NZ reports differently, it gets managed differently, and the drift begins.

Local execution on both sides. One program emphatically does not mean Australian crews on planes. It means NZ field teams, NZ freight and NZ staging arrangements running the shared method, with the Tasman crossed by data, not by engineers.

The failure mode: the stapled program

The alternative structure, an Australian program plus a subcontracted NZ mini-program, fails in slow motion. Two providers means a seam, and the seam collects everything: incompatible asset data, mismatched sign-off standards, disputes about whose scope the shared systems sit in. The NZ estate ends the program with a register that doesn't reconcile and a standard that doesn't quite match, and the next refresh pays the integration debt with interest.

Why it matters commercially

Trans-Tasman networks, retailers, banks, logistics operators, run shared platforms: one POS estate, one banking stack, one WMS. A capability shipped to Australian sites but delayed or divergent in NZ splits the platform, and the business feels it in every cross-country process. The deployment structure either protects platform unity or quietly breaks it.

Luxottica's line about Australia, "we simply would not be able to operate in a country the size and scale of Australia without IMI", scales across the Tasman for the same reason: scale and distance yield to structure, and one delivery structure is simpler than two.

The one-page test

Ask for the program's executive report. If ANZ fits on one page, one plan, one completion curve, one exception list, the structure is right. If New Zealand arrives as a separate attachment, the seam already exists, and it's collecting.

Two countries, one estate? Speak to an expert.