In Production · Appendix

The Operating Years Checklist

A catalogue-style appendix for years two to four of a platform that survived: the review lens distilled for reuse. Written for NZ platform teams.

SR
Steve Rackham
2 min read Guides

Appendix. Nine narrative parts told the operating-years story at fakey.xyz. This post distils the review lens — use it in steering, annual planning, or the quarter before a restructure.



Checklist Sections to Draft

Wave two and programme pressure

  • Wave-two workloads mapped against design assumptions
  • BUILD / ROUTE / DECLINE applied under programme deadlines

FinOps and politics

  • Showback before mandated chargeback
  • Allocation rules tested with a friendly business unit first
  • Narrative for every line item finance will challenge

Product vs. engineering team

  • Public roadmap or explicit “not this quarter”
  • Tenant council charter with representative voice, not loudest voice

Exceptions and guardrails

  • Waiver count tracked monthly; stale exceptions escalated
  • Senior exceptions documented with expiry and risk acceptor

Political visibility

  • Leadership slide: three metrics, one risk, one tenant quote
  • Quarterly narrative before anyone asks “what does the platform do?”

Provider drift

  • Retirement register reviewed quarterly
  • Refresh waves communicated before tenants discover them

Knowledge and handover

  • “Ask Dave” paths mapped and ticketed
  • Exception register + decision document + runbooks aligned

Build vs. adopt

  • Native service evaluation documented per capability
  • Platform decommission plan when you retire your own code

Three-year review

  • Metrics agreed before the meeting
  • Handoff artefacts named: what the next team can run without archaeology

One Block

Pick one section above and score your platform honestly this week — one tick is enough to start.