Manager Action Plan Template: First 90 Days, Quarterly Cadence
A manager action plan covers two distinct phases: the first 90 days in role, when the priorities are listening and earning trust, and the steady quarterly cadence after that, when the priorities shift to producing team outcomes against company strategy. Most templates address only one of the two and leave new managers to figure out the transition. This page covers both, with the cascading-goals framework that ties the manager's plan to company OKRs above and team execution below, a worked example for a new engineering manager inheriting a team of eight, and the trap most new managers fall into around week six.
Updated 11 May 2026
What Makes a Manager Plan Different
Individual contributor plans track the IC's personal output. Manager plans track team output, with the manager's personal commitments serving as the inputs that produce that team output. This dual nature has to be visible in the plan, because the failure mode of treating a manager plan like an IC plan is well documented: the manager defaults to doing IC work, the team underperforms, and the manager's calendar fills with crisis management instead of leadership.
The Harvard Business Review's research on the leader as coach documents how the manager's leverage is in the team's capability, not in the manager's individual output. The plan that reflects this is structured around team commitments first, with the manager's own activities serving them rather than competing with them. New managers especially struggle with this inversion because their entire previous experience optimised for personal output.
The right template separates three layers: company strategy (the OKRs the team's work advances), team commitments (what the team will ship this quarter), and manager activities (one-on-ones, decisions, escalations, capability building). Each layer informs the others. Company strategy shapes team commitments. Team commitments shape what the manager prioritises in their own week. Manager activities are the daily work that makes the team commitments achievable.
First 90 Days vs Steady Quarterly Cadence
First 90 Days
The first 90 days follow a Learn / Contribute / Lead pattern. Days 1-30 are for understanding the team's current state, the strengths and gaps, the political landscape, and the urgent versus important distinction. Days 31-60 are for shipping the first one or two meaningful changes, demonstrating that the manager will act on what they learn. Days 61-90 are for setting the team's first full-quarter rhythm under the new manager.
See the 30-60-90 day plan template for the detailed first-90-days structure with worked examples for new manager, sales rep, and business initiative scenarios.
Steady Quarterly Cadence
After day 90, the cadence settles into a quarterly rhythm. Each quarter, the manager defines two to four team goals tied to company OKRs, runs a weekly tactical review with the team, holds a one-on-one with each direct report every two weeks, and conducts a quarterly retro that feeds into the next quarter's plan.
The shift from first-90-days to steady cadence often gets missed. The new-manager rhythm is intense and visible; the steady cadence is quieter and easy to let drift. Managers who do not consciously redesign the cadence at day 90 often replicate the new-manager intensity for months longer than necessary, which exhausts both them and the team.
Worked Example: New Engineering Manager, Team of 8
Role: New Engineering Manager, inheriting team of 8 engineers from a manager who left the company. Team is shipping but morale is mixed and architectural debt is significant.
First 90-day outcome: Establish trust with all 8 engineers, deliver one meaningful process improvement, and set the team up for a clean Q3 OKR cycle.
| Phase | Manager Activity | Team Outcome | Day Target |
|---|---|---|---|
| Days 1-30 | First 1:1s with all 8 engineers (45 min each) | Team feels heard, manager understands gaps | Day 14 |
| Days 1-30 | Shadow 3 of the team's key recurring meetings | Manager learns rituals, decision norms | Day 21 |
| Days 1-30 | Skip-level meeting with each direct's senior peers | Manager sees the team from outside their bubble | Day 28 |
| Days 1-30 | Write one-page situational assessment | Team and skip-level have a shared baseline | Day 30 |
| Days 31-60 | Pick the one process change worth shipping | Team sees manager will act on what they learned | Day 35 |
| Days 31-60 | Weekly 1:1 cadence locked in for all 8 engineers | Team has predictable manager attention | Day 45 |
| Days 31-60 | Architectural debt audit run with team's senior engineer | Team has a shared backlog of debt with priority | Day 55 |
| Days 31-60 | Mid-point check with skip-level on what is working and what is not | Manager calibrates with own boss before quarter close | Day 60 |
| Days 61-90 | Define Q3 OKRs with team, tied to company OKRs | Team enters Q3 with a clear committed plan | Day 75 |
| Days 61-90 | First retro on first 90 days, captured for personal learning file | Manager codifies what worked and what did not | Day 85 |
| Days 61-90 | Day-90 review with skip-level on whether the manager is on track | Manager and skip-level are calibrated for steady-state | Day 90 |
| Days 61-90 | Promote one team member to tech lead role on debt initiative | Team member grows, manager builds capability rather than doing | Day 88 |
The structure makes the dual nature of the manager's work visible. The manager activity column is what the manager personally does; the team outcome column is what changes about the team as a result. Each phase has its own emphasis: Days 1-30 is heavy on listening, Days 31-60 introduces the first action, Days 61-90 ramps the team's autonomy and seeds the next quarter's work.
The Cascading-Goals Framework
Manager goals cascade in three layers. At the top sits company strategy, expressed as OKRs or strategic priorities, owned by the executive team. In the middle sit team commitments, owned by the manager, that translate company strategy into what the team will ship this quarter. At the bottom sit individual goals, owned by each team member, that define their personal contribution to the team commitments. Each layer should be traceable to the layer above it.
The trap is treating the layers as independent. When a team commits to a quarterly goal that does not visibly advance any company OKR, the work is at high risk of being deprioritised mid-quarter when other things compete for attention. When an individual goal does not visibly support a team commitment, the team member is at high risk of being seen as off-strategy. The cascading link is what makes prioritisation conversations cheap; without it, every priority change becomes a political negotiation.
Practical mechanic: at the top of every team OKR document, name the company OKR it advances. At the top of every individual OKR document, name the team commitment it supports. Two minutes of cross-referencing during planning saves hours of confusion mid-quarter. Asana's guide to cascading goals covers the same pattern with practical examples.
5 Mistakes New Managers Make in Their Action Plans
Shipping changes in week 2
The new manager arrives, sees an obvious problem, and tries to fix it before they understand why it exists. The team interprets the change as the new manager not respecting prior work, and the manager learns three weeks later that the problem they fixed had a reason. Wait until at least day 21 before any non-trivial change. Listening is not procrastination; it is the work.
Doing IC work to feel productive
By week 6, the manager has learned enough about the team's gaps to feel responsible for filling them. They start writing code, drafting PRDs, or doing analyst work. This feels productive because it is familiar, but it is the wrong work. Delegate even when the team will do it less well; the short-term quality cost buys long-term capability.
Skipping 1:1s when the calendar gets busy
Weekly or bi-weekly 1:1s with each direct report are the highest-leverage activity in the manager's calendar. When other priorities arrive, 1:1s are the easiest thing to push, and that is exactly why they should be locked in. Cancelled 1:1s send the signal that the team member is lower priority than the urgent thing that displaced them.
No skip-level relationship with own boss
New managers often default to giving their boss only the good news because they want to appear competent. This backfires when the boss eventually learns about problems they could have helped with at lower cost. The right rhythm is a regular short briefing where the manager surfaces what is working, what is not, and where they need help. Bosses much prefer early problems to late surprises.
No personal learning file
The first quarter as a manager produces lessons that can otherwise compound across an entire career. The manager who captures those lessons in a private file (a journal, a one-pager per quarter, a running notes doc) compounds learning. The manager who does not, keeps relearning the same lesson. This is the cheapest, highest-return habit in management and the most commonly skipped.
Frequently Asked Questions
What should a new manager focus on in the first 30 days?▾
How does a manager action plan differ from an individual action plan?▾
How often should a manager review and update their action plan?▾
Should a manager share their action plan with the team?▾
What is the trap most new managers fall into around week 6?▾
How do manager goals connect to company OKRs?▾
Related Templates
30-60-90 Day Plan: New Manager
Detailed first-90-days plan for newly-appointed managers.
Employee Action Plan Template
What direct reports use under a manager plan.
Executive Action Plan Template
C-suite quarterly cadence one level above manager.
Team Action Plan Template
Multi-person plan with role assignments.
Employee Performance Plans
PIPs and development plans for direct reports.
Download Free Templates
Excel, Word, and PDF formats.