.avif)
.avif)
Most Chiefs of Staff inherit a job description that was written generically, or never written at all. You show up on day one, your principal says some version of “I need leverage,” and then disappears into back-to-back meetings.
Those first 90 days as a CoS are not really onboarding. They are the window where the role gets defined, and it gets defined whether you do it deliberately or not. Do nothing and the job fills up with whatever nobody else wanted. Do it on purpose and you start building toward the version of this seat that actually matters: a strategic partner in the room where decisions get made, not an execution layer sitting underneath it.
Almost nobody arrives at that version on day one. That is normal. The distance between the job you were handed and the job you want to be doing in a few years is the whole game, and the first 90 days are where you either start closing it or quietly accept it.
We have watched hundreds of members go through this transition. The ones who land well do roughly the same things in roughly the same order. Here is the playbook.
Days 1-30: Learn the principal, not just the business
Your instinct will be to learn the business first. Resist it, at least a little. You were probably hired because you learn fast, and the org chart, the metrics, and the strategy deck will still be there in week three. What is harder to learn, and far more urgent, is how your principal actually operates.
In your first month, figure out four things about them.
How they consume information. Some principals want a one-page memo before every decision. Others want you to talk them through it on a walk. If you send beautifully formatted docs to someone who reads nothing longer than a Slack message, you will conclude they do not value your work. They just never saw it.
What drains them. Every executive has a category of work they are bad at or hate. That category might be your first territory of ownership. Taking it over completely, and visibly, is how you buy the trust to do bigger things later.
Where their calendar lies. Compare what your principal says their priorities are with where their time actually goes. The gap between the two is the most useful document you will produce all quarter, and most principals have never seen it laid out.
Who they trust. Map the informal circle: the board member they call first, the engineer whose opinion moves them, the peer they vent to. You will need this map constantly and nobody will hand it to you.
While you are doing this, run a listening tour with the leadership team, managers and/or influential IC's. Fifteen to twenty conversations, thirty minutes each, same questions across three themes:
- Understanding Their World
- e.g. What's the single biggest priority for your team right now?
- e.g. What's the single biggest priority for your team right now?
- Understanding the Organization
- e.g. Where do you see misalignment between teams or leadership?
- Understanding You (the CoS Role)
- e.g. Where do you think someone in my position could be most helpful to you?
Join Chief of Staff Launchpad for the full Listening Tour Framework.
You are not there to fix anything yet. You are building relationship capital you will spend later, and hearing the unfiltered version of the company before people learn to manage what they say around you.
One warning for this phase. Do not confuse access with authority. You will be in every important meeting from week one. That is proximity, not power.
Days 31-60: Pick one visible win
Month two is where new Chiefs of Staff most often stall. You have absorbed an enormous amount of context, you can see fifteen things that need fixing, and the temptation is to chase all of them. Pick one.
The right first win has three properties. It is genuinely painful for your principal or the leadership team. It is achievable in about thirty days without anyone’s budget or headcount. And it is visible, meaning people will notice when it is fixed.
The usual candidates: a leadership meeting everyone agrees is broken, a decision stuck between two functions for a quarter, a planning process that produces documents nobody reads, an investor update that eats a week of the CEO’s month. Any of them will do. What matters is that you take it end to end, fix it completely, and let the result speak.
This is also the month to install your operating rhythm with your principal. Whatever cadence you choose, protect it fiercely. A weekly thirty minutes that never moves is worth more than ad hoc access all week, because it is where you surface the things that do not have a meeting.
Days 61-90: Convert trust into a mandate
By month three you should know things about the company your principal does not. That is the point where the job changes. You stop absorbing context and start acting on it. This is also where most people stop, which is exactly why so many CoS roles stay stuck a level below where they should be.
Three moves help to foster continuous growth in the role.
Define the role in writing. Now, not on day one, is when a role definition is useful, because now you know what the company needs from it. One page: what you own, what you influence, what you stay out of. Review it with your principal. This document is what stops the role becoming a dumping ground for everything unassigned, which is how most Chief of Staff roles go wrong. Revisit this at least quarterly with your Principal to discuss what stays on your plate and what's changed.
Take over a recurring mechanism. Not a project, a mechanism: the weekly leadership meeting, the quarterly planning cycle, the board prep process. Mechanisms compound. Owning one gives you a permanent seat in the operating system of the company instead of a series of temporary assignments.
Say what you see. Somewhere in your first 90 days there will be a moment when you disagree with your principal on something that matters. Take it. Respectfully, with evidence, but take it. Principals do not keep Chiefs of Staff who only reflect their own views back at them. The entire value of this seat is a person close enough to see everything and independent enough to say so.
The most common mistake
When the first 90 days go wrong it is rarely a skill problem. It is that the person optimized for being helpful instead of being useful. Helpful means saying yes to everything, sitting in every meeting, becoming indispensable to the daily churn. Useful means having a point of view about what matters and organizing your time around it. Helpful earns gratitude. Useful earns a mandate. Only one of those compounds into a strategic seat.
Ninety days goes fast. Spend the first thirty learning your principal, the second thirty landing one visible win, and the third converting trust into a written mandate and a mechanism you own. That is the foundation the senior version of this role gets built on, and the people who skip it spend years trying to argue their way into a seat they could have designed in their first quarter.
Ready to go deeper?
The job description nobody wrote for you still isn't going to write itself.
That's the premise of the Chief of Staff Launchpad. One week: two live workshop days, then office hours to pressure test what you built, taught by people who have sat in the seat. Four modules cover the operating system of the role, strategic execution, influence and communication, and getting real leverage out of AI.
You finish with the documents this playbook keeps pointing at. A 90 day mandate plan, a project charter, a decision memo, an executive update, and a full Chief of Staff operating plan as the capstone, all drafted for your actual seat and critiqued by people who have written them before.
Join the next cohort. Save your spot →
