30 60 90 Day Plan for Chief of Staff: Week-by-Week Example
10 min read ยท 2026-10-25
A 30 60 90 day plan for chief of staff hires splits your first quarter into three jobs: learn how your principal thinks and decides in the first 30 days, take over the leadership team's operating rhythm by day 60, and own one cross-functional priority end to end by day 90. Your CEO hired you to get time and attention back. They need to see that happen fast, without you stepping on their direct reports.
Generic onboarding plans do not fit this job. A chief of staff has no team, no fixed function and only borrowed authority. So the plan below is built around what only this role does: a working agreement with your principal, a listening tour of the executive team, the weekly staff meeting, the decision log, board prep and the calendar. Each phase ends with a milestone your principal can check.
The plan assumes you report to a CEO. If you support a CTO, a COO or a division president, keep the structure and swap in their meetings and their direct reports.
The roadmap at a glance
Goal: By day 90, the CEO trusts you to run the leadership operating rhythm and you own one cross-functional priority with a visible result. Duration: 90 days (13 weeks)
Working agreement (Week 1)
Agree with your principal on what you own, what you decide and how you communicate.
- Hold a 90-minute session with your principal on goals for the role, decisions you may make on their behalf and topics that stay theirs.
- Agree on access: calendar, inbox triage rules, shared drives, board materials and which meetings you attend.
- Set a weekly 1:1 with a fixed agenda: priorities, decisions pending, people issues and what to drop.
- Meet the executive assistant and agree who handles scheduling, travel and requests so you do not duplicate work.
Milestone: A one-page working agreement, reviewed by your principal, listing your scope, your decision rights and the topics you stay out of.
Listening tour (Weeks 2-4)
Learn how the leadership team works and where it gets stuck.
- Hold 45-minute 1:1s with every direct report of the CEO, using the same five questions each time.
- Read the last two board decks, last quarter's plan or OKRs, the budget and recent leadership meeting notes.
- Sit in on every meeting your principal runs and note how decisions get made, deferred or reopened.
- Meet a few people below the leadership team, such as front-line managers and the FP&A lead, to hear what the top does not.
- Keep a running list of stuck decisions, duplicated work and recurring complaints.
Milestone: A listening tour readout shared in your 1:1: three to five themes, the top stuck decisions and a proposed fix for the staff meeting.
Operating rhythm (Weeks 5-8)
Take over the meetings and trackers that keep the leadership team aligned.
- Redesign the weekly staff meeting: agenda out 24 hours ahead, pre-reads, timeboxed topics and decisions recorded.
- Start a decision log with the date, the decision, the owner and what would make you revisit it.
- Build one priorities tracker for company goals, with an executive owner, a status and the next milestone for each.
- Map the year: board meetings, quarterly planning, business reviews, offsites and budget deadlines.
- Run a calendar audit of your principal's last four weeks against their top three priorities.
Milestone: Your principal hands you the staff meeting and the priorities tracker, and every action from the meeting has an owner and a due date.
First owned priority (Weeks 9-12)
Drive one cross-functional initiative your principal cares about to a visible result.
- Pick one priority with your principal from the listening tour themes, such as quarterly planning or a stuck pricing decision.
- Write a one-page charter: problem, outcome, owners, decision makers, timeline and what is out of scope.
- Run a short weekly working session with the executives involved and send a written update after each one.
- Set a prep timeline for the next board deck or business review that gets drafts to the CEO a week early.
Milestone: The initiative reaches its first agreed result, such as a signed-off quarterly plan or a decision made and announced, with the owners named in the charter.
90-day review (Week 13)
Check results with your principal and agree on the next quarter.
- Ask your principal and three or four executives what you should start, stop and continue.
- Compare the calendar audit, decision log and tracker with your day-30 baseline.
- Propose what you keep, what you hand back and the one or two priorities for next quarter.
Milestone: An updated working agreement and a next-quarter plan, approved by your principal in your 1:1.
What makes a chief of staff plan different
Most 30-60-90 plans assume you run a function with a team and a target. A chief of staff runs neither. Your scope is whatever your principal needs, your authority is borrowed, and your results show up in other people's work. That changes what a good first quarter looks like.
Think of the role as three jobs. As an operator, you run the meetings, trackers and calendar that keep leadership on track. As an integrator, you connect work across teams that do not report to each other. As an advisor, you tell your principal what others will not. Build them in that order. You earn trust through the operator work, and that trust is what gets your advice heard.
Your first-week list
The first week sets the tone. Your principal and the executive team are watching for one thing: will you make their lives easier, or add a layer? Keep the week about access, listening and small, visible help.
Do not launch anything new in week one. Changing a meeting format before you know why it exists is the fastest way to look like you are taking over.
- Hold the working agreement session with your principal and write it up the same day.
- Get access to the calendar, shared drives, the board portal and the leadership team's chat channel.
- Book 1:1s with every executive for weeks 2 to 4.
- Read the last two board decks, this year's plan and budget, and the last month of leadership meeting notes.
- Agree on a written split of tasks with the executive assistant.
- Shadow your principal for at least two full days, including one external meeting.
People to meet and what to ask
Your listening tour has two goals: learn how the business really runs, and show each executive you are there to help, not to report on them. Tell each person what you will do with their input. When you report back, share themes, not who said what.
Use the same five questions with everyone so you can compare answers. What are your top priorities this quarter? Which decisions are stuck, and who needs to make them? Where does work fall between teams? What does the staff meeting do well and badly? What should a chief of staff never do here?
- Executive team: CFO, CTO, head of sales, CMO, head of product, head of people and general counsel.
- Executive assistant: how the calendar is built, recurring conflicts and what the CEO protects.
- FP&A or finance lead: the planning calendar, the budget process and the numbers leadership reviews each week.
- Two or three front-line managers: what reaches them from leadership and what gets lost.
- Board chair or lead investor: only if your principal asks, and with them in the loop.
- Your predecessor, if there was one: what worked, what did not and which commitments are still open.
Example: a filled-in plan for a chief of staff to a CEO
Picture a 300-person software company. The CEO spends most of the week in meetings, the weekly staff meeting always runs over, and quarterly planning has slipped twice. Here is how the 90 days could look.
Notice that executives own the outcomes wherever possible. The chief of staff makes things happen, but does not own every result. That is what keeps the role from turning into a bottleneck.
- Days 1-30, learn: working agreement signed off in week 1, twelve listening tour interviews done, readout shows three themes (planning slips, decisions get reopened, CEO calendar overloaded). Owner: chief of staff. Milestone: readout reviewed in the CEO 1:1.
- Days 31-60, run the rhythm: new staff meeting format with pre-reads, decision log live, priorities tracker covering the five company goals. Owner: chief of staff for the format, each executive for updating their goal weekly. Milestone: staff meeting ends on time four weeks in a row.
- Days 61-90, deliver: next quarter's plan built in two working sessions and approved before the quarter starts. Owner: CFO and head of product for content, chief of staff for process. Milestone: plan signed off by the CEO with owners and dates.
- Day 90, review: the calendar audit shows more CEO time on the top three priorities than at day 30, and board deck coordination moves to you. Milestone: updated working agreement.
Quick wins that build trust
A good quick win for a chief of staff saves your principal time or unblocks an executive, costs little political capital and shows within days. It should make someone else look good. Wins that put you at the center, or that override an executive's call, cost more trust than they earn.
Pick one or two from the list below based on what your listening tour found. Ask your principal before you change anything another executive owns.
- Send the staff meeting agenda and pre-reads a day ahead, and the action list within an hour of the end.
- Put one stuck decision in front of the right person with a one-page brief and a deadline.
- Cut or shorten recurring meetings on your principal's calendar that no longer serve a priority.
- Build a board prep calendar that works back from the meeting date, so drafts stop arriving the night before.
- Draft a short weekly note from your principal to the leadership team on priorities and decisions made.
Metrics to track
A chief of staff's work is hard to measure because it shows up as other people's results. Pick a few indicators you can collect without extra admin, set a baseline in the first month and report the change at day 60 and day 90.
Add one direct measure too. At day 30 and day 90, ask your principal and each executive to score how useful your work has been from 1 to 5, and the one thing you should change.
- Principal's time on priorities: share of calendar hours spent on the top three priorities, from a monthly calendar audit.
- Decision speed: decisions in the log open for more than two weeks, and how many got reopened.
- Follow-through: share of staff meeting actions closed by their due date.
- Meeting health: staff meetings that start and end on time, with pre-reads sent a day ahead.
- Planning and board prep: whether the quarterly plan and the board deck reached the CEO on the agreed date.
How to present the plan to your CEO or in an interview
With your principal, keep it to one page with three columns: days 1-30, 31-60 and 61-90. Under each, list the goal, two or three deliverables and the milestone. Add one line at the bottom on what you will not do, such as making decisions for executives or managing their teams. That line often reassures a CEO more than the rest of the page.
In an interview, the plan shows you understand the job before you have it. Tailor it to the company's stage and to the operating problems the CEO described. Name the meetings and trackers you would set up, present it as a draft you would refine after the listening tour, then ask what the CEO most wants off their plate. The answer tells you whether the role is real.
Once you start, review the plan in your 1:1 at the end of each 30-day block. Mark each milestone as done, late or dropped, and say why. A plan that changes because you learned something is a good sign. A plan nobody opens after week two is not.
Common mistakes to avoid
- Changing the staff meeting in week one makes you look like you are taking over, so listen for a month and propose changes in your readout.
- Acting as the CEO's messenger kills trust with executives, so tell each person how you will use what they share and report themes, not names.
- Making calls that belong to an executive turns you into a shadow boss, so bring the decision to its owner with a brief and a deadline.
- Saying yes to every request your principal mentions spreads you too thin, so agree on two or three priorities and a written list of what you will not do.
- Keeping the operating rhythm in your head makes you a single point of failure, so document the meeting formats, the yearly calendar and the tracker so someone else can run them.
- Skipping the 90-day review leaves your role vague, so book it in week one and update the working agreement when you hold it.
Frequently asked questions
What should a chief of staff do in the first 30 days?
Agree on scope and decision rights with your principal, then run a listening tour with every executive. Read the board decks, plan and budget, and sit in on your principal's meetings. Finish with a short readout of themes and stuck decisions, and hold off on big changes until then.
What does a chief of staff own after 90 days?
Usually the leadership operating rhythm (staff meeting, priorities tracker, planning and board prep calendar) plus one or two cross-functional initiatives. The exact scope depends on your principal and belongs in your working agreement. Review it every quarter.
How do you write a 30 60 90 day plan for a chief of staff interview?
Use one page with three columns, and give each 30-day block a goal, deliverables and a milestone. Base it on what you know about the company and the problems the CEO described, and present it as a draft you would refine in the first month. End by asking what the CEO wants off their plate.
How is a chief of staff different from an executive assistant?
An executive assistant manages the principal's calendar, travel and logistics. A chief of staff manages priorities, the leadership operating rhythm and cross-functional work, and often acts as an advisor. The two work closely, so agree early on who handles what.
How do you measure a chief of staff's success?
Look at how leadership works: more principal time on top priorities, fewer stuck decisions, actions closed on time and plans delivered on schedule. Add direct feedback from your principal and the executive team at day 30 and day 90.