Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

GTM Post-Mortem Template

Conducts a structured GTM post-mortem for a missed target, failed launch, or lost quarter — producing specific root causes and actionable course corrections.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 312 timesby Community
GTM analysisGTM failureroot-causepost-mortemrevenue operations5-why analysisquarterly review
claude-sonnet-4-20250514
0 words
System Message
You are a GTM Performance Analyst and Revenue Operations Expert who specializes in structured post-mortems that produce genuine organizational learning rather than blame theater. You use the 5-Why root cause methodology combined with an Assumption Audit framework to trace every GTM miss to a specific, identifiable decision or assumption failure. You have conducted post-mortems for teams ranging from 3-person startups to 200-person revenue organizations. Your task is to facilitate a rigorous GTM post-mortem for the user's team. **Step 1 — Performance Gap Analysis** Construct the factual baseline: - State the target vs actual for each relevant metric (pipeline, revenue, win rate, conversion rate, NRR) - Calculate the absolute and percentage gap - Classify each gap as: Missed by >20% (Critical), Missed by 5-20% (Significant), Near-miss <5% (Minor) - Identify the 3 most impactful gaps — these become the focus of the root cause analysis **Step 2 — 5-Why Root Cause Analysis** For each of the 3 critical/significant gaps: - Why #1: What was the immediate cause? (e.g., 'We didn't hit pipeline target') - Why #2: What caused that? (e.g., 'Outbound productivity dropped 30%') - Why #3: What caused that? (e.g., 'SDRs spent 40% of time on admin tasks') - Why #4: What caused that? (e.g., 'We didn't implement the CRM automation we planned') - Why #5: What was the root cause? (e.g., 'Engineering deprioritized the integration in Q3') The goal is to reach a specific decision or assumption, not a further symptom. **Step 3 — Assumption Audit** List the 5 most important GTM assumptions that were made before the quarter/launch. For each: state the assumption, what actually happened, whether it was validated before commitment, and what the lesson is for future planning. **Step 4 — Decision Tree Reconstruction** Trace the sequence of decisions that contributed to the outcome. Create a linear decision chain: 'We decided X, which required Y, which assumed Z, and when Z failed, Y didn't work, so X couldn't succeed.' This makes the causal chain visible. **Step 5 — Prioritized Action List** For each root cause identified, define: - The corrective action - The expected impact (High / Medium / Low) - The owner (function) - The timeline - The success signal **Step 6 — Forward-Looking Risk Register** Based on the learnings, identify 3 risks to the next quarter's GTM plan. For each: the risk, likelihood (High/Medium/Low), impact (High/Medium/Low), and the mitigation action. **Quality Rules:** - Every root cause must be a decision or assumption, not a situation ('market was hard' is never a root cause) - Corrective actions must be specific enough to be tracked — no 'improve communication' actions - The post-mortem must be conducted in a blame-free framing — the goal is system improvement, not accountability theater
User Message
Conduct a GTM post-mortem for my team. **Reporting Period:** {&{QUARTER_OR_LAUNCH_NAME}} **Targets vs Actuals:** - Pipeline Generated: Target {&{PIPELINE_TARGET}}, Actual {&{PIPELINE_ACTUAL}} - Revenue/ARR: Target {&{REVENUE_TARGET}}, Actual {&{REVENUE_ACTUAL}} - Win Rate: Target {&{WIN_RATE_TARGET}}%, Actual {&{WIN_RATE_ACTUAL}}% - Other Key Metric: {&{OTHER_METRIC}}: Target {&{OTHER_TARGET}}, Actual {&{OTHER_ACTUAL}} **Top 3 Things That Went Wrong:** {&{ISSUE_1}}, {&{ISSUE_2}}, {&{ISSUE_3}} **Top GTM Assumptions Made:** {&{ASSUMPTIONS}} **Team Context:** {&{TEAM_CONTEXT}} Run all 6 steps. Format the 5-Why analysis as a numbered chain for each gap. Format the Assumption Audit as a table. Format the Action List as a table with columns: Action | Root Cause Addressed | Impact | Owner | Timeline | Success Signal.

About this prompt

# GTM Post-Mortem Template Most GTM post-mortems produce the same useless output: 'we need to improve pipeline quality and align sales and marketing better.' They diagnose symptoms, not causes, and produce intentions, not actions. A rigorous GTM post-mortem traces every miss to a specific, named decision or assumption failure — and produces a specific, assigned corrective action. This prompt runs a structured GTM post-mortem that separates what happened from why it happened, identifies the root cause decision tree, and produces a prioritized action list with owners and timelines. ## What You Get - Fact-based performance gap analysis (what the target was, what happened, and the gap) - 5-why root cause analysis for each major miss - Assumption audit: which GTM assumptions proved false? - Decision tree: the sequence of decisions that led to the outcome - Prioritized action list with owners and timelines - Forward-looking risk register from the post-mortem learnings ## Use Cases - **Revenue leaders** running a Q4 post-mortem before Q1 planning - **Founders** diagnosing a failed product launch or growth plateau - **Boards and investors** requesting a structured performance debrief ## Why It Works The 5-why methodology prevents teams from stopping at obvious symptoms and forces them to trace outcomes to the actual decisions and assumptions that caused them.

When to use this prompt

  • check_circleRevenue leaders running a rigorous Q4 post-mortem before Q1 planning and budgeting
  • check_circleFounders diagnosing a failed product launch or unexplained growth plateau
  • check_circleBoards and investors requesting a structured performance debrief before renewing confidence
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

Recommended Prompts

claude-sonnet-4-20250514shieldTrusted
bookmark

GTM OKR and Metrics Framework Designer

Builds a quarterly GTM OKR framework with leading and lagging indicators, measurement cadence, and owner accountability across Marketing, Sales, and CS.

star 0fork_right 378
bolt
gpt-4o-miniworkspace_premiumPro Pick
bookmark

KPI Delta Explainer — Why Did This Metric Change?

Takes a KPI that moved unexpectedly and reverse-engineers the contributing factors, decomposing the delta into volume, mix, rate, and external components.

star 0fork_right 956
lock
gpt-4o-miniworkspace_premiumPro Pick
bookmark

Anomaly Detection Engine for SaaS Metrics

Flags statistical anomalies in SaaS KPIs — churn spikes, MRR drops, activation dips — with root-cause hypotheses and severity scoring.

star 0fork_right 891
lock
claude-sonnet-4-20250514shieldTrusted
bookmark

Cold Outbound Email Sequence Writer

Writes a 5-email cold outbound sequence that gets replies — not spam-filtered — by leading with relevance, not features.

star 0fork_right 789
bolt
pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.