examples/acme-fitness/okrs/2026-Q3.md

---
cycle: 2026-Q3
start: 2026-07-01
end: 2026-09-30
status: active
---

# O1: Studios that try Acme stay — trials convert and members show up
DRI: maya

## KR1.1: Trial-to-paid conversion from 22% to 35%
Type: aspirational
DRI: maya
Confidence: 0.6
Score: —
Notes: Baseline is the trailing six-month average (Stripe + the trials sheet). Volume push —
quality pair is support ticket volume (health table): converting studios we then drown
doesn't count.

## KR1.2: Median studio onboarding time (signup to first member-booked class) from 9 days to 3 days
Status: dropped — 2026-09-03 — confidence under 0.5 at two consecutive check-ins forced a
named decision; call was kill. The onboarding rebuild lost its capacity to the payments GA
and the W34 emergency. Decision logged in ../checkins/2026-Q3/2026-W36.md. Id stays frozen;
no renumbering.
Type: aspirational
DRI: priya
Confidence: 0.35
Score: —
Notes: Speed push — quality pair was support ticket volume. The scripted onboarding-call
playbook survives (holds the median around 6 days when priya drives); the product rebuild
rolls to Q4 planning as a candidate.

## KR1.3: Member no-show rate from 14.2% to 10.6%
Type: aspirational
DRI: priya
Confidence: 0.7
Score: —
Revised: 2026-08-13 — baseline established; numeric target locked per the instrumentation
pairing. Original text: "Member no-show rate from baseline: unknown to 25% below baseline.
Pairing: no-show tracking ships by 2026-07-24 (jordan); baseline = first three full weeks of
data; target locked by revision once it lands." Tracking shipped 2026-07-15; the weeks of
Jul 20 – Aug 9 put the baseline at 14.2%, so the target locks at 10.6%. (PR #57)
Notes: Planned with `baseline: unknown` — allowed because it shipped with the instrumentation
pairing preserved above. Main lever is reminder nudges; quality pair is member notification
unsubscribe rate (health table) — a no-show number bought with reminder spam is a loss.

# O2: Studios run their money through Acme, not around it
DRI: jordan

## KR2.1: Class-pack payments live for every studio by 2026-08-15
Type: committed
DRI: jordan
Confidence: 1.0
Score: —
Notes: Milestone KR — anchors set at planning: 0.3 = live behind a flag for three pilot
studios; 0.7 = live for all studios inside the cycle but after 2026-08-15; 1.0 = live for
all studios by 2026-08-15. Launch KR, so it's paired with KR2.2: shipping counts for nothing
if studios don't run money through it. Quality pair: checkout error rate (health table).
Committed — a miss requires a root-cause note at retro. GA'd 2026-08-14.

## KR2.2: Active studios that have processed at least one class-pack payment, from 0% to 40%
Type: aspirational
DRI: maya
Confidence: 0.6
Score: —
Notes: The usage pair for KR2.1. "Active" = at least one member booking in the trailing 30
days. Volume push — quality pairs are checkout error rate and support ticket volume (health
table).

## Health metrics (monitored, not targeted)
| Metric | Red line | Source |
|--------|----------|--------|
| Support ticket volume | >25/wk | Front inbox report |
| Checkout error rate | >1.5% of payment attempts | Stripe dashboard + PostHog |
| Member notification unsubscribe rate | >2%/wk | PostHog |