Ali Demirbaş - Lab

Dashboard

Empty-State Action Card on a Dashboard A/B Test

A new user may open a dashboard before any data is available and see an empty screen.

  • Dashboard
  • First-action completion rate

Control vs Variant

Absent on one side, present on the other.

Changed
Presence
Page
Dashboard
Difference
added

Hypothesis

A card suggesting a first action may encourage initial engagement, compared with a message that only says there is no data.

How to run this test

Primary metric

First-action completion rate

Compare completion of the same predefined first action among eligible users assigned while their dashboard is empty.

Other metrics

  • Time to first meaningful dataMeasure time from the empty state to the predefined first data event.
  • Seven-day active useCompare all assigned users over the same seven-day activity window, not only those who follow the card.
  • Support contactsTrack questions such as “Where should I start?”.
  • Card dismissal rateUse dismissal as a diagnostic measure within the variant; there is no equivalent card in the control.

What to check before and during the test

  • CardAdd one predefined card that explains a practical first task.
  • Keep constantKeep dashboard features, task requirements and other onboarding steps unchanged.
  • Exit conditionRemove empty-state guidance once the relevant data or action exists.
  • SegmentsApply the same eligibility rules when reviewing self-registered and invited users.
  • Separate testsTest card copy, illustration or checklist-versus-single-action separately.

Setup mistakes to avoid

  1. 1Do not use sample data that could be mistaken for the user's real data.
  2. 2Test the card as one component; compare copy and visual alternatives separately.
  3. 3Let visitors dismiss the card or ignore the empty-state guidance.
  4. 4Do not block access to other features until the suggested action is complete.
  5. 5Do not mix sample data intended for different user segments.