Skip to main content

New Product Launch Planning

You have a product or feature that's ready to ship. The build is done. Now comes the equally complex work of getting it into the market in a way that actually generates the outcome you intended. Most launches fail not because the product is bad, but because the go-to-market planning treated launch as a single event rather than a system β€” and didn't account for the things that go wrong, the second-order effects of the choices made, or the gaps in the plan that only become visible when you look for them explicitly.

The Framework β€” Step by Step​

Step 1: Run a Pre-mortem to Surface Every Failure Mode​

How to apply it:

  1. Gather the full cross-functional launch team. Announce: "It's six weeks after launch. The numbers are bad β€” below any acceptable threshold. We're here to understand why." Give everyone 5 minutes to write independently.
  2. Collect every reason β€” from the trivial to the existential. Common ones that surface: onboarding was too complex, the announcement hit during a news cycle that buried it, the pricing confused the ICP, the sales team wasn't trained, the integration required by power users was missing, negative reviews appeared before positive ones established credibility.
  3. For each failure mode, assess: (a) probability, (b) impact if it occurs, (c) whether it's within your control to mitigate. Build a risk matrix. Address every high-probability, high-impact, controllable risk before launch.

The key question: Which failure modes are both likely and preventable β€” and are we actually preventing them?

Step 2: Apply Second Order Thinking to Your Go-to-Market Decisions​

Why this model fits: Every launch decision has a first-order effect (the intended outcome) and second-order effects (what happens as a consequence of the first-order effect). Most launch failures are second-order failures.

How to apply it:

For each major launch decision, trace the consequences two levels deep:

  • Launch to existing customers first β†’ First order: build social proof, get real usage data β†’ Second order: if there are bugs, they hit your most loyal users first; if feedback is negative, it's amplified by your most engaged advocates. Is that acceptable?
  • Price aggressively low to drive adoption β†’ First order: higher volume β†’ Second order: attracts price-sensitive users with high churn, anchors market expectations at the low price, signals low value to enterprise buyers. Is that acceptable?
  • Press announcement on Day 1 β†’ First order: coverage and awareness β†’ Second order: if the product isn't ready for prime time, the press cycle creates comparison to an incomplete experience. What's the timing that produces the best second-order outcome?

The key question: If this decision works exactly as intended, what happens next β€” and is that something we want?

Step 3: Use MECE to Validate the Launch Plan Is Complete​

How to apply it:

  1. Break your launch plan into its major work streams. The MECE check asks: are these streams mutually exclusive (no overlap that creates duplication or confusion) and collectively exhaustive (no domain missing)?
  2. Standard launch work streams: Product readiness (is it actually working?), Go-to-market (who are we reaching, how, with what message?), Sales enablement (does the team know how to sell/support it?), Success and support (can we onboard and retain new users?), Measurement (do we know what success looks like, and can we measure it?).
  3. For each stream, identify the owner, the definition of done, and the interdependencies with other streams. Launches fail most often at the interdependencies β€” not in any single stream.
  4. Run the exhaustiveness check: is there any stakeholder, user segment, or risk category not covered by any stream? That gap is where the launch will break.

The key question: Is there any dimension of this launch that no one on the team owns β€” and therefore no one will catch if it breaks?

Full Workflow​

Product Launch Planning β€” Framework

Step 1: Pre-mortem  ────────────  Output: Prioritized risk matrix + mitigation plan
          ↓
Step 2: Second Order Thinking  ─  Output: Consequence-traced GTM decisions
          ↓
Step 3: MECE Plan Audit  ───────  Output: Complete, owned launch plan with no gaps

Worked Example​

A product team at a B2B analytics company is launching a new AI-generated insights feature. Launch is in three weeks.

Pre-mortem: The team surfaces 14 failure modes. The two highest-probability, high-impact ones: (1) enterprise customers are concerned about data residency for AI-processed data β€” no one has addressed this in the messaging or legal docs; (2) the feature is opt-in, but the onboarding flow doesn't make it discoverable β€” most users will never know it exists. Both are fixed in the three weeks before launch.

Second Order Thinking: The team is planning a Product Hunt launch for visibility. First order: traffic and signups. Second order: Product Hunt users are predominantly individual developers; the company's ICP is enterprise procurement teams. A successful Product Hunt launch may generate noise that crowds out the targeted enterprise outreach. Decision: delay the Product Hunt launch by 4 weeks, run enterprise-specific outreach first.

MECE Audit: The plan has strong streams for product, marketing, and engineering. Two gaps identified: (1) no stream owns sales enablement β€” AEs haven't been trained; (2) no measurement stream β€” there's no defined success metric or data pipeline to track feature adoption. Both are added before launch.

Common Mistakes​

Treating launch as a single day rather than a 6-week arc. Launch is a pre-launch phase (preparation and enablement), a launch moment (announcement), and a post-launch phase (iteration and amplification). All three need plans.

Optimizing for launch day metrics rather than 30-day retention. Spike-and-drop launches look good in launch recaps and produce nothing durable. The OMTM (One Metric That Matters) should measure sustained adoption, not initial curiosity.

Apply This Framework with AI​

Describe your product, target users, and launch timeline in MindMax. The AI will run a pre-mortem, trace the second-order consequences of your key GTM decisions, and audit your plan for completeness.

πŸš€ Plan your launch in MindMax β†’

This page is part of the MindMax Mental Models Knowledge Base.