Mini‑Feature Postmortem & Launch Report: One‑Page Template + Checklist

Large launch retrospectives are useful, but they’re heavy. Mini features need a lightweight artifact you can produce within 48 hours of launch so insights are still fresh and the team can act. A one‑page postmortem focuses on the minimum signals that tell you whether the feature created value, created noise, or introduced risk.

This format also forces discipline: write a single sentence for outcome, two short telemetry queries that prove or disprove the outcome, one PQL definition (if relevant), and three follow‑up experiments. That keeps the artifact actionable and re-usable for other launches.

Use this as a fillable card in your docs or issue tracker. Keep answers short — one line or a concise bullet each. The sections map to what teams actually need to act: Outcome, Baseline & Target, Telemetry Queries, PQL Signal, Acceptance‑Test Gaps, and Three Follow‑Ups.

Below is the exact structure to paste into your template. You can keep it in a single doc or wire it as a lightweight form in Product Ops tools.

Don’t track dozens of vanity metrics. Choose two queries: one that measures exposure and basic usage (impressions, CTR, unique users who triggered the feature) and one that measures value (repeat usage, task completion, conversion to paid or upgrade). These map to Search Console concepts for impressions/clicks when tracking feature cards on marketing pages, and to product analytics for in‑app usage.

Example queries: 1) Exposure: distinct users with feature flag 'on' who saw the feature card this week; 2) Value: percentage of those users who completed the target action within 14 days. Make queries shareable (saved dashboards) and timestamp them so future teams can compare apples to apples.

Mini features rarely drive full sales cycles, but they can create micro‑PQLs: lightweight signals that a user got value and is likely to expand or convert. Define a single, easy‑to‑compute PQL rule tied to the feature (example: "user performs FeatureX + core activation step within 7 days"). Keep thresholds conservative to avoid noise.

Operationalize the PQL: add it to lead routing, a CRM tag, or an automated Slack alert for growth. Track both quantity (how many PQLs) and quality (conversion rate from PQL to demo/upgrade) in a short horizon (30–90 days) so you can judge whether the mini feature contributed real pipeline.

Mini features often ship with incomplete test coverage or missing monitoring. Use the postmortem to capture specific acceptance gaps (e.g., no regression test for edge case X, no error metric on background job). Those are high‑value, low‑effort fixes you can prioritize immediately.

Also add runbook items: what dashboard to watch for the first 72 hours, which logs to tail, and the rollback criteria. Those operational bits are what prevent small regressions from becoming support escalations or product trust issues.