Universal Studios
Universal Orlando: Guest account and AI experience strategy
Designing a future-state trip planning experience that connected guest accounts, conversational AI, and the wider park journey across web and mobile.
Role: Senior Product Designer and UX Strategist, contract. Timeline: 2026, roughly five months. Disciplines: product strategy, UX architecture, customer experience, competitive research, interaction design, and service design.
Exploratory concept work. Mid-fidelity, not shipped.
The challenge: a trip spread across too many moments
Planning a major park visit is not one task. Guests research, compare, book, prepare, arrive, navigate, and reflect across several products and channels. Tickets, hotels, dining, account details, personalization, and in-park experiences each have their own context, while the guest experiences one trip.
My role: turn a fragmented ecosystem into a North Star
I worked across the current Guest Account experience and future-state customer experience strategy. I partnered with product managers and a design systems designer during sprint work on live account flows, while also mapping the wider architecture needed to support a more connected guest journey across the California, Orlando, and Japan parks.
Understanding the existing architecture
The first step was understanding how the existing layers worked together. I mapped the account layer, personalized homepage, loyalty and identity experiences, commerce, and the emerging conversational layer. Each system had a different definition of the guest and the trip. The architecture map made those gaps visible and gave the team a shared language for discussing the future state.
Defining the opportunity for agentic AI
The opportunity was not simply to add a chatbot. It was to define where a conversational agent could genuinely help, what it could resolve at each stage of the journey, and when it should hand off to a human or a product flow. I mapped potential touchpoints across web and mobile, then used stakeholder conversations and research planning to test where the agent should live and what role it should play.
Questions that shaped the work
What does the guest need at this moment in the trip?
What can the agent resolve without sending the guest somewhere else?
Where does trust need to come before commerce?
What happens when the answer is uncertain or the environment is difficult?
Competitive research changed the framing
I ran a competitive teardown across travel planning and park experiences, looking at conversational interfaces, itinerary building, preference capture, group planning, messaging, and the relationship between AI and owned inventory. The research showed a clear strategic gap: products with strong AI often lacked direct inventory, while products with direct inventory did not yet have a strong conversational front door.
The trip planner conceptI translated the strategy into a future-state trip planner for web and mobile. The concept connected the conversational agent to saved items, trip planning, booking context, and group decision-making. A guest could start from a social post, screenshot, or booking confirmation, then build a plan instead of starting with an empty screen.
Core flows explored
Seed a trip from content or a confirmation the guest already has.
Save an item into a living trip while also capturing preference signals.
Plan with a group while balancing different preferences.
Move from exploration to preparation without losing context.
Why the gray wireframes mattered
The work stayed intentionally mid-fidelity. Early sketches, flows, architecture maps, and gray wireframes made it easier to discuss the model without distracting stakeholders with visual polish. The goal was not to present a final interface. It was to make the right questions visible early enough to influence the strategy.
Working across teamsAlongside the future-state work, I collaborated with product managers, research, engineering, and the design systems designer on live account experiences. That kept the North Star grounded in platform constraints, existing patterns, and the realities of sprint delivery.
Outcome and reflection
The work gave stakeholders a shared view of how Guest Account, trip planning, and conversational AI could connect over time. It also created a sequenced direction: establish a persistent conversational entry point, connect it to owned planning and booking experiences, then make the trip the organizing object across the guest journey. Because the work was exploratory, the most important outcome was alignment around what to investigate next.
Confidentiality note: This case study presents exploratory strategy and mid-fidelity concepts. Internal codenames, stakeholder names, unreleased roadmap details, and unverified performance targets are intentionally omitted.
View the Universal Orlando app
View the Universal Orlando app
Solution
I created a future-state experience model that connected Guest Account, conversational AI, and trip planning into one clearer customer journey. The work defined where the agent could help, how it could connect to saved plans and booking context, and what the platform would need to support next.
Rather than treating AI as a standalone feature, I positioned it as an intelligent layer across the experience. It could help guests start a plan, understand options, organize a group trip, and move between exploration and preparation without losing context.
What the work clarified
A shared North Star for the account and guest experience across multiple parks and platforms.
A clear set of conversational AI touchpoints across web, mobile, planning, and in-park moments.
A trip planner concept that made the guest’s plan a persistent object instead of a collection of disconnected transactions.





