The Landing Zone That Survived

Part 1 of “The Landing Zone That Survived”, the series overview. The story proper starts in Part 2: The Mandate.

The failure modes reference was diagnostic. It named what goes wrong before the first subscription lands.

This series inverts the framing. Instead of “here is what goes wrong,” it asks what right looks like, one sprint at a time, told chronologically through Fakey, a fictional but realistic Wellington fintech of about four hundred people, standing up an Azure landing zone under NZ obligations.

Why This Follows

Same audience, deeper engagement. Architects and delivery leads who read the failure series will recognise their own world. Narrative posts travel further in meetups and corridors than listicle diagnostics.

It fills the gap the first series left. Failure modes said what not to do. This series shows artefacts, meetings, decisions, and trade-offs, the “how it actually happened” content engineers crave.

It recycles the research. NZISM, Privacy Act 2020, Azure NZ North, CPS 234 where MegaCorp’s Australian regulated counterparties require it, and small-team realities get a second life in concrete context.

It stays honest. Fakey will ship imperfect increments, get paged at 2am, and discover that decommissioning is a deliverable nobody puts in roadmaps. Survival is the point, not perfection.

What You Will Get Across Twelve Parts

Twelve parts, from overview to finale. The arc runs from mandate to maturity: build, operate, defend, expand, and finally make the platform invisible.

1. The Landing Zone That Survived: this overview, framing, cast, and the map of the year
2. The Mandate: sponsors, funding, and how to scope a platform initiative
3. Discovery Week: interview templates and NZ regulatory mapping
4. The Design Decisions Document: subscription strategy, IaC choice, and the security questionnaire that made the design document earn its keep
5. Increment One: the first six weeks, minimum viable guardrails, and what was deliberately deferred
6. Onboarding the Pilot Team: first production workload, friction, fixes
7. The Operating Model: who watches the watchers when alerts land
8. The Cost Surprise: FinOps when the CFO asks hard questions
9. The 2am Page: operating model under incident pressure
10. The Second Team: platform versus bespoke when the important customer arrives
11. The Petone Exit: decommissioning as a deliverable
12. The Platform Becomes Invisible: year two opens, the annual review folded into the finale, and the series close

One Note on Fiction

Fakey is composite. No client is named. Details are chosen to feel true for NZ platform teams of two to four people, not to document any real engagement.