Rapid Validation: De-risking Basket Order Discoverability Using Remote Testing
How I piloted a new remote testing tool (Useberry) to identify critical discovery flaws before to identify critical discoverability gaps before development handoff.
Project Overview
Role
Senior UX Researcher
Timeline
Aug 2023
Methods
Useberry Testing
Outcome
Fixed Critical Discovery Flaw
Business Context
A new “Basket Order” feature was being prepared for web release to support advanced traders executing multi-leg orders.
Given the feature’s complexity and its impact on trading speed, discoverability and first-time usability were critical to adoption. However, no external validation had been conducted on the new navigation entry point.
Release timelines did not allow for a traditional moderated usability cycle. The team needed rapid, directional evidence to de-risk the launch before development freeze.
This study was initiated to validate discoverability and execution flow under tight time constraints using remote unmoderated testing.
The Challenge: The "Invisible" Feature
We were about to launch "Basket Orders" on the web platform—a complex feature for advanced traders to execute multiple orders simultaneously.
-
The design solution was finalized, but no external validation had been conducted on feature discoverability.
-
The Constraints: We had no time for moderated interviews. We needed quantitative confidence, fast.
-
The Solution: I used this opportunity to pilot Useberry, a remote unmoderated testing tool, to run a rapid "First-Click" and "Task Completion" study.
-
The "Agile" Methodology
To avoid delaying release timelines, I piloted Useberry for unmoderated prototype validation.
-
Tool: Useberry (for Heatmaps & Click-Path Analysis)
-
Tasks: 5 Core Tasks (Create, Add Scrip, Clone, Rename, Modify)
-
Metrics: Time on Task, Misclick Rate, and Completion Rate.
The Discovery: Users Couldn't Find It
The heatmap data from Useberry revealed a critical flaw instantly:
The feature was invisible.
-
The Fail: Task 1 (Create a Basket) had a 36% Success Rate—the lowest of all tasks.
-
The Friction: Users spent an average of 43 seconds just looking for the button.
-
The Evidence: The heatmaps showed users clicking everywhere except the correct tab. They expected it under "Regular Orders," but we had hidden it under a generic "Orders" tab.
Useberry Heatmaps revealed "Click Chaos"users clicked 270 times on the wrong elements, proving the entry point was not intuitive.
The "Quick Fix" Recommendations
Early detection enabled low-cost design iteration prior to release.
-
Add a "New" Badge: I recommended adding a visual highlight or "New" tag on the navigation bar to signal the feature's location.
-
Guided Onboarding: For the "Clone Order" task (which had high misclicks), I recommended a "First-Time User Experience" (FTUX) tooltip to show users where hidden actions were located.
The Impact: Research at the Speed of Design
This project wasn't just about "Basket Orders"; it was a proof-of-concept for Agile Research Ops.
-
Product Impact: Entry-point visibility was improved prior to release, reducing first-time discovery friction.
-
Ops Impact: Validated remote unmoderated testing as a scalable early-stage validation method, reducing dependency on fully moderated studies for exploratory checks.
Reflection
This project reinforced that research depth must match business velocity. Not every question requires a full moderated study but every release requires evidence. By adopting unmoderated tools like Useberry, I shifted research from being a 'bottleneck' to being a 'velocity enabler,' allowing the team to ship with confidence, faster.