Draft — under review. Last updated 19 October 2026. Where a fact is still open, this page says so rather than guessing.
Use case
Run a governed weekly product review
The weekly review is where a team agrees what moved and who follows up. It goes wrong when two people bring two different numbers for the same metric.
Who does it
The product team, with the analyst who owns the definitions.
What data it needs
- The handful of metrics the review covers — conversion, activation, retention — each with one agreed definition.
- Events in a supported store that are fresh enough for the review day.
Step by step
| Step | Status |
|---|---|
| One dashboard for the review: trends, funnels, retention, journeys | Live |
| Short written summaries of what each chart shows | Live chart narration |
| Every number resolves to one approved, versioned definition | In build catalog |
| Show data freshness and definition changes since last week | In build |
| A daily or weekly digest posted to Slack, with anomalies flagged | Next Watch |
| Evidence attached to each unusual movement, ready to assign | Next Watch · Later Dig |
What the review includes
Each number comes with its definition and version, the period, how fresh the data is, and the change since the last review. A movement that looks unusual carries the chart and breakdown behind it. It is flagged as something to look into, not explained away.
The decision it supports
Who follows up on what, by when — agreed against numbers nobody needs to re-argue. Any investigation it starts follows the activation-drop pattern.
Questions this page doesn't answer are the ones we want to hear. Ask on a call, or write to contact@depsmith.com.
Request a demo