Practical writing for enterprise delivery teams
Notes on delivery discipline, platform engineering, security practices and data governance. Written for teams building and operating systems in complex environments.
Recent insights
General guidance that does not disclose client details.
Why SLOs fail and what to do instead
Most SLO implementations stall because they measure the wrong things or lack operational response. A practical alternative.
Read →Threat modelling for delivery teams, not auditors
How to run threat modelling that improves architecture decisions rather than producing shelf-ware documents.
Read →Landing zones that teams actually use
The difference between a reference architecture and a platform teams adopt. Guardrails, defaults and developer experience.
Read →Architecture decision records in practice
Why lightweight written decisions produce better outcomes than meetings, and how to make them stick.
Read →Data quality is an operations problem
Treating data quality as a one-time fix fails. Treating it as an operational discipline works. Here's the difference.
Read →GenAI in enterprise: evaluation before deployment
Why evaluation harnesses, not prompt engineering, determine whether AI features survive contact with production.
Read →Making governance efficient, not bureaucratic
How to design approval workflows and evidence capture that support speed rather than blocking delivery.
Read →Secrets management beyond the vault
Secrets handling is more than a tool choice. Rotation, scope, audit trails and operational procedures matter more.
Read →Runbooks that work under pressure
Why most runbooks fail during incidents and how to write operational procedures that actually help on-call teams.
Read →Cost governance without blocking teams
Practical guardrails for cloud spend that create visibility and accountability without centralised bottlenecks.
Read →KPI semantics: why definitions drift
Reporting consistency breaks down when metric ownership is unclear. A practical approach to semantic governance.
Read →Handover as a first-class deliverable
Structured handover reduces operational risk and makes ownership transitions predictable rather than chaotic.
Read →Want to discuss a topic?
Share your challenge and we'll connect you with the right delivery expert.