Pilot Findings One-Sheet
April 2026 • Select Stores — Onboarding Scenarios 2 & 3
PROTOTYPE SCREENS TESTED
S2 Location Error
S3 No Stores Warning
Tested at prototype v151. Figma Make v160 incorporates 2 recommendations from this pilot.
MICROCOPY · BEFORE → AFTER
Scenario / Label
BEFORE (tested v151)
AFTER (recommended / v160)
S2
Location error message
"We couldn't find that location. Check the spelling or try a nearby city or ZIP code."
"Location not found. Try a different spelling, city, or ZIP — or use 'Use my location' below."
S2
Recovery options
None — no GPS button, no autocomplete, no 'did you mean?' suggestion.
"Use my current location" button + real-time autocomplete dropdown as user types.
S3
Warning title
"We couldn't find stores with weekly ads nearby. Try expanding your search or continue with budget-friendly ingredients…"
"No stores with weekly ads near your location." (separate title, distinct from body)
S3
Undefined jargon
"budget-friendly ingredients" — undefined, implies a degraded/unknown experience.
"budget-friendly recipe suggestions rather than live store sale prices" (v160 fix applied)
S3
Primary CTA
"Continue" — same label as normal flow; no signalling of consequence.
"Try a different location" — amber button, visually distinct (v160 fix applied)
S3
Secondary CTA
"Expand your search" — text only, no tappable target, no definition.
"Continue with limited features" — underlined link, explicit consequence label (v160)
S4
Post-onboarding error
"Something's wrong. We can't load your plan."
"We hit a snag loading your plan. Tap to retry — your progress is saved."
2 NEW UI MOMENTS ADDED · Figma Make v160
1. Explicit Recovery Button
"Try a different location" — amber primary CTA at the S3 warning. Gives users a clear action path instead of a dead-end text hint.
2. Informed-Consent Continue
"Continue with limited features" — secondary link that names the consequence before users commit, replacing the original unlabelled "Continue" button.
BARRIERS & DESIGN SOLUTIONS
CRITICAL
S2
No recovery path for location errors
FINDING When the location field fails, there is no GPS button, no autocomplete, and no 'did you mean?' suggestion. 0 of 3 testers who encountered this recovered without facilitator help.
FIX Add 'Use my current location' GPS button + real-time autocomplete to the location field. Target: 100% self-recovery rate.
HIGH
S3
Users proceed past no-stores warning without understanding
FINDING The 'budget-friendly ingredients' label was undefined jargon. Predicted comprehension of the consequence: 10–15%. A participant could tap Continue and reach onboarding completion without ever understanding they'd have reduced features.
FIX Require a single confirmation step ("I understand I won't see live sale prices") before 'Continue with limited features' is enabled. Add a feature-comparison tooltip.
MEDIUM
S2 + S3
Two error states share ambiguous copy that obscures cause
FINDING Both errors (invalid location + no stores) produced warning-style copy without identifying which problem occurred. Testers could not reliably distinguish a 'bad address' error from a 'no stores here' warning.
FIX Use distinct, problem-naming titles: e.g. "Location not found" vs. "No stores with weekly ads here". Standardise 'Try again' affordances across both states.
STAKEHOLDER FINDINGS
3 / 3
testers completed
onboarding (Sc. 5 & 6 reachable)
0 / 3
S2 error recoveries
without facilitator help
~70%
predicted notice rate
for S3 warning
10–15%
predicted comprehension of
"budget-friendly ingredients"
v160
Figma Make already
incorporates 2 recommendations
NOT READY FOR PILOT LAUNCH
2 critical / high barriers require resolution before the onboarding flow is suitable for real users. Fix S2 recovery path and S3 informed-consent step first.