The First 90 Days as a Chief of Staff: A Practical Operating Plan
Takeaway: Your first 90 days as a chief of staff are for diagnosing the situation, earning trust, and delivering one or two visible wins, not for reorganizing everything before you understand why it works the way it does.
The chief of staff role is unusual in that it rarely comes with a job description you can execute against on day one. You're hired to make a principal and a leadership team more effective, but what that means depends entirely on the person, the company, and the moment. That ambiguity is why the first 90 days matter so much. The habits, relationships, and reputation you build in the first three months tend to define how much leverage you have for the next two years.
The most durable framework for this period is Michael Watkins's The First 90 Days, the standard reference for leadership transitions with more than a million copies in print (Harvard Business Review Press). The plan below adapts its core ideas to the specific realities of the chief of staff role.
First, Diagnose the Situation You Are Actually In
Watkins's central insight is that there's no single right way to start a new role, because new roles come in different shapes. His STARS model names five of them: start-up, turnaround, accelerated growth, realignment, and sustaining success. Each calls for a different early strategy, and the fastest way to fail is to apply a turnaround playbook to a healthy team, or a caretaker's touch to a business that's on fire (Watkins, HBR).
For a chief of staff, the question is usually some version of these:
- Is this a new function or an existing one? If you're the first chief of staff the company has had, you're in a start-up situation and you're building the role from scratch. If you're replacing someone, you have inherited expectations, relationships, and possibly baggage.
- Is the leadership team healthy or in trouble? A team that's aligned and executing needs a very different kind of help than one that's fighting or drifting.
- Why does the principal want this role filled now? The real answer, which you have to draw out carefully, tells you what problem you're really being hired to solve.
Spend your first days getting clear on which situation you're in. It changes everything that follows.
Days 1 to 30: Learn Before You Act
The strongest temptation in a new chief of staff role is to prove your worth immediately by fixing something visible. Resist it. In the first month your job is to build an accurate map of the organization, and you can't do that while you're busy rearranging it.
Run a structured listening tour
Set up 30-minute conversations with every member of the leadership team and a selection of people one and two levels down. Ask the same core questions of everyone so you can compare answers:
- What is working well right now that we should protect?
- What is the biggest thing getting in the team's way?
- If you had my role, what is the first thing you would look at?
- How do decisions actually get made here?
Take careful notes and watch for patterns. When five people independently name the same broken process, you have found real work. When they each name something different, the problem is usually alignment itself.
Understand your principal in detail
The chief of staff relationship rises or falls on how well you understand the person you support. In the classic HBR article Managing Your Boss, Gabarro and Kotter frame this as a relationship of mutual dependence and argue that you need a clear read on your principal's strengths, weaknesses, working style, and needs before you can be genuinely useful (HBR).
Get specific and early. How does the principal prefer to consume information, in writing or in conversation? What do they want to be looped in on, and what do they want handled without them? Where do they lose the most time? What does a good week look like from their seat? Where possible, ask these questions directly rather than guessing.
Map how the machine runs
Document the current operating rhythm as it exists, not as it should be. What meetings happen, who attends, and what are they for? How does the company plan and track goals? Where do decisions get made and recorded, if they get recorded at all? You're building the baseline you will improve later, and you will spot the gaps just by writing it down.
Days 31 to 60: Earn Trust and Pick Your First Win
By the second month you have a map. Now you convert learning into a small amount of credible action.
Choose one or two early wins, carefully
Watkins emphasizes securing early wins that build momentum and credibility, but the choice matters more than the speed. For a chief of staff, the best first win is usually a visible improvement to something the leadership team already feels the pain of: a meeting that wastes everyone's time, a planning process that produces no follow-through, a decision that keeps getting relitigated because no one wrote it down.
Pick something you can genuinely improve within a few weeks, that helps the whole team rather than just the principal, and that doesn't require you to have political capital you haven't earned yet. Tightening the weekly leadership meeting is a common and safe first project, because everyone benefits and the improvement is obvious.
Avoid the trap of the ambitious reorganization. Reworking the entire operating model in month two, before you fully understand why the current one exists, is how new chiefs of staff burn trust fast.
Establish your working relationship with the principal
This is the month to move from observing your principal to actively supporting them. Set up a recurring one-on-one if you don't have one. Start producing a short weekly brief that surfaces what needs their attention. Begin taking small things off their plate and closing the loop reliably, so they learn that anything handed to you comes back done.
Reliability compounds. Every commitment you keep in these weeks makes the next, larger delegation possible.
Build relationships across the leadership team
A chief of staff has no formal authority over the executives they work with. Influence comes entirely from trust and usefulness. Use this month to become genuinely helpful to each leader individually, so that when you later need to hold the team to a process, you're enforcing it as a trusted partner rather than as the principal's enforcer.
Days 61 to 90: Install the System
By the final month you have earned enough trust to put durable structure in place. This is where you shift from fixing individual problems to building systems that prevent them.
Set up the operating cadence
Lock in the rhythm the leadership team will run on: the weekly tactical meeting, the longer strategic sessions, the planning and review cycle, and how goals are tracked between them. If any of these didn't exist or ran poorly, this is when you formalize them.
Stand up a single source of truth
Start a decision log and a clear home for operating documents. Even a simple, well-maintained record of what was decided, by whom, and why, saves the team from relitigating settled questions and gives new people a way to get up to speed. This becomes one of the most quietly valuable things you own.
Agree on how you will be measured
Close the first 90 days with an explicit conversation with your principal about what success looks like over the next two quarters. The role is broad enough that you and the principal can easily hold different definitions of a good job. Naming a few concrete priorities and how you will both know they're on track turns an ambiguous role into a plan.
A 90-Day Plan on One Page
- Days 1 to 30: Diagnose the situation. Listen widely, understand the principal, map the operating rhythm. Change little.
- Days 31 to 60: Deliver one or two visible wins. Build the working relationship with the principal. Earn trust across the leadership team.
- Days 61 to 90: Install the system. Set the operating cadence, stand up a single source of truth, and agree on how your success will be measured.
FAQ
Should I make changes in my first week as chief of staff? Only small, obviously helpful ones. The first weeks are for understanding why things work the way they do. Large changes made before you have that context tend to break things you didn't know were load-bearing and cost you trust you haven't yet earned.
What if the company has never had a chief of staff before? You're in a start-up situation, in Watkins's terms, which means part of your first 90 days is defining the role itself. Be explicit with your principal about what you will and won't own, and expect to renegotiate the scope as both of you learn what actually helps.
How do I show value early without overstepping? Pick a problem the whole leadership team already feels, improve it visibly within a few weeks, and give credit generously. Improving the weekly leadership meeting or a broken planning process are common early wins because they help everyone and don't require political capital you haven't built yet.
What does a chief of staff do in the first 90 days? The work falls into three phases. The first month is for diagnosis: a structured listening tour, learning the principal in detail, and mapping how the organization actually runs. The second is for earning trust and delivering one or two visible wins the leadership team already feels the need for. The third is for installing durable systems, the operating cadence, a single source of truth, and an explicit agreement on how your success will be measured.
What should be in a chief of staff 30-60-90 day plan? Structure it around what each milestone should produce. By day 30, you have listened widely and built an accurate map of the organization and the principal, and changed little. By day 60, you have earned credibility and delivered a visible early win. By day 90, you have installed the operating cadence and a decision log and agreed with your principal on concrete priorities for the next two quarters. Keep it a plan you revise as you learn, not a fixed script.
If you want a running start, our First 90 Days Chief of Staff Operating Plan is a fill-in template that turns this framework into a week-by-week checklist you can bring to your first day. Join the email list to download it and get future operator playbooks as they publish.
