CSO — expectations by cadence
Purpose: Operational checklist aligned to role-definition.md and project-ownership-guide.md.
Daily
- Client pulse: Meaningful touchpoint (Slack/email) — not a generic status dump.
- Delivery visibility: Linear board reviewed for blockers; ensure client-visible work maps to projects / milestones where applicable.
- Internal signal: Update internal health / risk notes (however the team tracks sentiment) when material.
- Async first: Prefer written updates in Linear over scheduling meetings for status.
Weekly
- Client value moment: Formal or semi-formal weekly touchpoint with a tangible artifact when possible (deck, demo snippet, doc).
- Internal: Participate in weekly leadership sync (replaces broad daily CSO+SL standup for portfolio status).
- SL alignment: Async or short sync on “what we ship next” vs “what we told the client” — no need for SL in every client call.
- Kick-off / EOW updates: Use playbook SOPs via cso-skills-catalog.md.
Monthly
- Health and scope: Review trajectory vs SOW; flag drift early.
- Data platform / docs: If the account uses a Data Platform doc, keep it current per skills/playbook.
- Expansion signals: Note upsell/renewal threads for leadership (vault or HubSpot per process).
Quarterly
- Project plan refresh: Re-run Project Review Meeting with Head of Delivery (or async approval if lightweight).
- Executive narrative: Sponsor-level summary of outcomes, risks, and next quarter’s bets.
- Self / team: Review KPIs (e.g., escalation proxy, comms consistency, milestone hit rate).
One-time / per engagement
- Post-SOW: Complete SOW ↔ project plan doc and schedule Project Review Meeting before scaling execution.
- Major scope change: Refresh plan and re-obtain Head of Delivery approval before committing dates to the client.
Last updated: 2026-03-23