Head of Delivery — expectations by cadence
Purpose: Practical rhythm for the Head of Delivery role. Adjust durations to portfolio size.
Weekly
- Leadership sync with CSOs (and SLs when needed) on standards, risks, and blockers — see weekly-leadership-sync.md.
- Spot-check high-risk accounts (renewals, margin pressure, repeated misses on Linear/comms).
- Review escalation queue or patterns (if tracked in Linear, Slack, or ops forum).
- Ensure Project Review Meetings are scheduled for new SOWs and quarterly refreshes as needed.
Monthly
- Review delivery health signals: internal meeting load vs client work, Linear hygiene trends, client health inputs (where available).
- Tune standards docs if the team repeatedly misses the same bar (one clear update beats many ad-hoc pings).
- Align with ops/finance on margin and utilization narratives for delivery.
Quarterly
- Portfolio review: which clients had plan refreshes, which need one, where scope drifted.
- Revisit KPIs (e.g., escalation count, plan approval SLA, hygiene metrics) and communicate any change.
- Optional: sample Project Review Meeting outputs for quality (defensibility, linkage to SOW).
Ad hoc
- Approve or send back project plans after CSO presentation at Project Review Meeting.
- Arbitrate when CSO and SL disagree on feasibility vs client commitment (after both have documented positions).
- Hiring / role clarity: input on CSO vs SL expectations when staffing changes.
Last updated: 2026-03-23