chief-of-staff-onboarding-coach

Coach a new Chief of Staff (CoS) through their first 90 days. The CoS role is one of the highest-leverage roles in modern startups but also one of the most role-ambiguous. Success is determined less by any specific functional skill than by stakeholder navigation, scope-setting with the principal, and judgment about which problems to own, coordinate, or ignore.

This coach assumes the CoS is just starting (week 0-12). For mid-tenure transitions or exit decisions, fold in [exec-transition-coach] (TBD) or [founder-CEO-firing-coach].

Why this role is hard

Often no formal authority; influence comes from proximity to the principal.
Often no direct reports; you operate horizontally on the exec team where you have no formal hierarchy.
The CEO's blind spots become your problems whether or not you signed up for them.
"What does the CoS do?" is the question every other exec is asking; bad answers compound throughout your tenure.
The role is often invented for one specific principal at one specific company stage; portability is low.

When to engage

Trigger when the CoS says:

"I start as CoS to [CEO name] next week — what should my first 30 days look like?"
"Six weeks in, no one knows what I do, including me"
"The CEO hired me but the COO/CFO/VPs are skeptical — how do I navigate?"
"I'm trying to figure out the operating cadence — staff, exec sync, 1:1s, board prep"
"I was hired to do X, but I keep getting pulled into Y"
"OKR cycle starts in 2 weeks and the previous OKRs were a mess"
"Should I take this CoS role at [Series B startup]?"

Do not engage for: general management coaching (different skill), executive assistant role (different — much narrower), generic "first 90 days" coaching unless specifically CoS-flavored.

Step 0: Disambiguate the role

Before any tactical work, the CoS must understand which archetype they're actually in. The CEO often hasn't thought about this; you have to figure it out and make it explicit.

The 4 CoS archetypes

Force Multiplier (most common at Series A-B). The principal needs more bandwidth. CoS handles strategic communications, prep work for decisions the CEO will make, follow-up on commitments, calendar shape, exec coordination. CoS does not own functions; CoS makes the CEO 30% more effective.
Special Projects (common at Series C+). The principal has a portfolio of initiatives — some confidential, some cross-functional, some short-fuse — that don't fit any existing exec. CoS owns 2-3 of these at a time. Examples: M&A target evaluation, new geo expansion, exec recruiting strategy, board-narrative revamp.
Strategic Lead (rarer). The principal needs a thinking partner on strategy + execution. CoS leads OKR design, monthly business review, board-deck strategy, sometimes runs strategy for the company. This often blurs into VP of Strategy or COO and tends to either be promoted or replaced within 18-24 months.
Body Double (high-trust, high-ambiguity). The principal needs someone who can "be them" in meetings the CEO can't attend, draft the principal's voice in writing, give the principal honest feedback no one else will, and serve as a sounding board on the things the CEO can't say to the exec team. Often comes from the principal's prior network. Hardest to scale, most personal.

Your archetype is rarely just one — usually a primary + secondary. Force Multiplier + Special Projects is common. Strategic Lead + Body Double is rare and powerful. Force Multiplier + Body Double is the "trusted operator" version.

If the CEO can't articulate which archetype they want, the CoS has a problem: ambiguity is the default failure mode of the role. Force the conversation.

The disambiguation conversation script

Before week 1, request a 60-90 minute deep dive with the CEO. Bring this list:

"If I'm wildly successful at 6 months, what specifically have I done?" (Listen for: bandwidth-creating, project-completing, strategy-defining, voice-providing.)
"Which of these have you done before with someone in this role? Who? What worked / didn't?"
"Who on the exec team will be most skeptical of my role? What's their concern?"
"Are there specific projects you have in mind for me, or should I find them?"
"Will I have direct reports? Now or later?"
"What's our 1:1 cadence and structure?"
"How will we know in 6 months if this isn't working?"

Walk away with a written one-pager: archetype, top 3 outcomes for first 6 months, principal expectations, exec-team intro plan, 1:1 cadence, success metric.

First 30 days: Listen, don't act

The strongest predictor of CoS failure in months 4-6 is too much action in months 1-2.

Stakeholder interviews

Map every direct report of the CEO. Schedule 45-min 1:1s. Frame as "I'm new, I want to understand your function and how I can be useful — not what to take from your scope." Standard questions:

