Two-Day Program: New General Manager Transition

Design Philosophy

New GMs typically fail not from lack of intelligence but from three specific gaps: they over-rely on functional expertise (managing what they know instead of the whole business), they resolve ambiguity too quickly by imposing false clarity, and they replicate the operating rhythm of their previous role rather than building one suited to end-to-end ownership. The program should be built around simulation and peer challenge, not lecture.

Day 1: From Function to Whole-Business Ownership

Module 1: The GM Transition (90 min)

Teach: The specific cognitive shift from optimizing a function to arbitrating tradeoffs across functions. Use the "portfolio of tensions" frame — growth vs. margin, speed vs. quality, today's P&L vs. tomorrow's capability.

Why: Most new GMs come from Sales, Ops, or Product and unconsciously over-index on their home function. Naming this bias explicitly is the fastest way to interrupt it.

Method: Have participants map where they'll be tempted to over-invest based on their background, publicly, in small groups.

Module 2: Priority-Setting Under Constraint (2 hrs)

Teach: A forced-ranking method for choosing 3-5 priorities max, with explicit criteria (value creation, urgency, reversibility, signal to organization). Emphasize that a priority list is a resource-allocation decision, not an aspiration list.

Why: New GMs typically inherit 15 "priorities" from predecessors, boards, and functional heads. Failure to compress this list is the single most common early mistake — it signals to the org that everything matters equally, which means nothing does.

Method: Case study (actual, anonymized) of a business with too many priorities. Participants must cut to 3 and defend the cuts to a skeptical "board" role-played by faculty.

Module 3: Reading a Business You Didn't Build (90 min)

Teach: How to diagnose a business fast — unit economics, customer concentration, talent bench strength, cultural signals — without waiting for 100 days of data.

Why: Ambiguity in the GM role is often not lack of information but excess, poorly triangulated information. Teach a structured diagnostic (e.g., "three lenses: numbers, people, customers") so they don't freeze or over-analyze.

Method: Give participants a data-rich but ambiguous business dossier overnight; they present a diagnosis the next morning.

Day 2: Operating in Ambiguity, Building Cadence

Module 4: Decision-Making with Incomplete Information (2 hrs)

Teach: Distinguish between reversible and irreversible decisions; teach "good enough" decision speed for the former and disciplined escalation/testing for the latter. Introduce pre-mortems and disconfirming-evidence habits.

Why: New GMs either freeze (seeking certainty that won't come) or act too fast on high-stakes irreversible calls out of anxiety to "show leadership." Both are costly. The skill is calibrating decision speed to reversibility and stakes — not applying one style universally.

Method: Live simulation — a crisis unfolds over the module (e.g., key customer threatens to leave, key exec resigns) with new information injected every 20 minutes. Debrief on how their decision speed and confidence shifted.

Module 5: Designing Your Operating Cadence (2 hrs)

Teach: How to build a rhythm of reviews (weekly ops, monthly financial, quarterly strategy), meeting design (who, what decision, what prep), and information flow that fits this business — not a copy of what they experienced as a direct report.

Why: Many new GMs default to the cadence their old boss used, which was designed for a different business context and different span of control. A mismatched cadence causes either micromanagement or blind spots.

Method: Participants design an actual cadence calendar for their actual business, peer-reviewed by two other GMs for gaps ("What would surprise you that this cadence wouldn't catch?").

Module 6: The First 90 Days — Signal and Symbolism (90 min)

Teach: Every early action (who you meet first, what you ask in reviews, what you tolerate or don't) is read as signal by the organization, disproportionate to intent. Teach deliberate use of symbolic actions to reinforce priorities.

Why: New GMs underestimate how much they're being watched and over-communicate through unconscious signals (e.g., who they copy on email, what they ask about in a walkthrough).

Method: Have participants script their first two weeks — first meetings, first questions, first visible decisions — then have peers "reverse-engineer" what message that sequence sends.

Closing Module: Personal Operating Philosophy (60 min)

Teach: Nothing new — have each participant write a one-page personal operating philosophy: their non-negotiables, their default decision rules, how they'll know if they're wrong.

Why: Retention requires synthesis into something the GM owns, not a program takeaway. This is also a commitment device — sharing it aloud increases follow-through.

Faculty Composition (deliberate choice)

• A former multi-business-unit CEO to teach cadence and portfolio tradeoffs — credibility only comes from someone who's lived the ambiguity.
• A behavioral/decision scientist for Module 4 — reversibility and decision speed need a rigorous framework, not just war stories.
• A sitting or recent GM from the same industry as a case-teaching partner — participants trust "this happened to someone like me" more than abstract theory.
• Peer small-group facilitators (not faculty) for debriefs — GMs learn as much from each other's actual dilemmas as from experts.

What to Deliberately Avoid

• Too much framework, too little simulation — GMs already know frameworks; they need practiced judgment under time pressure.
• Case studies with clean answers — ambiguity training fails if every case resolves neatly by 5pm.
• Letting participants keep their functional lens as a safety blanket — faculty should push back hard when someone reverts to functional depth instead of GM-level tradeoffs.