Ali Demirbaş - Lab
TRGet in touch

UI Elements

Adding Shortcuts for Frequent Actions: A/B Test Idea

A shortcut may remove repeated navigation for a familiar task.

  • UI elements
  • Successful task completion rate

Control vs Variant

Absent on one side, present on the other.

Changed
Presence
Page
UI elements
Difference
added

Hypothesis

Its assumptions may become stale, and a prominent shortcut can confuse users without relevant history. Define the target task and eligibility first, let users review reused information, and measure successful completion.

How to run this test

Primary metric

Successful task completion rate

Compare error-free completion of the predefined task among eligible assigned visitors.

Other metrics

  • Shortcut usage rateMeasure shortcut use among eligible assigned visitors who see it.
  • Failed task rateCompare errors, cancellations or invalid outcomes among visitors who start the task.
  • Task completion timeMeasure time using the same start and completion events; report non-completions separately.
  • Cancellation or correction rateTrack cancellations or edits after completion over the same follow-up period.

What to check before and during the test

  • ShortcutAdd one predefined shortcut for a repeated task.
  • EligibilityUse a fixed history-based eligibility rule before assignment.
  • Reused informationMake defaults current and visible so users can review them.
  • PlacementUse one fixed position without blocking the standard path.
  • ExperienceReview users with different levels of task history.

Setup mistakes to avoid

  1. 1Do not reduce an irreversible action to a single unconfirmed tap.
  2. 2Change the shortcut only, not the steps in the main flow.
  3. 3Show users the default information before applying it.
  4. 4Do not place a shortcut that makes no sense for new users ahead of the main path.
  5. 5Do not remove a shortcut solely because usage is low; review task success and user need.