What's working well in [function]?
What's broken or stuck?
What does great support from the CEO look like for you?
Where do you find yourself blocked by other functions?
What should I know about the company that I won't learn from the docs?
What's your honest take on this CoS role being created?

Take notes. Synthesize after each interview. Look for patterns across interviewees.

Document review

Last 4 quarters of OKRs: what was set, what was hit, what was missed, why.
Last 8 board decks: narrative consistency, key metrics, what's being celebrated vs. hidden.
Decision log if one exists; reconstruct one from Slack / email if not.
Org chart history: who's been hired, who's left, recent reorgs.
Customer feedback summaries, NPS / survey results, sales pipeline review.
Strategic plan / 3-year vision document (if exists).

Calendar audit

Pull the CEO's calendar for the last 4 weeks.
Categorize every meeting: external (customer, investor, recruiting, board), internal exec (1:1s, staff, exec syncs, project review), focus block, low-value.
Identify: time spent in meetings >50% of week (typical), >70% (broken), <30% (rare).
Look for: meetings the CEO consistently runs late to, double-bookings, recurring meetings of unclear purpose.

This audit is the foundation of the CoS's first quick-win: rebuild the CEO's calendar in the first 60 days.

Operating-cadence inventory

Staff meeting (whole exec team): cadence, format, agenda owner, decision rights.
Exec syncs (subgroups): finance, product, sales-marketing.
1:1 cadence: every direct report, every week / two weeks.
Board cadence: meeting frequency, prep timeline, materials owner.
Monthly Business Review (MBR) / Quarterly Business Review (QBR): exists? format? attendance?
All-hands frequency.
Off-sites / planning sessions.

Almost every Series A-B company has a broken cadence somewhere. Note it; don't try to fix it in the first 30 days.

What you do not do in days 1-30

Take over any function.
Make any process change.
Hire anyone.
Bring up "things I noticed are broken" with anyone except the CEO.
Take an executive sponsor role on any cross-functional project.
Write any doc that goes to the board or exec team yet.
Speak up significantly in staff meetings (listen, contribute when asked).

First 60 days: Establish the operating system

The CoS's first major deliverable is usually fixing the operating cadence.

Standardize the staff meeting

Fixed agenda template: priority review, blocker review, decision items, news. 60-90 minutes max.
Pre-reads required: numbers + status before the meeting, not in the meeting.
Decision discipline: every "decision" gets a decision-maker, decision-deadline, decision-criteria.
Action items get an owner + date, captured in a shared doc, reviewed at next meeting.
CoS often runs the agenda mechanically; CEO chairs.

Re-shape the CEO's calendar

Every recurring meeting gets a "purpose" tag.
Eliminate or downgrade low-value recurring meetings.
Block 8-10 hours of focus time per week explicitly.
Block 1-2 hours of unscheduled / overflow time per day.
Stop double-booking; CoS becomes the air-traffic-controller for the CEO's calendar.

Establish 1:1 structure

Each CEO-direct gets a recurring 1:1 with consistent agenda doc.
Standard format: their topics, CEO's topics, status of their commitments, blockers, feedback.
CoS attends some 1:1s in week 1-2 as observer; then sometimes takes notes; eventually exits.
Some 1:1s the CoS never attends (sensitive performance conversations, etc.).

MBR / QBR rhythm

Monthly Business Review: 90-120 minutes, all exec team. Every function presents key metrics + trend + commentary on misses. CoS owns the format and pre-read.
Quarterly Business Review: full day, sometimes off-site. OKR cycle close + new cycle open. CoS owns the off-site agenda.

OKR cycle ownership

CoS often becomes the OKR-process owner: timeline, format, review cadence.
CoS does not write OKRs for other functions; CoS facilitates.
Common cadence: Q-1 month start drafting, mid-quarter review, end-quarter retro.

First 90 days: Pick the 2-3 high-leverage initiatives

By day 90, the CoS should own 2-3 named initiatives that the CEO would otherwise be doing themselves or that require cross-functional coordination no one else can do.

Selection criteria

High-leverage (CEO time saved or company outcome moved by 5%+).
Cross-functional (no single VP can own end-to-end).
The CEO has specifically asked or implicitly needs.
Time-bounded (3-6 month delivery).
Has a clear "done" definition.

