Intake & fit check
You send release notes, rollout plan, and analytics access constraints. We confirm whether the question is measurable and whether the calendar allows a fair window. If the answer is no, we say so before any deposit.
Measurement process
From intake to a decision-ready brief
This page shows how Release Canvas Hub runs release impact measurement after version updates. Use it to brief stakeholders before you request an assessment or browse available engagements.
Baseline lock
Together we name the prior stable version, the observation dates, and up to four impact metrics tied to the change. Thresholds are written in plain language — what would force a pause versus a watch-and-wait.
Observation
During the window we track adoption, agreed reliability and behaviour signals, and known confounders (campaigns, holidays, incomplete upgrade share). Staged engagements add gate-by-gate notes.
Analysis & brief
Findings are version-aware. We separate upgraders from non-upgraders, call out weak instrumentation, and avoid composite scores that hide trade-offs.
Readout & next step
A 90-minute session (or facilitated retrospective) turns the brief into owners and dates: hold, fix-forward, or proceed. Materials remain yours to archive with the release record.
What we need from your side
- A named release owner who answers within one business day
- Shared views or exports for the analytics and crash tools you already use
- Honesty about overlapping experiments and marketing plans
- Agreement that we will not invent metrics the instrumentation cannot support
Match this process to an assessment
Most teams begin with a Post-Release Impact Assessment or a Pre-Release Baseline Setup depending on whether the version has already shipped.