Public-sector embedded delivery playbook
How to bring FDE discipline into public services without bulldozing governance or pretending policy constraints are optional.
Outcome: Deliver software improvements while respecting policy, auditability, equity, and frontline reality.
Operating sequence
- Map policy intent, service promises, frontline constraints, and citizen impact separately.
- Make audit and accessibility non-negotiable product requirements, not late-stage paperwork.
- Pilot in a bounded service line where operational staff can shape the tool safely.
- Publish what was learned: what improved, what failed, and what should become shared capability.
Artifacts to leave behind
- service blueprint
- policy-to-system trace
- accessibility checklist
- pilot evaluation
Kev’s blunt rule
If the engagement does not produce a visible workflow change, reusable product learning, or a clear kill decision, it was just expensive tourism with a laptop.