The First 90 Days as a Chief of Staff: A Practical Operating Plan

Feb 8

Takeaway: Diagnose the situation before choosing your pace. Learn the organization, agree on how you will work with the principal, and deliver a small number of improvements that fit the moment.

A new chief of staff rarely receives a stable job that can be executed from a standard checklist. The principal, leadership team, and company stage all shape the mandate. The first 90 days are how you turn that ambiguity into an operating agreement.

Learning should be the default at the start, but it isn't a rule against action. A healthy company gives you room to observe. A turnaround, safety issue, financial risk, or broken customer process may require immediate intervention. The useful discipline is to make early action narrow, explicit, and tied to the diagnosed situation.

Diagnose the transition before setting the plan

Michael Watkins's The First 90 Days is a widely used framework for leadership transitions (Harvard Business Review Press). His STARS model describes five situations: start-up, turnaround, accelerated growth, realignment, and sustaining success. The right entry strategy depends on which situation you have entered (Watkins, HBR).

For a chief of staff, start with four questions:

Why was the role created now? Look past the job description to the pressure that made the principal act.
Is the leadership team executing, strained, or in active trouble? The answer changes the pace and tone of your first moves.
Are you building a new function or inheriting one? An inherited role comes with expectations, relationships, and unfinished work.
What requires attention before the normal learning period ends? Name genuine urgency instead of treating every request as urgent.

Write a short transition hypothesis after your first week. It might say: "This is an accelerated-growth situation. The immediate risk is unclear ownership across two launches; the broader need is a repeatable planning cadence." Review it with your principal. The statement will change as you learn, but it gives your listening and early work a purpose.

Days 1 to 30: Build the map

The first month should produce a useful model of the organization, not a pile of introductory meetings.

Run a structured listening tour

Meet each leadership-team member and a deliberate sample of people closer to the work. Ask a consistent set of questions so you can compare answers:

What is working well that should be protected?
What most often slows the team down?
Which decision keeps returning without closure?
Where does ownership become unclear?
What should this role make easier within six months?

Record themes, examples, and disagreements. Five similar complaints may point to a system problem. Five different explanations of the company's top priority may point to an alignment problem. Treat either as a hypothesis until you have observed the work itself.

Agree on the relationship with the principal

The role depends on understanding how the principal works. Gabarro and Kotter describe the manager relationship as one of mutual dependence and argue for understanding both parties' goals, strengths, weaknesses, and working styles (HBR).

Ask directly:

What decisions can I make without you?
Which issues must reach you immediately?
How do you prefer recommendations to be presented?
Where do you want me in the room, and where should I stay out?
What would make you say this hire is working after 90 days?

Turn the answers into a lightweight working agreement. Include update format, one-on-one cadence, delegated authority, escalation thresholds, and how you will handle disagreement. This prevents both overreach and unnecessary dependence.

Map the current operating system

Document how work actually moves:

Recurring leadership and operating meetings
Planning and goal-review cycles
Major cross-functional initiatives
Decision rights and common escalation paths
Where decisions and operating documents live
Known commitments with no clear owner

Don't redesign the system as you map it. Note what each mechanism is trying to accomplish, who relies on it, and what evidence shows it is failing.

Handle urgent issues narrowly

If a serious problem can't wait, state the exception. For example: "I am pausing the listening plan for two days to resolve the launch ownership gap. I will document the decision, then return to the broader diagnosis." This makes the intervention legible and reduces the chance that one emergency becomes your permanent way of working.

Days 31 to 60: Turn evidence into credibility

By the second month, you should be able to name a few patterns with examples. Now choose work that proves your judgment without pretending you understand everything.

Select one or two early wins

An early win should meet four tests:

The leadership team already recognizes the problem.
The principal supports the change.
The result can be seen within a few weeks.
The change doesn't require authority you haven't been delegated or context you haven't yet developed.

If several leaders already agree that the weekly meeting wastes time, a clearer agenda and decision recap can be a useful early win. Confirm the principal's support and understand who currently owns the format before changing it. A meeting is political infrastructure, even when everyone complains about it.

Another good candidate is a decision that keeps being revisited because no record exists. A small log can help, but don't announce a company-wide documentation overhaul before showing that the practice solves a real problem.

Build reliability in visible loops

Close every commitment you accept. If a date moves, say so before it passes. Send the principal a short weekly brief that distinguishes information, decisions, and risks. This is how they learn which work can be delegated without disappearing.

Make the same reliability available to other leaders. A chief of staff who only serves the principal can quickly be perceived as a gatekeeper. Help functional leaders prepare decisions, remove cross-functional blockers, and understand what the principal needs from them.

Recheck the role hypothesis

At day 45 or 60, compare what you were hired to do with the work the organization now needs. Bring discrepancies to the principal. A useful conversation covers:

What should remain in your remit?
What belongs with a functional leader?
Which temporary work should end after stabilization?
Which outcomes will matter in the next quarter?

Days 61 to 90: Install only what the team will maintain

The final month is the time to make successful practices repeatable.

Formalize the operating cadence

Define the rhythm the leadership team will use: weekly tactical work, periodic strategic decisions, planning, and goal review. Give each meeting a purpose, owner, inputs, outputs, and rule for who attends.

Don't add meetings simply to make the system look complete. Remove or combine routines that serve the same job.

Create a durable decision record

If the team is losing or relitigating decisions, start a decision log. Capture the decision, owner, date, context, tradeoffs, and status. Link it to meeting notes and operating documents rather than duplicating the same answer across several places.

Define success for the next two quarters

Close the first 90 days with a written agreement about the next phase. Choose a small set of outcomes, how progress will be seen, and which decisions you can own. Include the work that should stop. An expanding list of responsibilities without explicit priority is not a mandate.

A one-page plan

By day 30

Diagnose the transition situation and urgent exceptions.
Complete a structured listening tour.
Agree on working norms with the principal.
Map the current operating system and decision paths.

By day 60

Deliver one or two supported early wins.
Establish reliable update and escalation loops.
Build useful relationships across the leadership team.
Reconcile the initial remit with what you have learned.

By day 90

Formalize the smallest operating cadence the team needs.
Create a maintained decision record where the need is clear.
Agree on outcomes, authority, and priorities for the next two quarters.

Frequently asked questions

Should I make changes in my first week?

Make narrow changes when the risk of waiting is clear. For everything else, learn enough to understand the purpose, dependencies, and owners before changing the process.

What if the company has never had a chief of staff?

Treat role definition as part of the first 90 days. Set an initial remit with the principal, review it at days 30 and 60, and document what you own, influence, and escalate.

How do I show value early without overstepping?

Choose a problem the team already acknowledges, confirm sponsorship, and improve a bounded part of it. Make the result and the handoff visible.

What if I joined during a turnaround?

Shorten the diagnostic cycle, but don't abandon it. Identify the few risks that require immediate action, name the temporary decision process, and keep learning while the urgent work moves.

Use the free First 90 Days Chief of Staff Operating Plan to turn these milestones into a week-by-week working document.

Adrienne Gaughan