30-60-90 day plan for executives
On this page
- Why this plan runs through the board or CEO, not a line manager
- The 30-60-90 day plan
- A filled example: an invented new CRO
- The listening tour: who to include and what to ask
- What the CEO or board owes
- When the listening tour contradicts the original mandate
- How the 90-day review differs at this level
- Common mistakes
- Adapting the plan by function
- Questions people ask
A 30-60-90 day plan for an executive should be built around a structured listening tour, a written diagnosis presented to the board or CEO, and one deliberately chosen decision by day 90 — not a list of initiatives announced in week one to look decisive.
For the general new-hire version of this template across roles, see the 30-60-90 day plan template for new hires.
Why this plan runs through the board or CEO, not a line manager
Most 30-60-90 plans are owned and reviewed by a direct manager. An executive's plan is different because the accountability sits one level up: a CEO reviewing a new CFO or CRO, or a board reviewing a new CEO. That relationship needs the same discipline as any other manager relationship — a fixed reporting cadence, explicit commitments on both sides — but it is easy to skip because everyone involved is busy and assumes the executive will simply figure it out. The plan below exists to make sure that reporting relationship is deliberate rather than assumed.
The 30-60-90 day plan
30-60-90 day plan — [Name], [title], reporting to [CEO/board]
Start date: [date] Mandate given at hire: [what the org expects this hire to fix or build]
DAYS 1-30 — Structured listening tour. No structural changes announced.
Owns:
- One-on-one conversations with every direct report, key peers, and [N] customers or
frontline stakeholders, using a consistent set of questions across all of them
- A review of the last [N] quarters of relevant data: financials, pipeline, product metrics,
whichever the mandate is about
- A list of decisions already in motion that are on hold, with dates and owners
Produces by day 30:
- A written synthesis of the listening tour: recurring themes, points of disagreement, surprises
- An explicit statement of what will not change yet, shared with the team directly
Board/CEO owes:
- A clear, specific mandate at hire, restated in the first week: what this role exists to fix
- Introductions to the board, key customers, or other stakeholders the executive cannot reach alone
- Cover from pressure to announce changes before the diagnosis is finished
DAYS 31-60 — Present the diagnosis; agree the first moves
Owns:
- Present a written diagnosis to the CEO or board: what the data and the listening tour show
- Agree on one or two first moves, chosen jointly rather than announced unilaterally
- Begin executing the agreed first moves, visibly, on a stated timeline
Produces by day 60:
- A diagnosis document the CEO or board has seen and responded to, not just delivered
- Early evidence on the first moves: a metric moving, a process changed, a relationship repaired
Board/CEO owes:
- A real response to the diagnosis, including disagreement, rather than silent approval
- Decision rights clarified: what the executive can decide alone versus what needs sign-off
- Protection from a second, conflicting mandate arriving mid-quarter from elsewhere in the org
DAYS 61-90 — Own the function's direction for the next period
Owns:
- Present a plan for the function's next two to four quarters, built on the diagnosis
- Make one staffing, structural, or resourcing decision independently within agreed decision rights
- Establish the recurring reporting rhythm this role will keep going forward
Produces by day 90:
- A forward plan reviewed and, where needed, approved by the CEO or board
- A written 90-day self-assessment: what the listening tour got right, what it missed
Review cadence: weekly check-in with the CEO (or board chair for a CEO hire); formal
reviews at day 30, 60 and 90 built around the listening tour, the diagnosis and the first moves.
A filled example: an invented new CRO
Executive: Naomi Reyes, incoming Chief Revenue Officer, mandate to fix a slipping win rate and rising sales rep turnover.
Day 30: held one-on-ones with all 6 sales leaders, 12 individual reps across segments, and 5 recently lost customers; reviewed 4 quarters of pipeline and win-rate data; found that reps consistently cited unclear compensation changes as the top frustration, a theme that had not reached the CEO directly before.
Day 60: presented the diagnosis to the CEO, including the compensation finding; agreed to freeze further compensation changes for two quarters while a revised plan was built, and to fix a specific broken handoff between marketing and sales that had come up in nearly every conversation.
Day 90: presented a two-quarter plan to stabilize compensation and rebuild the lead handoff process; made an independent call to restructure one underperforming sales pod, within the decision rights agreed at day 60; self-assessment noted that the customer conversations had surfaced a product gap the internal conversations alone would have missed.
The listening tour: who to include and what to ask
A listening tour that only includes direct reports produces a diagnosis shaped entirely by the people whose jobs the executive now controls, which is not a neutral sample. Include peers, frontline employees away from leadership, and external stakeholders such as customers or partners where relevant, and ask each of them a consistent, short set of questions: what is working that should not change, what is broken that has not been said out loud, and what would they do first if they had this role. The consistency across conversations, not the individual answers, is what makes the synthesis at day 30 defensible rather than anecdotal.
What the CEO or board owes
| Commitment | What it prevents |
|---|---|
| A specific mandate, restated in week one | The executive guessing what they were actually hired to fix |
| Real engagement with the day-60 diagnosis | An executive discovering months later that their read on the problem was never actually shared |
| Clear decision rights after the diagnosis | Every decision escalating unnecessarily, or the reverse: overreach with no clear mandate |
| Protection from a second, conflicting mandate | The executive caught between two different definitions of success from different stakeholders |
When the listening tour contradicts the original mandate
Executives are often hired against a mandate the board or CEO believed was correct at the time — "fix the sales team," "fix the product roadmap" — and the listening tour sometimes finds that the real problem sits somewhere else entirely. Naming that gap at day 30 or 60 is uncomfortable because it can sound like the executive is deflecting from the job they were hired to do. Bring it forward anyway, with the specific evidence from the data review and the listening tour, and let the CEO or board decide how to respond rather than quietly working the original mandate while privately believing it targets the wrong problem. An executive who executes a mandate they privately think is wrong, without ever raising the disagreement, is not being loyal; they are setting up a failure nobody will be able to explain honestly in a year.
How the 90-day review differs at this level
A line manager's 90-day review checks tasks against a plan. An executive's review should check something harder: whether the diagnosis itself was right, because a wrong diagnosis executed perfectly still fails. Walk through the original mandate, the day-30 listening tour findings, and what changed as a result, and ask directly where the executive's initial read has already needed revising. An executive who cannot name anything they got wrong in the first 90 days is either unusually accurate or, more likely, not being fully honest about the diagnosis process yet.
Common mistakes
The most common mistake is a structural change announced in the first month to demonstrate decisiveness, before the listening tour and data review are complete. It is a common failure precisely because boards and CEOs often expect visible momentum quickly, which pushes new executives toward acting before they understand why things are the way they are. A second mistake is a listening tour that never gets written down, so the diagnosis lives only in the executive's head and cannot be checked, questioned, or handed to a successor if the executive leaves. A third is skipping frontline and external voices in favor of only talking to peers and direct reports, which produces a diagnosis that confirms what leadership already believed rather than surfacing what they were missing.
Adapting the plan by function
- CEO hired by a board: extend the listening tour to include major investors and board members individually, and treat the day-60 diagnosis presentation as a full board meeting, not a single conversation.
- CFO or COO focused on operational fixes: weight the data review more heavily relative to the listening tour, since operational problems often show up clearly in the numbers before anyone names them out loud.
- CMO or CRO in a customer-facing function: make external stakeholder conversations (customers, partners) mandatory, not optional, since internal-only conversations miss how the market actually experiences the company.
- Executive replacing someone who left under difficult circumstances: add an explicit trust-rebuilding goal to the day 1-30 phase, since the listening tour in this situation is also the first real test of whether the organization believes things can improve.
Keep the listening tour synthesis and the diagnosis document in writing, dated, so a later disagreement about what was said or agreed at day 30 or day 60 has a record to check against rather than two people's differing memories of the conversation.
Questions people ask
Should a new executive present a plan to the board at day 90?
Present a diagnosis and a direction, not a fully executed plan. Boards and CEOs are generally more concerned with whether the executive has correctly identified the real problems than with how much has already changed, and a rushed 90-day plan built to look decisive often targets the wrong problem.
Who runs the day 30, 60 and 90 check-ins for a new executive?
The person the executive reports to: the CEO for most C-level roles, or the board directly for a CEO hire. A skip-level style conversation with the executive's own direct reports is a useful addition, but it does not replace the core reporting relationship's check-ins.
How is a listening tour different from just having meetings?
A listening tour has a fixed list of people, a consistent set of questions asked of each of them, and a written synthesis at the end. Ad hoc meetings produce impressions; a structured listening tour produces a diagnosis someone else can check against what the executive later decides.
What is the biggest risk in an executive's first 90 days?
Making a visible, structural change before the diagnosis is actually finished, in order to look decisive early. It is a common failure mode precisely because boards and new bosses often expect visible action, which pushes executives toward changing something before they understand why it was that way in the first place.