farishattab5@gmail.com LinkedIn

Booking System · Web + Mobile · 2025

Qiddiya Booking Journey

A modular booking system for Qiddiya's two flagship parks, handling multiple ticket types, add-ons and group bookings across web and mobile.

Not fixed flows. A system that generates them.

Role
Lead Product Designer
Timeline
2025
Team
7 (Design, Product, Engineering)
Platform
Responsive Web · Mobile App
Languages
Arabic (RTL) and English (LTR)

At a glance

The challenge

One booking system for Six Flags and Aquarabia, each with its own tickets, add-ons and rules.

The approach

I designed a modular system that assembles each journey from shared building blocks, instead of hard-coding flows.

Impact

  1. Powered ticket sales for both parks, including Six Flags' high-demand, sell-out launch
  2. Designed and handed off end to end in 5 months
  3. Reused and extended across multiple park offerings and future experiences

01 The Problem

Business Goals

  1. One system for both parks, on web and mobile
  2. A short path to purchase that still covers accounts, payment and policy confirmation
  3. Room to absorb changing rules and new offerings

User Goals

  1. Pick the right ticket for their visit
  2. Book for a family or group without losing track of who each ticket is for
  3. Always know where they are, what they're paying and what's left

Design Challenge

How might we support many ticket types, add-ons and group scenarios without overwhelming people, and ship it on two platforms in five months?

02 Role & Constraints

  1. 01Led design of the end-to-end booking journey for both parks, web and mobile
  2. 02Defined the modular system behind every flow and template
  3. 03Oversaw design quality, consistency and approvals across the team
  4. 04Worked with engineering to map the system to backend structures and payment requirements

01

Tight Delivery Timeline

Designed, validated and handed off in five months, against park launch dates.

02

Two Parks in Parallel

Six Flags and Aquarabia were built at the same time, on one shared system.

03

Moving Business Rules

Tickets, add-ons and rules kept changing, so the flows had to change with them.

04

Payment & Security

Payment and security requirements fixed parts of the flow in place.

03 Approach & System Thinking

01

Many tickets, one simple choice

Categories, bundles and add-ons, without adding steps for the user.

02

Park-specific logic

Journeys adjust per park, from ride access to experience bookings.

03

Built to change

New rules and offerings slot in without reworking the core.

04

One experience, two platforms

Consistent on web and mobile, with interactions tuned to each.

I structured every journey as a set of building blocks, arranged by what the user picks and which park they're in. Each block works on its own and behaves the same everywhere, so the question stopped being "which flow?" and became "which blocks?"

Booking System Architecture Diagram

04 Core Building Blocks

Modular System Components

Reusable blocks, not screens, combined to fit each booking scenario.

Ticket Type

01

Ticket Type

Choose a ticket or package, and compare alternatives.

Who

02

Who

Assign up to 9 tickets across Adults, Children, Seniors, Companions and People of Determination.

When

03

When

A calendar showing availability and peak pricing, narrowing from month to week.

Add-ons & Extras

04

Add-ons & Extras

Extras assigned to individual tickets.

Experiences (AQC Only)

05

Experiences (Aquarabia only)

Date-specific experience packages, added alongside tickets.

Summary

06

Summary

A live breakdown of tickets, extras, pricing, promo codes and upgrades.

Cross-sell & Upgrades

07

Cross-sell & Upgrades

Contextual upgrades that update the cart without breaking the flow.

Login

08

Login

Placed late in the journey to cut early drop-off.

Payment

09

Payment

Saved cards, Apple Pay and financing, with a final summary before confirming.

05 UX Challenges & Interaction

Challenge 01

Designing the Stepper

The journey had steps within steps. Showing them all would have overwhelmed people, so we kept the stepper focused on where you are and what's next, and kept the rest out of the way.

Challenge 02

Managing Flow Complexity

Paths branch by ticket type, add-ons and park. Instead of forcing one rigid flow, the journey adapts to each selection, so the complexity stays beneath the surface.

Stepper & Progress Logic

Stepper & Progress Logic

The current step, what's done and what remains, without the full tree.

Responsive & Bilingual Interaction

Responsive & Bilingual Interaction

Consistent across desktop and mobile, touch and pointer, English and Arabic.

Dynamic Pricing & Feedback

Dynamic Pricing & Feedback

Every change to tickets, dates or extras updates the price instantly.

06 Key Templates

Ticket Selection

Template 01

Ticket Selection

Problem

Choosing ticket types, quantities and dates without getting lost.

Solution

A guided structure with clear ticket groups and live pricing.

Add-ons & Extras

Template 02

Add-ons & Extras

Problem

Understanding extras and assigning them to the right ticket.

Solution

A filtered list with clear availability and per-ticket assignment.

Cart

Template 03

Cart

Problem

Reviewing and editing everything before checkout.

Solution

One cart with grouped items, edits, promo codes and upgrades.

Checkout

Template 04

Checkout

Problem

Several required steps that could stall people early.

Solution

Progressive steps, login held back, and a summary that stays in view.

Confirmation

Template 05

Confirmation

Problem

Clear feedback when payment succeeds or fails.

Solution

Dedicated success and error states, with next steps and a way to recover.

07 Design Decisions

Login Mid-Journey

Decision 01

Login Mid-Journey

We moved sign-in to after people commit to buying. Fewer drop off early, and accounts are only created when there's real intent.

Cart Timer

Decision 02

Cart Timer

A 15-minute hold protects inventory during high demand and gives people a clear window to finish.

Modular System

Decision 03

Modular System

Composable journeys instead of fixed flows, so new parks and offerings don't need a redesign.

Add-ons Logic

Decision 04

Add-ons Logic

Extras attach to individual tickets, not the whole cart, so groups can customize per person without confusion.

08 Reflection

01

Treat complexity as a structural problem. The answer was a better system, not busier screens.

02

Design for change. The rules shifted throughout, and the modular approach absorbed that instead of fighting it.

03

Speed and quality don't have to trade off when the system is right. Five months, two parks, no compromise on clarity.

Next Case Study

Six Flags Qiddiya City

The flagship digital platform for a record-breaking theme park, built to introduce it to the world before it opened.

View Case Study
Six Flags Qiddiya City
Let's talk

Open to senior product design roles across global teams.