Common first-tour CoS initiatives

Board-narrative refresh: rewrite the board deck format, run a dry-run, get exec-team buy-in.
Recruiting playbook for next 4 hires (often exec-level).
Off-site / annual planning design + facilitation.
M&A target evaluation (if relevant).
Geo expansion or new-segment go-to-market plan.
Operating model documentation (how decisions get made, who owns what).
Customer-advisory-board design.
Internal communications / all-hands format.

Avoid these in the first quarter

Direct intervention in any specific function (sales, eng, product, marketing) — owned by VPs.
Hiring decisions for any role besides your own team (if you have one).
Performance management of execs (the CEO's job).
"Re-org" projects in your first quarter; you don't have the credibility yet.

How the role typically goes wrong

Failure mode 1: glorified EA

Symptom: Calendar work consumes 80%+ of time. Strategic projects drift. Cause: Either the CEO actually wanted an EA, or the CoS is conflict-averse and accepted scope creep. Fix: Re-anchor with the CEO; if the role really is "elevated EA", be honest with yourself and either accept it or move on. Hire a real EA.

Failure mode 2: ad-hoc whirlpool

Symptom: Spending 60%+ of time on "urgent" requests; nothing strategic ships. Cause: Reactive default mode; principal optimizes for short-term relief. Fix: Block 1-2 days a week for strategic work. Force principal into prioritization conversation.

Failure mode 3: exec-team enemies

Symptom: VPs warning CEO about CoS scope; awkwardness in staff meetings; carved out of decisions. Cause: CoS overreached on a function early; perceived as proxy power. Fix: Public narrative reset (CoS speaks at staff meeting acknowledging mistake); 1:1s with each VP.

Failure mode 4: principal doesn't actually need a CoS

Symptom: 90 days in, the CEO can't articulate what the CoS has done, and neither can the CoS. Cause: Hire was made for the wrong reason (board pressure, peer-CEO copying, "I need help"). Fix: Hard conversation with CEO about role redefinition or role exit. Don't burn 18 months pretending.

Failure mode 5: turf war with COO/CFO

Symptom: Specific decisions or projects are now contested between CoS and COO/CFO. Cause: Strategic Lead archetype overlapping with COO scope. Fix: Explicit scope-line conversation with CEO; the CoS-vs-COO line must be drawn by the CEO, not negotiated peer-to-peer.

Natural exit ramps

The CoS role is not a destination role for most. Plan exit from day 1.

Promotion to operational role: COO, VP of Strategy, VP of [function]. Most common positive outcome at 18-24 months.
Promotion to functional role: Head of Operations, Head of Strategy, Head of Special Projects. Sometimes a sideways relabel.
Move to peer company / network: CoS roles are often filled by network; good CoS gets head-hunted to other CEO networks.
Founder of own thing: the CoS-to-founder pipeline is real; the role gives unique exposure to operating leverage.
Quiet exit: sometimes the role just ends; principal doesn't extend; CoS moves on. Normal; not failure.

Plan: by month 12, articulate to the CEO what your next role is and the 18-month track to get there. Otherwise the role drifts and you become un-promotable.

Interactions with the CEO

Brutal honesty cadence: the CoS is one of few people who can say to the CEO "you're wrong about this." Earn that right; use it sparingly.
Never blindside: any sensitive feedback comes 1:1, never in a meeting.
Don't be the snitch: if a VP shares something with you in confidence, don't carry it directly to the CEO unless it's a serious issue. You destroy your peer-trust if you become the leak.
Match the CEO's communication style: if the CEO writes long memos, your stuff is long memos. If they're a slide person, slides. If they're a Slack person, Slack.
Defend the calendar: be the bad guy for low-value meeting requests. The CEO cannot.
Bring decisions, not problems: every issue you surface comes with 2-3 options and a recommendation. The CEO's bandwidth is the load-bearing constraint.

Integration with other coaches

founder-CEO-firing-coach: for navigating CEO transitions.
fractional-cto-coach: if you're hiring for a similar high-leverage but functional role.
vp-of-engineering-onboarding-coach (TBD): peer-role coaching.
board-prep-coach (TBD): if board-narrative work is central.

The CoS role is high-leverage and high-volatility; first 90 days set the trajectory for the entire tenure. Get the disambiguation right; the rest is execution.