Jagadeeswaran Ganesan

A theme park, an F1 circuit and a cultural district do not report the same things. They still had to be run to one standard.

Research, structure and interface design across Qiddiya's verticals, where every business needed a platform of its own and all of them had to agree underneath.

Sector
Giga-project, Saudi Arabia
Year
2025 to present
My role
Stakeholder research, information architecture, UX/UI, design system
Scope
Seven platforms, five verticals
qiddiya · programme control
Portfolio All verticalsSportsEntertainment
38Active packages
91%On schedule
6Need a decision
SportsCultureTheme parkMotorsportHospitality
Theme park · ride systemsOn track
Motorsport · circuit worksDecision due
Culture · district fit outOn track
Motorsport OverviewPackagesRisks
PackageOwnerStageStatus
Circuit surfacingDeliveryStage 4Approved
Pit complexDesignStage 3In review
Spectator accessOpsStage 2Blocked
Broadcast compoundDeliveryStage 3Approved
Every vertical uses the same four stages. What sits inside them is theirs.
Awaiting you 6SentClosed
Spectator access, stage 2Blocked
Motorsport · raised by Operations · 4 days
Two business units hold different dates for the same handover. One of them has to move.
Send backDecide
Sports · venue commissioning2 days
Hospitality · phasing5 days

PortfolioEvery vertical at once, and the six things that actually need a person.

Reconstructed in HTML for this page. Representative layouts, invented data, no client material.

The challenge

Qiddiya is not one business. Sports, entertainment, culture, theme parks and motorsport each run their own operation, with their own business units, their own teams and their own idea of what progress looks like.

  • The same word meant different things. Ready, approved and complete each carried a different definition depending on which vertical you asked. One set of stages every business had to map onto, and freedom inside them.
  • One platform would have fitted nobody. A circuit package and a cultural fit out do not share a workflow, and forcing them to would have made both worse. Separate platforms per business, built from shared parts.
  • Nobody could see across. Leadership had reporting assembled by hand, arriving late and already out of date. A portfolio view that reads from the same data the teams work in.
  • People left before they started. On the version this replaced, exit and bounce sat at 100 per cent. Users landed and went straight back out. A first screen that says what the session is for and the shortest way to finish it.

The insight

The instinct on a programme this size is to standardise the work. That fails, because the work genuinely is different. What can be standardised is the language it reports in, and what it feels like to be inside it. The version before mine functioned, and people still did not take to it, because nothing about it read as Qiddiya.

0

Reported construction value of the programme

0

Square kilometres, the size of the city being built

0

Attractions planned across more than twenty neighbourhoods

0

Residents at full scale, alongside the visitors

Scale figures published by Qiddiya Investment Company, construction value from published project reporting. They describe the programme, not my contribution to it.

What that decided

Not one platform. Seven, each shaped around how that business actually runs, sharing one set of stages, one set of components and one definition of every status word.

And one set of guidelines carrying Qiddiya's brand and its culture through all of them, so a person opening any of them recognises where they are before reading a word.

Most of what these platforms hold is data, so the charts, the scales and the way a figure sits on a page are the design rather than decoration laid over it. Getting someone to their number in fewer steps is an art direction problem as much as a flow problem.

The product

Not one platform. One standard, and a platform per business.

Seven platforms across the businesses. Each matches the work it serves. Underneath, the same stages, the same components, the same words and the same brand, so everything still adds up at the top and still looks like one organisation.

One standard

sports
Venue readiness12 packages
8Ready3In review1Blocked
theme park
Ride systems26 packages
19Ready5In review2Blocked
motorsport
Circuit works17 packages
11Ready4In review2Blocked
culture
District fit out9 packages
6Ready2In review1Blocked
SportsVenues, commissioning, event readiness
Theme parkRides, systems, safety sign off
MotorsportCircuit, pit and broadcast works
CultureDistricts, fit out, programming

Four of the seven shown here. Different work, different screens, the same stages and the same words underneath, so a package in motorsport and a package in culture still mean the same thing when they meet at the top.


How the work was done

Stakeholder research

Rounds of interviews and working sessions across the verticals, with the people who run the work and the people accountable for it.

Language audit

Collecting what each business meant by ready, approved and complete, then agreeing one definition everyone could live with.

Systems mapping

Drawing how each vertical actually operates before designing anything, so the structure came from the businesses rather than from a template. Where two units disagreed, the map made it visible instead of leaving it to be discovered later in a build.

Qiddiya Five verticals, one language

Shared components

One library behind every platform, so a status, a stage and a package read identically no matter which business you are in.

Testing with the teams

Put back in front of the same people it came from, vertical by vertical, before it was built rather than after.


What came out of it

Seven platforms rebuilt to one set of guidelines. Satisfaction rose from 2 to 8 out of 10, and conversion went up 300 per cent. Conversion here means a session that reaches its target: the person gets the data they came for, in the fewest steps, without dropping out on the way.

The version before it worked and people still would not use it. Exit and bounce sat at 100 per cent, so nobody was getting past the landing page to find out whether it was any good. It carried nothing of the brand and nothing of the culture, so it never felt like theirs. Very little of that movement is new functionality. It is recognition, and a route to the number that does not make people give up on the way there.

0

Platforms, rebuilt to one set of guidelines

2 → 8

Satisfaction score, out of 10

0

Increase in conversion

Measured against the versions these replaced, where exit and bounce sat at 100 per cent.


Want the longer version?

Happy to walk through the research, the disagreements it surfaced and how the structure settled.