Recap. Costs are attributed. Tenants can see what they pay — and they want more for it.
Series In Production · 3
Part of In Production. Browse the series overview for every part.
Outline
- Hook: The first tenant asks for a public roadmap and gets silence
- Context: Mandate said “operate a platform”; reality wants product management
- Fork: Product team (backlog, research, release notes) vs. engineering team (tickets, SLAs, heroics)
- NZ field note: The first tenant council meeting — and why the loudest tenant is rarely the representative one
Sections to Draft
- Minimum viable product ops for a 2–4 FTE platform team
- Tenant council charter (who speaks, who decides, what gets published)
- What breaks when you pick the wrong model
- Steal-this checklist
Next in the Series
Part 4 — “Guardrails Meet the First Real Exception.” Someone senior needs something the guardrails forbid — and governance designed to say no needs a process for “yes, with conditions.”
One Block · build from here
Before the next tenant council, publish one thing tenants can plan against — even if it is only "what we are not building this quarter."