Service Lead (SL) — expectations by cadence
Purpose: Operational checklist aligned to role-definition.md. Mirrors the structure of CSO expectations-by-cadence and Head of Delivery expectations-by-cadence so roles are comparable.
Daily
- Execution truth: Linear reflects real state for accounts you support; blockers and technical risk are visible, not implied.
- Unblock ICs: Clear technical north star; respond to escalations so ICs are not spinning without a decision path.
- Escalate early: Surface capacity, stack, security, or feasibility risks to Head of Delivery per escalation framework before they become client surprises.
Weekly
- CSO–SL alignment: Async or short sync per account on “what we ship next” vs “what we told the client” (see meeting catalog: CSO–SL alignment).
- Leadership sync: Participate when invited — bring technical debt spikes, dependency blockers, and quality themes (not ticket-by-ticket status).
- Linear truth: With CSO, ensure the board stays trustworthy for technical and operational reality (linear hygiene standards).
- Cross-service friction: If work spans services, escalate through the CSO for the affected account rather than negotiating only SL-to-SL in the blind.
Monthly
- Operating / allocations: Confirm sub-service and project allocations match reality (who is on which client or internal project, hours assumptions). Service Leads own keeping this layer accurate as the resourcing system of record matures.
- Patterns: Note repeated quality misses, estimate drift, or stack risks across accounts in your line — inputs for service line review and Head of Delivery.
Quarterly
- KPIs and narrative: Review agreed SL metrics with leadership (e.g. quality / stability proxies) and capture a short service-line health narrative: hiring needs, playbook gaps, cross-client technical themes.
- Plan gates: Be available for Project Review Meeting and technical sign-off on major plan changes for accounts you support.
One-time / per engagement
- Technical sign-off: Approve §5 (technical approach, effort, risks) of the SOW ↔ project plan before Head of Delivery review when you are the SL for that engagement.
- Material change: When technical assumptions shift materially, ensure the engagement re-gates through plan review rather than quiet drift (project lifecycle).
Relationship to standards
The consolidated delivery standards apply to everyone. The SL is especially accountable for the technical and execution side of that floor (quality, honesty of state, feasibility).
Last updated: 2026-03-30