post-launch-retro

Post-Launch Retro

Hard Gate

NO RETRO COMPLETION WITHOUT:

1. Current metric value (exact number + source + date)
2. Comparison to baseline and target
3. Hypothesis outcome: confirmed / refuted / inconclusive
4. What we learned (one sentence)
5. Next action: continue / iterate / rollback / stop
6. Written to products-graph

Process

digraph retro {
    trigger [label="Trigger: /post-launch <feature> <weeks>", shape=box];
    metric [label="Current value provided?\n(number + source + date)", shape=diamond];
    demand_m [label="PROBE: ask for current value", shape=box];
    compare [label="Compare to baseline\nand target", shape=box];
    hyp [label="Hypothesis outcome stated?", shape=diamond];
    demand_h [label="PROBE: confirmed /\nrefuted / inconclusive?", shape=box];
    next [label="Next action stated?", shape=diamond];
    demand_n [label="PROBE: continue / iterate /\nrollback / stop?", shape=box];
    write [label="Write to products-graph", shape=box];
    pass [label="PASS → retro closed", shape=box, style=filled, fillcolor="#ccffcc"];

    trigger -> metric;
    metric -> demand_m [label="no"];
    demand_m -> metric;
    metric -> compare [label="yes"];
    compare -> hyp;
    hyp -> demand_h [label="missing"];
    demand_h -> hyp;
    hyp -> next [label="stated"];
    next -> demand_n [label="missing"];
    demand_n -> next;
    next -> write [label="stated"];
    write -> pass;
}

Checklist

• Feature name and launch date: ___
• Primary metric (must match what was defined at launch): ___
• Baseline at launch: ___
• Target: ___
• Current value: ___ (number + source + date of measurement)
• Hit target? yes / no / partially
• Hypothesis: confirmed / refuted / inconclusive
• What did we learn that we didn't know before: ___
• Next move: continue / iterate / rollback / stop
• → write to products-graph

"Too Early" Protocol

If PM says "too early to retro":

1. Ask: "What's the minimum observation period for this metric to be meaningful?"
2. Ask: "What date should we reschedule the retro to?"
3. Log a reschedule entry with that date — not a skip, not an open item

"No Data" Protocol

If PM says "can't get the data":

• This IS the retro finding: instrumentation failed
• Log: feature launched without measurable outcome; instrumentation gap identified; recommend fix before next feature launch

Red Flags

Thought	Reality
"метрика растёт"	На сколько? От чего? К чему? Нужно число.
"всё хорошо"	Не артефакт. Нужно число + сравнение с target.
"ещё рано"	Назначь дату. Не пропускай без reschedule.
"гипотеза не была сформулирована"	Зафиксируй что узнали — это и есть retro.
"данных нет"	Это и есть вывод: instrumentation failure. Залогируй.

When to Skip

• Feature was rolled back before the retro window (the rollback IS the retro — log it)
• Explicitly: "skip post-launch-retro"