Harsha Kotthapalli
← All 34 outputs

Measure and maintain · output 30 of 34

Launch post-mortem: what the launch did, against what was agreed.

Four questions against the number set before ship, the drop located in the funnel and named as one failure, and every change written as an edit to a named document. Facts, not fog, and no blame either.

See the real example ↓Take the free diagnostic →
Launch post-mortemWeek 8
No success number was set before launch, so it cannot be judged against intent.
Found60KeptBroughtPaid
AwarMessConvProdRead
Failure named: message
4 items skipped · 4 changes, each edits a named document
No success number was set before launch, so it cannot be judged against intent.

The full output carries the verdict table, the funnel read, the failure type, the four skipped items and the four changes.

See the full output →

The output at a glance · built on WealthKarma

How it gets made

What goes in

The launch brief
The week 4 to 8 numbers
The skipped checklist items
What buyers said

The target never moves after the fact

What comes out

The retro record

The report

Circulated to everyone named

How long

1day

per launch

30 to 90 days after ship

The output, in full

Built on WealthKarma, a retirement app for Gulf expats. Every count is real and every gap is marked as a gap.

Launch post-mortemWealthKarma consumer beta · week 8 read
The army's four questions plus blameless mechanics, pointed at a launch. 1 launch · 4 items skipped.
01 · The verdict
No success number was set before the beta launched, so it cannot be judged against intent. The most valuable change from this retro is that the next launch gets its number first.
ObjectiveTargetActual
Beta users startedNever set60
Users kept goingNever setUnmeasured
Users paidNever setn/a, no price exists
Verdict: cannot be judged against intent. Baseline: none exists; this was the first launch.
02 · What the numbers did
Found you (community)Started (60)Kept going (unmeasured)Brought someone (unmeasured)Paid (no price)

The drop cannot even be located: everything after 'started' is dark. The WhatsApp community filled the beta; what those 60 did next was never recorded.

03 · The diagnosis
Awareness
Never heard
Message
Heard, didn't start
Conversion
Cared, didn't act
Product
Didn't deliver
Readiness
Poor answer
All 12 recorded losses trace to the buyer never starting, not to a rival winning. The homepage rewrite that would test the message was written months ago and never shipped, so the current message has run unopposed and untested through the whole beta.
04 · Skipped, and what it cost
Pass number agreedThis retro reads history, not performance
Pricing ownedThe paid stage of the funnel cannot exist
Activation moment defined'Kept going' is unmeasurable at week 8
Homepage rewrite shippedThe message was never tested where buyers look
05 · Sustain / improve
Becomes default
WhatsApp community as the beta channel. It produced all 60 users at no spend.
Shipping a beta before the full product. The product is in hands; that part worked.
Each change edits a document
Pass number signed before shipLaunch brief
Pricing gets an owner and a datePackaging & pricing
Activation moment signedOnboarding journey
Homepage copy ships, datedPositioning
06 · The finding
The launch cannot be judged, and that is the finding. Four skipped items decided it before ship day.
07 · What can't be known
A retro without a pre-set number reads history, not performance; nothing above says whether 60 was good.
60 users is a small base. Any week-8 movement inside it is noise until the base grows.
The community filled the beta, but causation between community activity and starting is asserted, not shown, at this scale.

Where it sits

Research

Compete

Position

Message

Launch

Measure

you are here · 30 of 34

Want this for your company

This is one of thirty-four. The diagnostic tells you which ones you're missing.

Take the free diagnostic →Book a call →
← Product funnel metrics

Next in the journey

Trust metrics →