Product & UXR · Insight sprint

It tells you the wait. It never teaches the day.

Study: 29 AI-moderated interviews, IQS 3.84/5 · first-time cell is thin (5, ~3 clean), so first-timer reads are directional; the home-screen clutter finding is stimulus-caveated.

Key takeaway

The app is a lookup that assumes you already know how to run a park day, so it teaches no one, and the people who need teaching most can't tell you they're stuck.

The fix isn't more features, it's guidance and literacy. And first-timer difficulty won't surface in first-timer feedback, so design the first day from what veterans watch happen.

What's going on

Five findings.

The app informs, it doesn't compose.

It answers "what's the wait, where is this, what's on the menu" and stops there. It never sequences a day or teaches the system.

the app doesn't actually really teach you that virtual queues exist [...] there's no tutorial like, 'Oh, it's your first time at Disneyland, you should know this.'P12 · 18-24 M CA @ [12:15]

So strategy lives outside the app.

People learn ride order, Lightning Lane timing, and insider moves from Reddit, TikTok, and cast members, not the product.

I learned it through Reddit before I went on the trip, people were talking about the best strategies for getting on rides.P06 · 35-44 F CA @ [12:56]

The newcomer deficit is latent and witnessed.

First-timers often call the day "easy"; the veterans next to them describe the struggle the newcomer doesn't report. State it as a mechanism, not a rate.

I've personally seen my friends [...] literally wait for five minutes in front of the entrance trying to scramble to scan their phone because they don't know where it is.P16 · 18-24 F CA @ [12:34]

Disconfirming case kept in view: No, we're all pretty app savvy. (P24 · 35-44 M NJ @ [08:58]). Newcomer ease is real for some and tracks prior digital fluency.

The queue system is the densest comprehension gap, and it reaches passholders.

Lightning Lane, Virtual Queue, and reservations are unclear even to frequent visitors. Because it's a paid feature, the confusion isn't just UX, it's suppressed uptake.

I said maybe the virtual queues one. I don't know exactly like what that is and it's hard to tell.P17 · 25-34 F CA @ [07:46]

Concrete frictions stack on top.

Restrooms are the most frequently named navigation gap with no filter; food discovery is vendor-by-vendor with no food-first view; the gate scan and map legibility both cost people time in the moment.

I don't recall seeing a filter option for just finding bathroomsP25 · 18-24 F OH

who's gonna know that there's that item at that stall.P27 · 25-34 F CA @ [13:36]

Where users stall

The journey, with the friction at each node.

Plan the day

learns on Reddit, not the app

Enter the park

gate-scan scramble

Navigate

map shows but doesn't read

Eat

food discovery is a database; order status fails silently

Manage queues

LL / VQ not understood, even by passholders

Stay present

"exhausting and necessary"; heaviest users most bothered

The app is strong at the lookup nodes (a fact, fast) and absent at the composition nodes (sequencing the day, teaching the system, surfacing what's next). Every stall is a place it informs but does not guide.

What's driving it

Psychology and needs.

"I don't know what I don't know." The deficit is invisible to the person who has it, so they can't ask for help and don't report a problem.
I don't know the things that I don't know [...] there's a lot of different tabs and clickable things on the app that I've never clicked.P26 · 25-34 F CA @ [04:34]
Need: scaffolding and discoverability, not more features.
Control vs. presence (a real say-do gap). People say they want to be present, and the better the app works the more it pulls them onto the phone. The heaviest users are often the most bothered. Need: the app to reduce checking, not reward it.
Two opposing home-screen needs (don't average them). One camp wants less ("tune out the noise"); another wants it personalized to their day. Both are real; the package does not claim they converge. Need: treat them as two design bets, not one.
Trust through accuracy. Wait-time lag and silent failures (a mobile order that never updates) break reliance fast. Need: honest, current state over more surface area.

Do this

Sequenced by horizon.

This sprint

Prototype a "what's next" sequencing layer (live waits, location, and the bookings the guest already holds) and a plain-language Lightning Lane / Virtual Queue explainer. Backlog the cross-segment quick wins with specs: a restroom filter, a food-first search across vendors, and the entry pass / gate scan on the home screen.

Next sprint

Test a personalized, logged-in home ("your day") against the real screen, and a first-session onboarding built from what veterans observe newcomers miss, not from newcomer self-report.

Not now / needs data

Size the first-timer cell (thin: 5, ~3 clean) before sized first-timer claims. Re-measure home-screen clutter on the real logged-in screen (the stimulus was logged-out and promo-heavy). Leave price/coupons and brand positioning out of this brief.

Evidence: 29 AI-moderated interviews, IQS 3.84/5. Single-method qualitative, no quant instrument: every finding here is directional, not sized. First-timers are thin (5 in cell, ~3 clean); the home-screen clutter finding is stimulus-caveated (logged-out, promo-heavy). Quotes are exact and located to the transcript. Validate with a sized wave before committing roadmap.

More cuts of this study

The same findings, rendered for other rooms. Open any cut.

The full storyThe showcaseThe scrollytelling walkthrough of the whole study, start to finish. For brand & growth marketingMarket insightsOrientations, positioning, and what to say to whom. Unsized by design. For leadershipExecutive one-pagerThe single decision: invest in guidance and literacy, not features. For academicsWhite paperThe method (the Interview Quality Score) and the mechanism, for peer review.