The First 90 Days as a Chief of Staff:
What to Do, When to Do It, and What to Avoid
The first 90 days in a Chief of Staff role set everything that follows. Get them right and you build the trust, access, and context that makes the rest of the role work. Get them wrong and you spend months recovering ground you should have built in week two.
I have watched this play out across twenty years of CoS-level work and more practitioner conversations than I can count. The failure mode almost never looks like incompetence. It looks like good judgment applied in the wrong sequence.
The Two Mistakes That Derail Most New Chiefs of Staff
Before the 30/60/90 framework, it is worth naming the two failure modes it is designed to avoid — because both are tempting, and both look like the right move until they are not.
Moving too fast. The new CoS arrives with energy, capability, and a genuine desire to demonstrate value. Within the first two weeks, they are proposing a restructured operating cadence, surfacing three structural problems to the principal, and beginning to redesign the leadership meeting format. Every one of those moves is substantively correct. None of them have the trust behind them to land. The exec team routes around the new CoS. The principal starts wondering whether they hired someone who listens. The CoS spends the next two months recovering credibility they should never have lost.
Becoming invisible. The opposite error is equally damaging. The new CoS is so careful not to disrupt that they produce nothing visible in the first month. They attend meetings, take notes, and say they are still in listening mode. The principal cannot explain what the CoS is doing. The exec team stops looping them in. The role quietly shrinks before it has a chance to grow.
The first 30 days should feel almost uncomfortably slow for a high-performer — because the work is absorption, not action. That discomfort is a signal you are doing it right.
Days 1–30: Learn Before You Build
Your only job in the first thirty days is to understand. Not to fix. Not to impress. Not to prove yourself. To understand — with enough precision that every action you take in days 31 through 90 is grounded in what is actually true about this organization, this principal, and this moment.
Week one belongs to the principal. Before anything else, understand how they think, how they prefer to receive information, and what is keeping them up at night that is not on the official priorities list. The single most useful question in week one: have they had a Chief of Staff before, and what worked or did not? That answer shapes everything about how you enter the role. If they have never had a CoS, the role will need to be built, not filled — a fundamentally different task.
Weeks two and three belong to the organization. Meet every executive stakeholder in a one-on-one — not to introduce yourself, but to understand their priorities, their blockers, and what they think the principal needs most that they are not getting. Map the informal power structure: who actually influences decisions before they reach a meeting room? These people are not always on the org chart, and knowing who they are is a structural advantage you cannot get from a briefing document.
Week four: one quick win. Before the first month closes, identify one thing you can improve that is small, visible, and not politically charged. Something that clearly makes the principal's day easier. Do it well. Say nothing about it. Let the result speak. This establishes that you produce, not just observe — without triggering the credibility loss that comes from acting before you have built trust.
Days 31–60: Build the Operating System
By day thirty, you understand how things work. Days thirty-one through sixty are about beginning to shape how they work — carefully, with explicit buy-in at each step.
Establish your operating rhythm. A consistent one-on-one cadence with the principal is the foundation of everything. The specific format depends on how they work — daily fifteen minutes or weekly forty-five minutes — but the purpose is always the same: the principal should never have to wonder where things stand. A shared weekly priorities document — five things that matter most this week, reviewed at every one-on-one — is the single most effective tool for preventing the CoS from losing sight of the high-priority work in the flood of daily requests.
Surface one real structural problem. By day sixty, you have enough context to identify something meaningful: not a project that fell behind, but a recurring friction that keeps producing the same problem. Name it to the principal. Bring a point of view on what is driving it. Do not necessarily propose the solution yet. This is the move that distinguishes the Chief of Staff from a senior EA — you noticed the pattern, named it, and brought it to the person who can do something about it without being asked.
Days 61–90: Start to Lead
By day sixty, you have trust, context, and a working operating rhythm. Days sixty-one through ninety are when you begin to operate at the level the role actually requires.
Propose one structural change. Choose the change with the best ratio of impact to political cost — not the most ambitious, the most likely to succeed and be visible. Get explicit buy-in from your principal before you move. Do not assume that enthusiasm in a meeting is the same as authorization. The CoS who moves on implied approval and encounters resistance has made a recoverable but costly error.
Have the 90-day debrief. This is the conversation most Chiefs of Staff skip — and the most important one of the first quarter. Not a performance review. A mutual calibration. Ask the principal directly: what am I doing that is most useful? What am I missing? Where should I be spending more time?
Then share your own read: what you have learned, the structural problems you have identified, and what you believe the highest-value work is for the next ninety days.
This conversation, done well, is the moment the CoS role stops being provisional and starts being permanent. The practitioners who have it consistently report that it changed the nature of their relationship with their principal. The ones who skip it consistently describe a growing uncertainty about whether the role is working — on both sides of the relationship.
The First Week Questions That Actually Matter
The questions you ask in week one shape what you learn in weeks two through four. These are the four that matter most — not because they are comprehensive, but because the answers to each one unlock the information everything else depends on:
To your principal: Have you had a Chief of Staff before? What worked and what did not?
To each executive stakeholder: What do you think the CEO needs most from a Chief of Staff that they are not getting right now?
To yourself at day fourteen: Do I know the two or three things that are most important to my principal right now — not the stated priorities, the real ones?
To yourself at day thirty: Does my principal know they can trust me to handle something without checking in?
If the answer to the last question is no, the first month was absorbed by observation without output. That is recoverable — but the next thirty days need to be different.
CoS Certified addresses the first ninety days in full — not as a generic onboarding checklist, but as a structured entry sequence built from what actually works across different organization types and principal relationships. Join the waitlist to be notified when enrollment opens.