Skip to content
ProductOS ProductOS ProductOS

Release Record Template

One record per release, per phase. Copy it, fill it in, link it from the walkthrough invite. The measures come from the Job Spec; do not restate them, link them. For a Full Spec release the RFC’s Rollout table says what each phase’s audience and exit criteria are; this record says whether they were met.

Release: [name] Phase: Private Preview / Public Preview / GA Path: Quick Win / Lightweight / Full Spec Launch owner: [PM, or Tech Lead where there is no PM] Job Spec: [link] · RFC or brief: [link] Approver: [Head of Product, or the delegated PM + Tech Lead]

Why this phase, and why now

Section titled “Why this phase, and why now”

[One or two lines. Material or small, and which question this phase answers: holds up / solves the problem / will they pay / can the business carry it.]

Measures

Section titled “Measures”

Linked, not restated. If a line here is not in the Job Spec, fix the Job Spec.

  • Job to be done: [link to the Job Spec’s job statement]
  • Working looks like: [leading indicator] from [baseline] to [target] by [DD/MM/YYYY]. Signal: [name].
  • Not working looks like: [guardrail] crosses [threshold], or the abandon signal: [from the Job Spec]. Then we: [hold / pull / talk to every account].
  • Dashboard: [link]

Pricing hypothesis

Section titled “Pricing hypothesis”
  • Price point: [e.g. per seat per month]
  • Metric and model: [per seat / per site / per transaction / bundled]
  • Who pays: [role at the customer]
  • Evidence so far: [usage, willingness to pay, won and lost conversations]

Launch Readiness Check

Section titled “Launch Readiness Check”

Tick, link evidence, or write N/A and why. Lines from Gates and Approvals.

It works

  • Customer path walked (outcome UAT) · evidence:
  • Tests and regressions green · evidence:
  • Kill switch tested (rollback proven) · evidence:

We will know what happened

  • Measures live, baseline running · dashboard:
  • Monitoring owner named · who / until:

The business is ready

  • Support briefed and ready · who said yes:
  • Sales has seen it and can sell it · who said yes:
  • Marketing ready, or not needed · date / “no launch”:
  • Value and price validated · evidence:

Scaled to the stakes

  • Production-readiness validated · evidence:
  • Product principles check · notes:
  • [other lines from the gate, as the stakes demand]

Signed off

  • Walkthrough and approval · date / yes in writing:

Switched on

Section titled “Switched on”
  • Audience: [named accounts / opt-in cohort / everyone]
  • On: DD/MM/YYYY
  • Preview label showing: [product / docs / opt-in screen] (n/a at GA)
  • Two-week read booked for: DD/MM/YYYY

Two-week read (DD/MM/YYYY)

Section titled “Two-week read (DD/MM/YYYY)”
  • Working metric: [actual vs target]
  • Not-working signal: [hit / not hit]
  • Pricing call: Right / Over / Under · because:
  • Call: Fired / Partial / Missed / Unscoreable · because:
  • Decision: Widen / Hold / Pull · owner:

After GA, the 30-day and 90-day reviews run from the Post-Launch Review Template.

Section titled “Related”