Chief of Staff Best Practices for Startups

What a Chief of Staff actually does at a startup

At a startup, a Chief of Staff (CoS) is the operating partner to the founder or CEO. The role is not an executive assistant, not a project manager, and not a generalist utility player. A CoS owns the operating rhythm of the company — the cadences, decisions, and follow-through that translate the founder's priorities into shipped work.

In practical terms that means running the weekly leadership sync, keeping OKRs and action items honest, unblocking cross-functional projects, and preparing decisions before they reach the founder's desk. Done well, the CoS gives back roughly one day per week of the founder's time in the first 60 days.

Build a weekly operating cadence you can defend

Best practice: pick one weekly leadership meeting, one monthly business review, and one quarterly planning session — and protect them. Every other recurring meeting should justify itself against that spine.

The weekly leadership sync should have a fixed 45–60 minute agenda: metrics, blockers, decisions needed, and owner check-ins on the top 3–5 priorities. No status theater. If a topic needs more than 10 minutes, it becomes a separate working session with the two or three people who actually own it.

The monthly business review is where the CoS pulls the company out of the week and looks at trends: pipeline, burn, hiring, retention, and OKR progress. The output is a one-page memo, not a 40-slide deck.

Use a lightweight decision framework (DACI or RAPID)

Startups stall when nobody knows who decides. A Chief of Staff should implement a simple decision framework — DACI (Driver, Approver, Contributors, Informed) or RAPID — and use it on every non-trivial decision.

The rule of thumb: if a decision has been discussed in two meetings without an owner, the CoS assigns a Driver and a deadline the same day. Decisions get written down in one place — a Notion or Coda doc, one row per decision, with date, owner, context, and outcome. This becomes the company's decision log and the single most valuable artifact for onboarding future hires.

Delegate with a written charter, not a verbal handoff

Founders lose the most time on ambiguous delegation. Best practice: every recurring responsibility a founder wants to hand off gets a one-page charter — outcome, success metric, decision rights, escalation path, and cadence for review.

A CoS drafts these charters, gets founder sign-off in a 15-minute review, and then owns the handoff to the responsible team member. Six charters in the first quarter is a realistic target and typically clears 40–60% of the founder's operational load.

Install a communication system, not more meetings

The default fix for confusion at a startup is another meeting. A Chief of Staff should fix it with a communication system instead: a weekly founder update (async, written, same format every week), a shared decision log, a single source of truth for OKRs, and clear rules for what belongs in Slack vs. a doc vs. a meeting.

The weekly founder update is non-negotiable. It goes out every Friday and covers wins, misses, decisions made, decisions needed, and one ask. Investors, advisors, and the leadership team all read the same version. This one document eliminates roughly 30% of one-off status questions.

Keep OKRs boring and current

Best practice: three to five company-level objectives per quarter, with two to four measurable key results each. The CoS owns the OKR document, updates progress weekly, and flags any KR that hasn't moved in two weeks.

The failure mode is OKRs that get set at the offsite and never opened again. The fix is embarrassingly simple — the CoS pastes the OKR table into the weekly leadership sync notes every single week.

The first 90 days: what a Chief of Staff should ship

Days 1–30: listen. Sit in every recurring meeting, interview each leader, and map the current operating rhythm. Output: a written diagnostic — what's working, what's broken, and the top three things to fix.

Days 31–60: install the cadence. One weekly leadership sync, one monthly business review, one decision log, one OKR doc, one weekly founder update. Kill or consolidate at least two existing recurring meetings.

Days 61–90: hand off. Draft charters for the top three responsibilities the founder should no longer own, and transition each to a leader with a written success metric.

When to hire a Chief of Staff (fractional vs. full-time)

A fractional Chief of Staff usually fits pre-seed through Series A companies with 5–50 people, where the founder is the bottleneck for follow-through but the company can't yet justify a $180K–$250K full-time hire.

Move to full-time when the operating load is consistently more than 25–30 hours per week, the CoS is running board prep and fundraising ops end-to-end, or the company is scaling past ~75 people and needs a permanent partner to the CEO.

Common mistakes founders make with their first Chief of Staff

Hiring too junior. A great EA is not a great CoS — the role requires someone who can push back on the founder and own executive-level decisions.

No written charter for the role itself. If the CoS mandate isn't in writing, it will drift into whatever the founder happens to be anxious about that week.

Treating the CoS as an inbox. The CoS is a force multiplier on decisions and cadence, not a dumping ground for tasks the founder doesn't want to do.