UI Elements
Adding Shortcuts for Frequent Actions: A/B Test Idea
A shortcut may remove repeated navigation for a familiar task. 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.
A/B test scenario. This page is a test plan, not the result of a real experiment.
- 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
If users with relevant history get a predefined shortcut for a task they repeat, they can finish it without going through the same navigation every time. Successful task completion rate could then rise, unless stale defaults lead to errors that cancel out the gain.
Test plan
When to run this test
Repeated navigation steps in analytics, session recordings of users making the same selections from scratch, or support tickets asking for a faster way to do a task show people taking the same long path again and again. A shortcut that works gets picked by eligible users, who review the information it brings back and complete the task without errors. If the task cannot be undone, do not reduce it to a single tap; design a review step first or choose a different task.
How to measure success
Successful task completion rate
Compare error-free completion of the predefined task among eligible assigned visitors.
Also track
- 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.
How to set it up
- 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.
What to watch when reading the result
- 1Shortcut usage or a shorter task completion time does not count as success on its own. Judge it by successful task completion rate, and check that the failed task rate and the cancellation or correction rate after completion do not rise, because a fast but wrong transaction is not a gain.
- 2Keep the main flow's steps unchanged in this test, or you will not know whether the difference came from the shortcut or from a new flow. Read users with different task histories separately, and make sure the shortcut does not sit ahead of the standard path for new users, who may find it meaningless.
- 3If usage is low or the difference is unclear, do not remove the shortcut right away; it may matter a lot to a small group of repeat users, so check their successful completion separately. Test whether the gap between the arms could be down to chance with the A/B test significance calculator.
Frequently Asked Questions
Who should see the shortcut?
Determine eligibility before assignment using a fixed history rule. A prominent shortcut may confuse people without relevant history. Review eligible groups with different transaction histories separately.
Can reused defaults create risks?
Yes. Verify that reused information is current and visible for review. Do not apply hidden assumptions or reduce an irreversible action to one unreviewed tap.
Does frequent shortcut use mean success?
Check failures and corrections or cancellations after completion. Fast but incorrect transactions are not a gain. Use error-free transaction completion as the primary outcome.
Should a low-use shortcut be removed?
Not automatically. It may matter greatly to a small repeat-user group. Keep one fixed location that does not block the standard route, and preserve the main flow's steps.
More tests in UI Elements
All testsAuto-Advancing to the Next Step: Flow A/B Test Idea
UI elementsFlow completion rate
A multi-step flow experiment example: manual continue versus auto-advance once a choice is made. See both arms, the control-and-undo notes and the KPI.
Site-Wide Campaign Announcement Bar A/B Test Example
UI elementsCampaign action completion rate
Adding a time-boxed announcement bar across every page, framed as an experiment example with both arms, the banner-blindness risk and the KPI.
Announcement Bar Timing: Immediate or Delayed A/B Test
UI elementsCampaign page visit rate
A campaign bar timing test comparing immediate display with one precisely defined delay rule. Set the delay and target campaign action before launch.