The Landing Zone That Survived

A chronological follow-up to the failure modes series: Fakey, a fictional Wellington fintech, from mandate to mature platform.

Pilot
SR
Steve Rackham
3 min read Concepts

The failure modes series 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, CPS 234, Privacy Act 2020, Azure NZ North, 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

  1. The Mandate — sponsors, funding, and how to scope a platform initiative
  2. Discovery Week — interview templates and NZ regulatory mapping
  3. The Design Decisions Document — subscription strategy, IaC choice, and the security questionnaire that proved documentation was revenue
  4. Increment 1 — minimum viable guardrails and what was deliberately deferred
  5. Onboarding the Pilot Team — first production workload, friction, fixes
  6. The Operating Model — who watches the watchers when alerts land
  7. The Cost Surprise — FinOps when the CFO asks hard questions
  8. The 2am Page — operating model under incident pressure
  9. The Second Team — platform versus bespoke when the important customer arrives
  10. The Petone Exit — decommissioning as a deliverable
  11. The Platform Becomes Invisible — year two opens; the annual review and series finale (Part 11 folded into the opening recap)

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.

One Block

Before part 1, name your fictional (or real) sponsor in one sentence: who cares if this platform ships, and what do they lose if it does not?