Service Lead (SL) — role definition
Purpose: Define the Service Lead as the technical anchor for delivery: architecture soundness, estimates, IC quality, and technical sign-off on the SOW ↔ project plan — while the CSO remains accountable for client success and plan narrative.
Mission
- Own technical excellence, defect density, and “integrity of the build” for assigned engagements or service lines.
- Approve §5 (technical approach, effort, risks) of the SOW ↔ project plan before Head of Delivery review — async or in a focused session.
- Unblock ICs: clear technical north star, code review culture, mentorship (including AI-assisted workflows).
- Partner with the CSO so client-visible milestones match engineering reality.
Accountability
- RACI “R” (Responsible) for technical delivery quality and feasibility statements on the plan.
- Not the primary presenter in the Project Review Meeting by default — attends when Head of Delivery or CSO needs a targeted technical read (see technical-approval-guide.md).
- Escalates capacity, stack, or security risks to Head of Delivery per escalation framework.
Source material
- Historical rhythm example: sl-day-in-the-life.md (references to legacy “EP” / standup language should be read in light of meeting catalog).
Last updated: 2026-03-30