Back to work

Enterprise UX · Digital transformation

Hajj Enterprise Operations Platform

From meeting-driven reporting to digital operational intelligence

  • Enterprise B2B
  • Meeting-driven → digital
  • UX Lead, hands-on
  • Multi-team, Power BI, legacy data
  • Live for 2026 Hajj season
Client
Leading energy provider in Saudi
Role
UX Lead + Product Designer
Duration
4 months
Team
2 designers, with PM, Ops, Mecca and development counterparts
Delivery
2026 Hajj season, MVP 3
The live power monitoring dashboard for the Hajj period alongside the project-manager data entry platform, showing load, meter connectivity, interruptions, readiness and the projects list.

01 · Overview

Overview

Led the UX transformation of a PowerPoint- and meeting-driven Hajj reporting process into a connected enterprise platform for operational data capture, validation, reporting and executive decision-making.

02 · The problem

Operational reality lived in decks and meetings

  1. 01Operational status was reported in PowerPoint decks, assembled by hand.
  2. 02Each department reported in its own structure and its own terminology.
  3. 03Progress was reviewed in physical meetings, on the meeting’s schedule.
  4. 04Information arrived fragmented and inconsistent across sources.
  5. 05There was no digital view of consumption, outages, overloads or readiness.

What the organisation needed was a single path: capture reality on the ground, validate it, publish it digitally, and put timely information in front of leadership while there was still time to act.

A legacy Arabic project report slide next to the new digital project detail screens that replaced it.

The legacy reporting artefact, and the digital surface that replaced it.

03 · Approach & key decision

Getting the governance model right before designing on top of it

Role
UX Lead, hands-on throughout: discovery, data and KPI analysis, information architecture, flows, hi-fi UI, developer handoff and QA. I led two designers on the engagement.
Challenge
Information was fragmented, inconsistently structured, and rarely tied to a clear action. Source reports were in Arabic and translated for the design work, with terminology verified against native speakers before it entered the interface.
Governance decision
The initial assumption was that Mecca users would correct project data directly. The validated model inverted it: the project manager reports reality, the Mecca team reviews, and then either approves and publishes or sends it back for revision. Catching this before the downstream design was built kept the approval trail, the states and the entire data-entry surface aligned with how the organisation actually works. It was the single clearest UX-leadership moment on the project.
The initial information architecture next to the structure confirmed in the users and stakeholder workshop sessions.

Initial understanding, and the structure confirmed in workshop.

04 · The workflow

Capture → Validate → Publish → Decide

  1. 01 · Project manager

    Capture

    Reports ground reality against their own projects, in a structured entry flow rather than a deck.

  2. 02 · Mecca team

    Validate

    Reviews each submission and either approves it or sends it back for revision, with the trail preserved.

  3. 03 · The platform

    Publish

    Approved information moves into structured digital reporting instead of a scheduled review meeting.

  4. 04 · CEO & operations

    Decide

    Read readiness, load, interruptions and risk from a shared view, and act on them in the same cycle.

Requirements and operational understanding on the left, and the confirmed PM-to-Mecca-team approval workflow diagram on the right.

The four stages as one connected approval workflow.

05 · Execution & constraints

Two surfaces, one vocabulary, inside a fixed data model

Data-entry platform
A separate product surface, deliberately not part of the CEO portal: login → project list → add or update → approval → reporting. Keeping it separate meant the people reporting reality were never designing around an executive’s view of it.
States as reusable patterns
On Track, Delayed, Completed Early, Completed Late and Not Started, plus empty and no-result, validation, error, approval and send-back. These were authored as reusable patterns rather than one-off screens, so the same vocabulary carries across the whole workflow.
Constraints navigated
Power BI’s chart limitations meant investigating which visualisation patterns were actually supported and adapting the information design around what was feasible. The underlying data model could not be changed, so I designed around it, restructuring how information was surfaced without touching the source structure.
The Hajj operating cycle
The same dashboard was designed to shift focus across pre, during and post Hajj: readiness before, live operations during, and learning after.

New project entry

Final UI of the new project entry form, on the project info step.
Wireframe of the data-entry platform's new project entry form, on the project info step.
WireframeUI design

Mecca users review screen

Final UI of the Mecca review screen, with the project details panel and the approve and publish action.
Wireframe of the Mecca review screen: the projects table with a project's details open in a side panel.
WireframeUI design

Data-entry platform: entry and review, wireframe to final UI.

The during-Hajj live operations dashboard next to the pre-Hajj readiness dashboard, showing the same surface with different priorities.

One dashboard, two phases of the cycle: live operations and readiness.

06 · Delivery & outcome

A connected ecosystem, live for the 2026 Hajj season

The PowerPoint-and-meeting reporting process was replaced by a connected capture → validate → report → decide ecosystem, live for the 2026 Hajj season at MVP 3.

The change is qualitative and stated as such: leadership moved from periodic visibility that arrived with the next deck to continuous digital visibility of the same operation. No adoption, time-saving or performance figures were measured, so none are claimed.

CEO during dashboard

Delivered UI of the CEO dashboard, with the readiness index, projects at risk, site distribution and drill test countdown.
Wireframe of the CEO dashboard: readiness index, project and maintenance summaries, site map, risks and safety reports.
WireframeUI design

Data entry landing page, PM users

Delivered UI of the project-manager data-entry landing page with the my projects table.
Wireframe of the project-manager data-entry landing page with the my projects table.
WireframeUI design

Both surfaces, from wireframe to delivered interface.

Conclusion

“The real transformation wasn’t the dashboard. It was changing how operational information moved through the organisation, from ground reality to leadership decision.”

Next case studies

More works

Portrait of Mohammed Rizwan

Mohammed Rizwan

Senior Product Designer and UX Lead

Location
Dubai, UAE
Experience
15+ years

Drag to swing · Click to flip

Off the clock

Rizwan wearing a blue helmet and harness in a misty mountain landscape.

Usually watching a Guy Ritchie film, planning my next trip, or chasing an adrenaline rush.

Click to flip back

LET'S TALK

Let’s build something meaningful together.

Book a meeting

Connect with me

Emailmailrazik@gmail.comPhone+971 556703127