First 90 Days as a General Manager: A 30/60/90-Day Plan
A practical first-90-days plan for learning the business, stabilizing priorities, clarifying decisions and building an evidence-led operating rhythm.
Advanced Executive Program in Management & Business Administration develops connected capability across strategy, finance, customers, operations, technology and people. This practical 30/60/90-day plan can be used before enrollment, during executive study or inside an authorized workplace exercise.
New general managers face pressure to act before they understand the business system. The plan balances listening with responsibility: learn the economics and operating reality, stabilize immediate risks, then make a small number of explicit choices.
Transition mandate
What should a newly appointed general manager learn, decide and establish during the first 90 days? Use the tool on this page to produce a staged 30/60/90-day plan with deliverables, evidence and guardrails. Start with a bounded decision, retain the evidence behind every material claim, and distinguish what is known from what is assumed. The tool is designed to improve management preparation and review; it does not replace the authority, specialist judgement or procedures required by an employer.
The cost of acting before diagnosis
The 30/60/90-day plan creates a compact common language for those connections. It does not force every organization into the same answer. Instead, it makes local definitions, evidence, constraints and accountability visible. That is useful when a management team agrees on the goal but disagrees about the route, or when confident recommendations rely on incompatible assumptions.
Three horizons and four proof points
| Element | Management purpose | Minimum evidence |
|---|---|---|
| Mandate | Clarify expected outcomes, authority, constraints and non-negotiable commitments. | A role title does not reveal which decisions the leader actually owns. |
| Business model | Understand customers, value proposition, revenue, cost, cash and critical dependencies. | The first diagnosis should connect commercial and operating evidence. |
| Stakeholder system | Map people whose decisions, knowledge or trust affect delivery. | The map should include customers and frontline roles, not only senior hierarchy. |
| Operational reality | Observe core workflows, exceptions, service failures and capacity constraints. | Direct observation tests whether formal process descriptions match practice. |
| Decision rights | Clarify recurring choices and escalation paths across functions. | Early ambiguity becomes recurring friction if left implicit. |
| Operating cadence | Establish reviews, evidence standards and follow-through routines. | The cadence should serve decisions rather than create additional reporting work. |
1. Mandate
Clarify expected outcomes, authority, constraints and non-negotiable commitments. A role title does not reveal which decisions the leader actually owns.
Review question: What observable evidence would confirm that mandate is working in the selected scope, and who has authority to respond when it is not?
2. Business model
Understand customers, value proposition, revenue, cost, cash and critical dependencies. The first diagnosis should connect commercial and operating evidence.
Review question: What observable evidence would confirm that business model is working in the selected scope, and who has authority to respond when it is not?
3. Stakeholder system
Map people whose decisions, knowledge or trust affect delivery. The map should include customers and frontline roles, not only senior hierarchy.
Review question: What observable evidence would confirm that stakeholder system is working in the selected scope, and who has authority to respond when it is not?
4. Operational reality
Observe core workflows, exceptions, service failures and capacity constraints. Direct observation tests whether formal process descriptions match practice.
Review question: What observable evidence would confirm that operational reality is working in the selected scope, and who has authority to respond when it is not?
5. Decision rights
Clarify recurring choices and escalation paths across functions. Early ambiguity becomes recurring friction if left implicit.
Review question: What observable evidence would confirm that decision rights is working in the selected scope, and who has authority to respond when it is not?
6. Operating cadence
Establish reviews, evidence standards and follow-through routines. The cadence should serve decisions rather than create additional reporting work.
Review question: What observable evidence would confirm that operating cadence is working in the selected scope, and who has authority to respond when it is not?
Days 0–30, 31–60 and 61–90
Step 1: Days 1-10
Confirm mandate, immediate risks, key commitments and access to evidence. The immediate output is a mandate note and risk watchlist.
Step 2: Days 11-30
Interview stakeholders, observe workflows and reconcile the basic economics. The immediate output is a fact base with named uncertainties.
Step 3: Days 31-45
Share a diagnosis and invite challenge from people close to the work. The immediate output is a corrected operating picture.
Step 4: Days 46-60
Select a small number of priorities and stop or defer conflicting work. The immediate output is a focused priority set.
Step 5: Days 61-75
Clarify decision rights, measures, owners and review routines. The immediate output is an operating agreement.
Step 6: Days 76-90
Launch reversible improvements and establish outcome review dates. The immediate output is initial execution evidence.
Step 7: Day 90 review
Compare the mandate, diagnosis, decisions and observed results. The immediate output is a transparent progress review.
Step 8: Beyond day 90
Expand only after the first operating cycle produces evidence. The immediate output is a controlled next-phase plan.
Transition example: inherited service unit
A newly promoted general manager inherits a business unit with strong revenue growth, declining service reliability and tension between sales and operations. The leader must avoid choosing a side before reconciling customer promises, capacity, margin and exception handling.
| Evidence or choice | Current entry | Interpretation | Management response |
|---|---|---|---|
| First 30 days | Map promise-to-delivery flow | Customer commitments and operational constraints | No premature reorganization |
| Days 31-60 | Select service reliability as shared priority | Revenue quality, rework and retention evidence | Stop conflicting local targets |
| Days 61-90 | Pilot acceptance rules and weekly exception review | Lead time, rework, margin and complaints | Use reversible scope |
| Decision-right repair | Name authority for nonstandard commitments | Current approval ambiguity | Publish escalation path |
| Day 90 outcome | Reliability trend improving; margin stable | Four weeks of comparable data | Continue pilot before scale |
Transition traps
- Announcing a transformation before understanding the system.
- Treating stakeholder meetings as evidence by themselves.
- Reorganizing to demonstrate action.
- Creating too many priorities.
- Changing metrics before establishing a baseline.
- Promising results outside the leaders authority.
New-GM questions
Should a general manager wait 90 days to act?
No. Immediate safety, legal, customer or continuity risks require action. The plan discourages broad irreversible change without evidence.
How many priorities should be selected?
Use the smallest number the organization can resource and review coherently. Three to five may be workable, but context determines the limit.
What should be shared with the team?
Share the mandate, evidence, uncertainties, decisions, owners and review dates at a level appropriate to the audience.
How is success measured?
Compare agreed early outcomes and operating evidence with the starting baseline, while distinguishing the leaders contribution from external conditions.
Michael Watkins’ The First 90 Days is an established transition-management reference emphasizing diagnosis, situation-specific strategy, alignment and early wins. This MTF plan uses those broad principles but provides an independently written general-manager artifact with explicit deliverables, evidence and exit criteria. It is not a summary of the book and does not imply endorsement by Harvard Business Review.
The plan must be adapted to local authority, employment law, consultation duties, regulated obligations and the actual business situation. It is not a mandate to evaluate or change individuals outside authorized people processes. Confidential business and employee information belongs in approved systems. The fictional worked example is supplied so learners can practise without exposing workplace data.
An internal sponsor should review the plan at each exit gate and distinguish learning from performance evaluation. A day-30 hypothesis can be wrong without the transition having failed; the relevant test is whether the manager sought credible evidence and adapted responsibly. Conversely, completing a long meeting list is not proof of diagnosis. Keep the original charter, revisions and decision records so the day-90 retrospective can identify what changed and why.
Sponsor-review rhythm
Use a 30-minute weekly sponsor check with a stable agenda: evidence learned, assumption changed, decision required, relationship risk, capacity conflict and promise made. The sponsor should clarify authority and remove cross-organizational barriers without converting the new GM into an executor of an undocumented answer.
At days 30, 60 and 90, review deliverables before narrative. For day 30, open the baseline, maps and risks; for day 60, open the priority, decision-rights and capacity records; for day 90, open the live cadence, outcome evidence and six-month roadmap. Discuss what is absent or weak. A presentation that cannot link to the underlying artifact does not pass an exit gate.
Record sponsor decisions and changes to the original mandate. If the sponsor asks for a new major priority, show which planned work, capacity or deadline changes. If authority remains ambiguous after escalation, narrow the GM’s commitments rather than accepting invisible accountability.
The final review should name three continuing risks, three capabilities the leadership team now owns and one transition practice to stop. This prevents the first-90-days plan from becoming a permanent parallel management system.
If the GM inherits an active incident, regulatory deadline, cash emergency or major customer failure, the normal sequence compresses but does not disappear. Stabilize through the authorized response structure, preserve a minimal decision log and separate emergency authority from permanent governance. Once the immediate exposure is controlled, return to diagnosis and sponsor alignment. Crisis activity can create an illusion of understanding; the post-incident review should identify which facts remain unknown and which temporary controls must be retired.
Relationship portfolio for the new GM
Map relationships by the decisions and outcomes they enable, not by organizational prestige.
| Stakeholder | Shared outcome | Evidence they hold | Commitment inherited | Trust risk | Next useful interaction |
|---|---|---|---|---|---|
| Sponsor | |||||
| Leadership-team member | |||||
| Frontline manager | |||||
| Customer or partner | |||||
| Control / specialist owner |
In the first 30 days, listen for conflicts between formal accountability and practical influence. A person who owns a source system may determine whether a decision can be verified even without senior title. A frontline manager may see a capacity failure before the executive dashboard. A long-standing customer commitment may constrain the apparent freedom of a new strategy.
Do not promise solutions in exchange for access or trust. Record what you heard, what you will verify and when you will respond. Close the loop even when the answer is no. By day 60, convert recurring relationship dependencies into an operating mechanism—decision forum, service agreement, escalation route or data ownership—so progress does not depend on the new GM’s personal intervention. By day 90, identify relationships the leadership team must own without the GM as intermediary.
Balance the relationship portfolio across levels and viewpoints. If every conversation is with senior sponsors, the GM may miss workarounds and customer harm; if every conversation is frontline listening, authority and resource constraints may remain unclear. Sample advocates, sceptics, source owners, implementers and affected customers. Treat disagreement as information to test, not as automatic resistance.
Promise and decision ledger
New general managers inherit promises and create new ones quickly. Maintain a ledger so stakeholder conversations do not become incompatible commitments.
| Date | Promise or decision | Stakeholder | Authority | Resource implication | Evidence / due date | Status |
|---|---|---|---|---|---|---|
| Own / recommend / escalate |
Review the ledger weekly with the sponsor during the first month. If a promise exceeds authority or conflicts with capacity, correct it early and directly. Do not wait until day ninety to disclose that two senior stakeholders were given incompatible expectations. Where an inherited promise lacks a clear owner, identify the accountable executive and the consequence of continuation, renegotiation or withdrawal.
Day-forty-five decision review
At the midpoint, select the five decisions consuming the most attention. For each, ask whether the frame is stable, evidence has improved, authority is clear, implementation capacity exists and a latest responsible date is known. Some decisions should move forward; others should be narrowed, escalated or removed from the transition agenda.
This review prevents diagnostic work from expanding indefinitely. It also detects premature commitments made during the first weeks. If a decision has already become irreversible, record the assumption and monitoring rule rather than pretending it remains open.
Transition-to-routine test
During days seventy-five to ninety, ask another leadership-team member to run the operating review, explain the KPI definitions and follow an escalation without the GM intervening. Observe where the system depends on personal memory or authority. Convert those dependencies into records, delegated rights, training or sponsor decisions.
The transition is mature when the leadership team can execute routine management, raise evidence-based exceptions and challenge assumptions while the GM focuses on integrated choices. If every issue still routes through the new GM, visible activity has replaced organizational capability.
30–60–90 transition plan with exit criteria
A general manager’s first 90 days are not three equal lists of activities. They are a sequence of hypotheses, relationships, decisions and operating artifacts. The plan should be agreed with the manager’s sponsor and adapted to the business situation: start-up, turnaround, accelerated growth, realignment or sustaining success. It must not promise results the new GM cannot responsibly know on day one.
Before day 1: mandate and guardrails
Clarify why the role exists now, the two or three outcomes the sponsor expects, decisions reserved to others and commitments that cannot be reopened. Request current financials, customer segmentation, operating metrics, organization design, risk register, major contracts, strategy, open decisions and change portfolio. Confirm which information is sensitive and where notes may be stored.
Write a one-page transition charter:
Business situation hypothesis:
Sponsor’s required outcomes:
Decisions I own / recommend / must escalate:
Non-negotiable obligations:
Critical relationships:
Known events in the first 90 days:
Evidence available and missing:
Weekly sponsor cadence:
Day-30, day-60 and day-90 review dates:
Days 1–30: diagnose and stabilize
The objective is a defensible baseline, not a new strategy announcement. Meet the direct team individually using common questions: What must not be disrupted? Where do results diverge from the story? Which decision is stalled? Which customer or employee signal is management missing? What should I understand before changing it? Ask for evidence and examples without turning listening into an anonymous accusation channel.
Build four maps. The value map links customers, offers, revenue, cost and contribution. The operating map shows demand, flow, bottlenecks, quality and capacity. The stakeholder map records interests, influence, commitments and trust risks. The decision map identifies recurring forums, authority, escalation and unresolved choices. Reconcile official numbers with frontline experience and customer evidence.
Act immediately only for safety, legal, ethical, severe customer or continuity risks, or where the cost of delay exceeds the cost of acting with limited information. Label other ideas as hypotheses. Avoid reorganizing to demonstrate momentum.
Day-30 deliverables: verified baseline; situation diagnosis with confidence labels; stakeholder and decision-rights maps; top risks; list of promises inherited; two or three bounded stabilization actions; and a decision on what not to change yet.
Exit criteria: the sponsor agrees the situation type; key metric definitions reconcile; the GM can explain the business model and main constraint; required specialists have reviewed critical risks; and the leadership team recognizes the baseline even where it disagrees with interpretation.
Days 31–60: align choices and mobilize
Convert diagnosis into a small set of choices. Define the few outcomes that matter over the next two quarters and the behaviours or operating mechanisms expected to create them. Test options across financial value, customer consequence, operational feasibility, technology, people and risk. Include continuation and stopping work as explicit options.
Resolve decision rights before launching initiatives. For each priority, name the outcome owner, initiative owner, scarce capacity, dependencies, leading signal, lagging outcome, review date and stop or adapt trigger. Retire or defer work that consumes the same constraint without adequate contribution. Agree how information will travel: weekly operating exceptions, monthly integrated review and sponsor escalation.
Use early wins carefully. Choose one or two improvements that matter to stakeholders, reveal the operating system and can be delivered without hiding structural work. A cosmetic win that overloads the team or bypasses controls spends trust rather than earning it.
Day-60 deliverables: agreed priorities and non-priorities; decision-rights record; capacity-tested action portfolio; communication map; leadership-team working agreements; and one early-win plan with evidence and safeguards.
Exit criteria: owners accept deliverables and resources; the portfolio fits the scarce-role capacity; affected stakeholders understand what changes and what does not; unresolved disagreement is escalated; and the sponsor approves the next-phase mandate.
Days 61–90: execute, learn and institutionalize
Move from transition activity into the permanent management system. Start the operating cadence, publish definitions, review prior decisions and require evidence for action closure. Coach the leadership team through the first cycles rather than personally owning every task. Compare early results with the day-30 baseline and distinguish implementation activity, adoption, operational output and business outcome.
Assess organization and capability only after the work and decisions are understood. Where changes are necessary, use authorized people procedures and appropriate professional support. Do not use a generic competency map as a substitute for role analysis, fair assessment or local employment requirements.
At day 75, run a pre-mortem: if the plan disappoints by day 180, what likely failed? Look for missing capacity, weak adoption, incompatible incentives, unreliable measures, sponsor drift and decisions that remain nominally delegated but are repeatedly overridden. Correct the operating design before expanding the initiative list.
Day-90 deliverables: live management cadence; controlled KPI and decision records; first outcome evidence; revised risk and capacity view; talent/capability priorities; six-month roadmap; and a transition retrospective.
Exit criteria: the business no longer depends on the transition plan to coordinate routine management; owners use the cadence; early evidence can change action; the sponsor understands risks and trade-offs; and the GM has a credible six-month agenda rather than an enlarged task list.
Worked plan: inherited service unit
The unit shows 7% revenue growth but contribution margin is four points below plan. Customer renewal is stable, backlog is rising and overtime is concentrated in a specialist queue. On day 10, the GM resists a proposed six-person hiring request because the workload definition includes repeat cases. By day 30, analysis shows two issue categories produce 38% of repeat demand and one reporting definition changed mid-quarter.
The GM stabilizes the queue with temporary cross-training, restores the prior metric definition and authorizes a two-week process test. By day 60, the leadership team selects three priorities: reduce repeat demand, improve forecast accuracy and rebuild specialist coverage. A lower-value office redesign is deferred. Each priority has capacity, owner and review trigger. By day 90, repeat cases decline 16% in the test population without worse resolution quality; the GM scales the change in stages and approves only two targeted hires because the remaining gap is skill-specific.
The early win is useful because it tests diagnosis and improves customer and workforce conditions. It does not prove the whole strategy. The six-month roadmap retains a downside scenario if peak demand exceeds the revised forecast.
Weekly learning log
Record one assumption confirmed, one assumption weakened, one relationship requiring investment, one decision that needs clarity, one promise made, and one item deliberately deferred. Share the relevant parts with the sponsor. The log protects against hindsight and helps the GM detect whether urgency is crowding out diagnosis.
The Advanced Executive Program in Management & Business Administration provides an integrated framework across strategy, finance, customers, operations, technology and people that can support this transition work.