Your First 90 Days on the Executive Team: A Playbook for New C-Suite Leaders

Most new executives walk into their first week with a plan for their function and no plan for their peers. They know the P&L, the team structure, the three problems the board hired them to fix. What they don't have is a map of how the executive team operates—who defers to whom in a disagreement, which topics are settled in the meeting and which get decided in a hallway conversation afterward, what "alignment" means to the CEO versus what it means to the CFO. That gap is where new executives fail. Not because they lack skill, but because they misread the room for months while assuming competence will speak for itself [1].

Get One Win Before You Get Understood

The instinct on day one is to listen. Tour the floors, schedule 30-minute coffees, absorb context. Ben Horowitz tells a story about an executive who arrived quoting Stephen Covey—"first seek to understand, then be understood"—and planned to spend a month just talking to people. Horowitz's response: "You're going to be fired in a month if you do that" [8]. The correction isn't to skip listening. It's to compress it. Pair every listening session with a search for the single problem you can solve this week. One deliverable. One decision unblocked. One thing the team can point to and say, "That person did that." Sam Altman makes the same point about momentum: when things stall, people don't want vision speeches—they want small wins [9]. Your first weeks on the executive team work the same way. Credibility compounds from visible results, not from how many coffees you drank.

Ask the CEO directly: What is the one thing you'd love to see resolved in my first two weeks? Then do that thing. Hand yourself the win on a silver platter if you have to [8]. Everything else—the org redesign, the strategic pivot, the vendor renegotiation—can wait until you've earned the right to propose it.

Map the Decision Architecture

Every executive team has a visible decision process and a shadow one. The visible one lives in the Monday morning meeting agenda. The shadow one lives in the CEO's Thursday evening call with the COO, or in the Slack DM between the CTO and the head of product. Your job in the first 30 days is to figure out both.

Start by asking each peer a version of this question: "Walk me through the last big decision this team made that you disagreed with—and how it landed." The answers will reveal who holds veto power, who gets consulted as a courtesy, and which topics are considered settled before they reach the table. New executives who skip this step end up lobbying the wrong person or raising an issue in the wrong forum, and both mistakes are expensive [1].

If you were promoted from inside the company, this step is even more critical. Your former peers saw you in a different role. The power dynamics you understood as a VP don't translate directly. You need to re-map the room as if you're new, because from the executive team's perspective, you are [1].

Build Relationships Before You Need Them

Reaching out to peers only when you need something—budget approval, headcount, a joint initiative—marks you as transactional. The relationships that matter on an executive team are the ones built in the weeks when you don't need anything at all [4].

Send a short note to each direct peer within your first week. Not a formal introduction deck—a two-line message: "I'd like to understand what's on your plate and where my team can help yours. Can we grab 30 minutes?" Go several levels down, too. The directors and senior managers who report to your peers are the ones who'll tell you how cross-functional work happens in practice [4]. Connect with the people your teammates reference most often. If the head of engineering keeps mentioning a particular product manager, get on that person's calendar.

For those who joined from outside the company, the CEO should be actively facilitating these connections—setting up meetings, identifying stakeholders, and debriefing you on how interactions went [2]. If the CEO isn't doing that, ask for it explicitly. Say: "I'd like a weekly 15-minute check-in for my first 60 days where I can run interactions by you." That's not weakness. That's using the resource you have.

Narrow Your Agenda to Three Things

Ambitious new executives show up with eight priorities. Horowitz and Ghodsi both describe this pattern: the eager hire who wants to fix everything simultaneously and ends up fixing nothing [8]. The discipline is subtraction. Within your first two weeks, write down the three outcomes that matter most in your first 90 days. Share them with the CEO. Share them with your peers. Then ignore everything that isn't on that list until the list changes.

Eynat Guez describes a similar discipline from the scaling side—challenging every process, every assumption, but doing it sequentially rather than in parallel [10]. The executives who succeed at scale are the ones who bring in senior people capable of teaching the organization how to grow, then focus those people on one frontier at a time.

Your three priorities should pass a simple test: Can someone outside your function verify whether you've achieved them? "Build a world-class marketing team" fails the test. "Ship the Q3 campaign on time and within budget" passes it. Observable outcomes build trust faster than aspirational language.

Re-Establish Team Norms—Don't Inherit Them Silently

Whenever a new member joins the executive team, the team's dynamics shift. The CEO who brought you in likely intended that shift [2]. But if nobody names what's changing, the old norms reassert themselves within weeks and you end up conforming to a culture you were hired to evolve.

Within your first 30 days, ask the CEO to facilitate a conversation—even a brief one—about how the team wants to work together going forward. This isn't a trust fall exercise. It's a practical discussion: How do we handle disagreements in the room versus offline? What does the CEO expect in terms of pre-reads before meetings? When is it acceptable to go directly to a peer's direct report, and when is that a boundary violation? These norms feel small, but violating an unspoken one in month two can cost you six months of trust [2].

If you were an internal promotion, you carry an extra burden here. Your former peers may test whether you've "changed." Your new peers may wonder if you're still loyal to your old team. Name both dynamics early: "I know some of you worked with me when I was running product. I want you to know I'm operating from this seat now, and I'm going to make decisions that reflect that" [1].

Manage Your Energy, Not Just Your Calendar

The first 90 days in a C-suite role are among the most cognitively demanding stretches you'll face. You're processing new information at a rate that doesn't slow down—names, political context, historical decisions, unresolved conflicts. Jane Finkle's research on career transitions highlights something easy to overlook: the people who integrate most effectively aren't the ones who take every meeting—they're the ones who protect time to process what they've learned [7]. Block 30 minutes at the end of each day to write down three things: what you learned, what surprised you, and what you need to follow up on. This habit pays for itself within two weeks.

For introverts especially, the social demands of executive onboarding can drain the energy needed for the strategic work that actually builds credibility. Don't let the meet-and-greet calendar crowd out the thinking time. If you cross paths with senior leaders in informal settings—an elevator, a coffee line—use those moments. A 90-second conversation with the right person can be worth more than a scheduled hour [7].

Where This Breaks

This playbook assumes a CEO who's invested in your success. If the CEO treats integration as HR's problem and doesn't show up for your debrief conversations, you're operating without a safety net [2]. That's survivable, but you need to compensate by finding a peer sponsor—someone on the executive team who'll tell you what you're missing. If no one volunteers for that role, that's a data point about the team's culture worth paying attention to.

The playbook also breaks when you're brought in during a crisis. If the company is in the middle of a layoff, a reorg, or a cash crunch, the luxury of relationship-building shrinks. In those moments, the "one win" advice from Horowitz becomes even more urgent—deliver a result before you try to build a coalition [8]. And if you discover in month two that the role you accepted isn't the role that exists, escalate to the CEO immediately. Don't wait for the 90-day review.

Pick your three priorities by end of week one. Share them with the CEO and two peers before Friday.