The First 90 Days as a Chief of Staff: A Practitioner's Playbook
Your first 90 days determine everything that comes after. Here's the structured framework I use with every Chief of Staff: what to decode, what to design, and what to deliver in each phase. Plus the traps that derail most new Chiefs of Staff.
Decode — Listen, Map, Understand
Your first month is about listening. Not presenting. Not suggesting. Not proving you're smart. Listening.
You need to decode three things: your CEO, your organization, and the situation you inherited.
Decode your CEO: Ask the five core questions from Week 1 (communication style, decision architecture, strategic focus, energy, authority). Sit in meetings and watch how they think. Notice what energizes them and what drains them. Watch what they say yes to and what they deflect. You're building a mental model of how this CEO operates.
Decode your organization: Who are the key players? Where are the silos? Where's the trust? Where's the dysfunction? Map the leadership team. Understand each person's agenda. Figure out who's aligned with the CEO and who isn't. This is detective work.
Decode the situation: What's the business in the middle of? Is there a crisis? A transition? A scaling challenge? Growth mode or stabilization mode? Understanding the context changes everything about your role.
In this phase, your credibility comes from asking smart questions, not having smart answers. People respect someone who listens carefully before jumping in.
The trap: moving too fast. New Chiefs of Staff often want to prove themselves immediately. Don't. Spend 30 days understanding before you start changing anything. The time you spend decoding in Month 1 makes you 10x more effective in Months 2 and 3.
Design — Build Systems, Earn Trust
You've decoded. Now you build. This phase is about designing the operating system that makes the CEO and organization more effective.
Design the operating rhythm: How often does the CEO meet with the leadership team? When are strategy conversations? When are 1-on-1s? What's the meeting cadence that works for this CEO? Most new Chiefs of Staff need to tighten up the rhythm. There are too many meetings with unclear purpose, or too few meetings where key decisions aren't getting made.
Design the decision architecture: How do decisions actually get made in this organization? What decisions does the CEO need to be in? What decisions can the team own? Create clarity about decision authority, decision timing, and documentation. This is D.A.R.E. framework work: Define who owns what, Advocate for their position, Recommend options, Execute the decision.
Design information flow: What does the CEO actually need to see to be effective? Probably not everything. Create a system where the right information gets to the CEO in the right format at the right time.
Deliver small wins: Identify 2-3 small things you can fix immediately. Not transformational. Just functional improvements that make the CEO's life slightly better. Use them to build trust and prove you understand the landscape.
Your credibility in Month 2 comes from execution, follow-through, and listening to feedback. You'll iterate on the systems you design based on how the CEO responds.
Deliver — Show Results, Expand Impact
By Day 61, you understand the landscape. You've built the foundational systems. Now you expand your impact.
Show results: Point to what you've improved. The decision architecture is working. The leadership meetings are tighter and more productive. Information is flowing better. The CEO has more capacity. These don't have to be massive changes. They just have to be real and measurable.
Identify where you add the most value: By now, you know whether you're a strategic advisor, an operational builder, or a connector. Lean into that. Don't try to be all three equally. Focus on the archetype that matches your strengths and your CEO's needs.
Expand your scope thoughtfully: The CEO is now trusting you with bigger things. Use that trust carefully. Take on something bigger that plays to your archetype. Maybe you start strategic planning if you're the Strategy CoS. Maybe you own the transformation initiative if you're the Transformation CoS.
Build relationships across the org: You should know most of the leadership team by name and understand their challenges. You should have started having regular touchpoints. These relationships are how you'll operate effectively for the next year.
By Day 90, the CEO should feel like you understand them and your organization deeply. They should trust you with increasingly important things. And you should have a clear picture of your role and your value.
The trap: expanding too fast. Don't take on more than you can deliver on. Build the foundation first. The house of cards is fine if you're building on bedrock. You're not building on bedrock until Day 60.
The Traps That Derail Most New Chiefs of Staff
Trap 1: Moving too fast. You're excited. You can see what needs fixing. You want to prove your value. So you start changing things in Week 2. And you lose the trust you've been building. The pattern I see: fast-moving new CoS creates chaos before they create clarity. Slow down. Listen first.
Trap 2: Not building relationships outside the CEO's office. If you only connect with the CEO and ignore the leadership team, you're not a Chief of Staff. You're an assistant. You need relationships across the org. You need to understand different perspectives. You need to be trusted by people who aren't the CEO.
Trap 3: Overstepping your authority. Just because you sit next to the CEO doesn't mean you have decision authority everywhere. You don't. Be very clear about what you own and what you advise on. When you step outside that lane, you create friction and lose credibility.
Trap 4: Staying invisible. Some new Chiefs of Staff are so focused on supporting the CEO that they forget to communicate with the broader organization. The leadership team doesn't understand what you do or why you matter. Create visibility. Let people understand how you add value.
The Credibility Curve — Trust Builds Then Compounds
There's a predictable pattern in your credibility growth over 90 days.
Days 1-30 (Honeymoon): People give you the benefit of the doubt. You're new. They're curious. Your credibility is highest when you ask good questions and listen carefully. The moment you start prescribing solutions, trust goes down.
Days 31-60 (Implementation): You've designed systems. Now you're executing. Your credibility rises if you follow through on commitments and deliver what you said you would. It falls if you miss deadlines or change direction constantly.
Days 61-90 (Consolidation): You've proven you understand the landscape. You've delivered on small commitments. Now the CEO and the team trust you with bigger things. Your credibility compounds because you've earned authority through results.
By Day 90, you should have significantly more credibility than Day 1. Not maximum credibility yet, but real credibility. People believe you understand the business. They believe you follow through. They believe you have the CEO's best interests in mind. They believe you're not here to build your own fiefdom.
That trust is currency. Guard it carefully.
Your First 90 Days
If you're in the middle of your first 90 days, I want to hear what you're experiencing. If you've already done it, share what you'd do differently.
Where are you in the 30/60/90 cycle? What surprised you most about this phase? What's harder than you expected?
Of the four traps I mentioned, which one are you most vulnerable to? What's your strategy for avoiding it?
Looking back on your first 90 days: what would you tell yourself on Day 1 that you know now?
What's one small win you delivered in your first 60 days that built trust with your CEO?