Run an Amplitude Dashboard Review
Give each dashboard chart a question, owner and decision context before the review. The meeting should explain meaningful changes and choose follow-ups, rather than narrate every line that moved.
Before you start: Have saved charts, edit or ownership access as needed and a small set of product questions. Verify that the review audience can open the sources.
Worked example: An onboarding review includes eligible signup volume, activation and a relevant guardrail. Each chart should explain what changed, whether it is trustworthy and what decision follows.
Step-by-step guide
Write the review questions
Choose the few decisions the team needs to make. Remove charts with no current question rather than expanding the dashboard indefinitely.
Verify the inputs
Check event definitions, exclusions, dates and cohort maturity. Assign each metric an owner who can explain its limitations.
Assemble the saved analyses
Add the relevant charts to the dashboard using supported controls. Label intentional differences in population or time range.
Review exceptions first
Focus discussion on meaningful changes and data-quality concerns. Separate measurement artifacts from plausible behavior changes.
Choose an investigation
Record a specific hypothesis, evidence needed and owner. A chart movement should not automatically become an implementation ticket.
Preserve the decision record
Save what the team decided and when it will revisit the question. Keep source links so the next review can assess progress.
Common mistakes
Chart tour replaces decisions
Reading every number consumes the review without changing action.
No metric owner
Definitions become folklore. Assign accountability.
Mixed periods compared
Label exceptions before interpreting movements together.
Tips
Put the decision question in each chart description.
Review measurement changes before business interpretation.
Start the next meeting with prior follow-ups.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.