Cheif Of Staff - Roles & Responsibilities

???? What a Consultant Chief of Staff Does (In One Line)

A Consultant CoS is a force‑multiplier for the executive: they design and run the operating system of the business—strategy, planning, cadence, decisions, and cross‑functional execution—without owning a P\&L.

???? Engagement Models

• Fractional / Part‑time CoS: 10–25 hrs/week; sets operating cadence, facilitates exec priorities, fixes cross-functional bottlenecks.
• Interim CoS: 3–6 months; stabilizes leadership rhythms, launches OKRs, stands up PMO and GTM/ops rituals.
• Project CoS: 8–12 weeks; drives a CEO “special project” (e.g., cost takeout, market entry, M\&A integration).
• Embedded Consultant CoS: 6–18 months; acts as full CoS while coaching a future internal CoS.

???? Level-by-Level Roles & Responsibilities

1) Associate / Junior Consultant CoS (IC-level)

Focus: Execution support, analytics, documentation
Core Responsibilities:

• Build Executive Briefs: synthesize data into one-pagers (context, options, recommendations).
• Stand up meeting artifacts: agendas, notes, action trackers, decisions log.
• Run OKR & KPI hygiene: definitions, baselines, weekly scorecards.
• Draft communications: CEO updates, town-halls, board pre-reads.
• Maintain risk/issue registers and follow up on owners & dates.

Typical Deliverables: Action tracker, KPI dashboard, decision log, exec newsletter.

2) Consultant CoS (Mid-level)

Focus: Operating cadence, cross-functional alignment, change management
Core Responsibilities:

• Design the Operating Rhythm: weekly exec meetings, monthly business reviews (MBR), quarterly OKR reviews.
• Prioritization & Trade-offs: facilitate what the exec team starts/pauses/stops; manage the portfolio of initiatives.
• Lead PMO-lite: charters, RAID (Risks, Assumptions, Issues, Dependencies), milestones, RACI.
• Stakeholder Management: align Product–Sales–Finance–Ops on goals and dependencies.
• Decision Architecture: clarify decision rights (Recommend–Agree–Perform–Input–Decide), surface escalations fast.
• Change Control: shepherd proposals, impact analysis, and communications.

Typical Deliverables: Annual plan/OKRs, MBR templates, portfolio tracker, RAID log, change calendars.

3) Senior Consultant CoS

Focus: Strategy translation, org design, executive effectiveness
Core Responsibilities:

• Convert Strategy → Execution: define bets, metrics, and the sequencing of programs.
• Org Design & Capacity: clarify roles, spans & layers, load balancing; build the CoS office playbook.
• Board & Investor Readiness: narratives, metrics, risks, and remediation plans.
• Crisis & Risk Governance: major incident bridges, comms cadence, after-action reviews.
• Leadership Enablement: coach VPs on decision quality, meeting hygiene, and KPI literacy.

Typical Deliverables: Strategy-on-a-page, operating model blueprint, board deck kit, risk governance framework.

4) Principal / Executive Consultant CoS

Focus: Enterprise transformation, CEO advisory, scaling the ops system
Core Responsibilities:

• Architect the Enterprise Operating System: multi-business-unit cadence, cross-region governance.
• Portfolio Value Management: benefits realization (cost, revenue, risk), TCO tracking across programs.
• Culture & Ways of Working: codify behaviors, escalation paths, and leadership rituals.
• Succession & Capability Build: hire/mentor an internal CoS team; handover plan.

Typical Deliverables: Enterprise cadence map, value realization dashboard, leadership playbook, succession plan.

???? End-to-End Scope (What the CoS Office Owns)

1. Strategy & Planning
   • Annual/quarterly planning; OKR definition; prioritization and resourcing.
2. Operating Cadence & Governance
   • Weekly exec; MBR/QBR; decision forums; risk reviews; board prep.
3. Execution & PMO
   • Program charters; milestones; RAID; dependency management; issue clearing.
4. Data & KPIs
   • North-star metrics; balanced scorecards; variance analysis; early-warning indicators.
5. Communications
   • Exec updates; town halls; change comms; stakeholder maps; narrative framing.
6. Change & Incident Bridges
   • Major incident coordination; post-mortems; lessons learned; playbooks.
7. Org & Talent
   • Roles/RACI; spans & layers; capacity planning; leadership effectiveness routines.

???? RACI (Example)

• Strategy/OKRs – D: CEO | R: Senior CoS | A: COO/CFO | C/I: ELT
• MBR/QBR Cadence – R: CoS | A: COO | C: Finance/HR/BU leaders | I: All managers
• Board Prep – R: Senior CoS | A: CEO | C: CFO/Legal | I: ELT
• Change Control (Tier-1) – R: CoS + Change Manager | A: CAB Chair | C: IT/Facilities/HR | I: Impacted orgs
• Major Incident Bridge – R: CoS (facilitation) | A: Incident Owner (IT/Facilities) | C: Security/Comms/Legal | I: ELT

???? KPIs for a Consultant CoS

• Planning & Execution: % OKRs green, schedule variance, benefits realized (₹/%, revenue, cost).
• Operating Rhythm: action closure rate, decision SLAs, meeting effectiveness scores.
• Risk & Incident: time-to-escalation, MTTR on cross-functional issues, recurrence rate.
• Stakeholder Health: NPS from ELT/BU heads, comms engagement, change adoption metrics.

????️ Sample Weekly Cadence (Lite, High-Impact)

• Mon: Exec stand-up (30m) – top 3 priorities, risks, decisions needed.
• Tue: Program syncs – PMO reviews RAID; unblock decisions.
• Wed: KPI pulse – dashboards, variances, countermeasures.
• Thu: Stakeholder communications – update notes, town-hall prep.
• Fri: Debrief & planning – wins, lessons, next week plan; update decision log.

????️ Tooling & Templates (Ready-to-Use)

• Operating Rhythm Kit: agenda templates, decision log, action tracker, OKR sheets.
• Portfolio & PMO: program charter, milestone plan, RAID, dependency map.
• Leadership Comms: CEO weekly note, town-hall deck, change comms plan.
• Governance: MBR/QBR pack, risk register, incident after-action review.

If you want, I can generate these as PPTX + Excel files tailored to your context (IT, Facilities, vendors, co‑working partners), so you can plug in data quickly—handy since you’re working long hours.

✅ When to Hire Which Level

• Associate CoS: You need clean exec artifacts, trackers, and dependable follow‑ups.
• Mid-level CoS: Multiple initiatives compete; decisions stall; you need a crisp operating cadence.
• Senior CoS: Strategy must convert to outcomes; cross‑functional conflicts are slowing the org.
• Principal CoS: Enterprise transformation; board scrutiny; scale across geographies/functions.

????Success Conditions (What You Need to Provide)

• Access: calendars, dashboards, program owners, financials (as allowed).
• Authority: decision rights to convene leaders and drive trade-offs.
• Clarity: non-negotiable outcomes (e.g., cost reduction, launch by date, risk posture).
• Cadence: commit to weekly/MBR/QBR rituals—consistency beats intensity.