Head of Delivery — how standards are set and communicated
Purpose: Repeatable way to introduce or change delivery standards so the team can adopt them (and so enforcement is fair).
Principles
- One source of truth — Standards live in delivery, especially 04-standards-and-sops. Playbook remains canonical for templates/SOPs; link out rather than duplicating.
- Observable behaviors — Each standard should translate to something a peer can verify (doc exists, Linear state, meeting happened).
- Small batches — Prefer a few high-leverage standards over a long list that nobody internalizes.
- Announce + deadline — Communicate what changes, why, and by when; use leadership sync for Q&A.
Steps to add or change a standard
- Draft in
knowledge/delivery/04-standards-and-sops/(or update an existing file). - Cross-link from INDEX.md and the relevant role doc (CSO / SL / IC).
- Announce in weekly leadership sync with examples of “good” vs “miss.”
- Set enforcement — Who checks (Head of Delivery, delegate, peer review in Project Review Meeting).
- Review quarterly — Keep, tighten, or retire based on data and feedback.
Related
- escalation-framework.md — when standards repeatedly aren’t met
- project-review-meeting — gate for plan quality
Last updated: 2026-03-23