Chief of Staff First 90 Days: What Should You Prioritize?
Chief of Staff or Chief of Chasing?
In the first 90 days, a Chief of Staff should agree on a mandate, map decision authority, test one bounded operating loop, and assign owners who can maintain it. Start with role clarity, then test leadership inputs, decisions, and follow-through. Use the final phase to document the process and review the mandate with the CEO.
Access to the CEO doesn't give you authority over every loose end. Make the decision rights explicit, test the loop on one cross-team problem, and check whether people can keep it running without your next nudge.
Leadership prep and follow-upThe brief has a next move
A bounded onboarding review connects a changed priority to a decision and functional follow-up.
- Decision prep
- Chief of Staff coordinates the question
- Decision authority
- Authorized functional or executive owner
- Follow-through
- Functional owners update the affected work
Coordination stays visible without making the Chief of Staff the owner of every result.
How should a Chief of Staff define the mandate in the first 30 days?
Start with the CEO's current priorities and where they believe execution is breaking down. Ask functional leaders the same questions independently. The difference between the answers is an investigation list, not a verdict on either side.
Agree on a short mandate with the CEO. Include what you own, where you coordinate, what you can decide, and which matters require the CEO or a functional leader. Explain that mandate to the people whose cooperation it requires.
Copy this starter:
Purpose of the role this quarter:
Company priority I will support:
Recurring process I own:
Decisions I can make:
Decisions I prepare but do not make:
Functional responsibilities that stay with their owners:
Escalation route when authority is unclear:
How the CEO and I will review progress:
What we will deliberately leave outside this mandate:Learn how the CEO consumes information and makes tradeoffs. A concise written pre-read may help one executive; another may need a short discussion before reviewing options. Adapt the preparation without removing the decision record.
What belongs in a Chief of Staff decision map?
An org chart shows reporting lines. A decision map shows who can settle the choices that repeatedly cross those lines.
| Recurring decision | Who prepares it | Who decides | Who contributes | Who must hear the outcome |
|---|---|---|---|---|
| Priority tradeoff across functions | [Driver] | [Authorized leader] | [Affected functions] | [Teams changing work] |
| Customer scope exception | [Driver] | [Commercial authority] | [Sales, CS, delivery] | [Account and implementation owners] |
| Roadmap change | [Driver] | [Product authority] | [Engineering and affected functions] | [Teams using the roadmap] |
Fill this in from actual authority, not job titles alone. When no one can identify the decision maker, ask the sponsor to resolve the gap. Do not quietly become the approver because everyone copied you on the thread.
What should a Chief of Staff test in days 31–60?
Pick a bounded problem that the CEO and functional leaders agree matters: a recurring cross-team decision, an unreliable pre-read, or follow-up that disappears after staff meetings. Avoid redesigning the entire company's cadence in your second month.
For an onboarding problem, start with one weekly review covering Product, Sales, and CS. Gather changed priorities, dependencies, and decision requests. Keep routine status in writing. Bring only issues that need the available decision makers into the discussion.
Use this minimal pre-read:
| Priority | What changed | Evidence | Assumption gap or blocker | Decision requested | Decision maker | Needed by |
|---|---|---|---|---|---|---|
| [Outcome] | [Observable change] | [Source and date] | [Specific issue] | [One question] | [Person] | [Date and reason] |
After the meeting, record the decision, action owner, due date, and affected people. At the next review, inspect whether the action changed the work. If nobody can act on the output, adjust the process or authority before expanding it.
What should be repeatable by day 90?
Document how inputs arrive, who checks them, how decisions are routed, and who verifies follow-through. Give each functional leader responsibility for their own commitments. Your role can coordinate the system without absorbing ownership of every result.
Bring a short review to the CEO: what the pilot revealed, which decisions were resolved, what remains open, and what should change about your mandate. Use evidence from the actual review cycles. Don't claim time savings or business impact you have not measured.
| Phase | Deliverable | Acceptance check |
|---|---|---|
| Days 1–30 | Mandate and initial decision map | CEO and relevant leaders understand your authority |
| Days 31–60 | Bounded review with a decision record | An issue reaches the right person and has a clear next step |
| Days 61–90 | Written operating process and revised mandate | Inputs, decisions, and follow-up have owners beyond you |
Adapt the sequence to your mandate, any reorganization, and urgent work.
Chief of Staff is not a forwarding address.
When an update is missing, first check whether the owner knows what is required and why it matters. When a decision is missing, check authority. When a commitment returns, ask what prevented completion.
These are different problems. Solving all three by sending more reminders can conceal the reason work is stuck. Establish a route the company can use, then step in where the route fails.
You should finish the first quarter with a clearer mandate and a repeatable process people understand. A longer queue of people waiting for your reminder is an early warning about the process you built.
What is Decided?
Decided is an AI operating alignment layer for fast-moving SaaS companies. Clara runs recurring private 1:1 AI voice check-ins about priorities, blockers, decisions, and commitments. Decided compares the answers and prepares an alignment map, a weekly leadership brief, and context for follow-up.
Coordination stays visible without making the Chief of Staff the owner of every result.
People review the context and make the decisions. Before rollout, explain what is captured, who sees the output, how it is used, and whether participants can review notes. Private 1:1 describes the format, not anonymity. Decided is not hidden monitoring, employee scoring, or an automated employment decision system.
Explore Decided for Chiefs of Staff. Try a live voice check-in to see how it works.
Sources.
The Chief of Staff Network's first-90-days guide discusses the principal, role definition, and operating responsibility. Atlassian's DACI play distinguishes decision roles.
