Journey Maps for a
Complex Loyalty Program.

Structuring scattered knowledge into clear, persona-based journey maps — so teams could finally understand the full picture and act on it.

Role
Product Designer
Collaborators
Mariana (UX Researcher) · Internal Stakeholders
Context
MGM Resorts · Loyalty Program
5
Persona-based journey maps
Centralized knowledge repository
Cross-team alignment
Strong feedback from leadership
01 — At a glance

Everything you need
to understand this project.

Project Structure complex loyalty journey maps across 5 personas to bring clarity, surface gaps, and enable better decision-making for internal teams.
Role Product Designer — worked in duo with Mariana (UX Researcher), combining research depth and design synthesis across the full project.
Goals Understand user progression across tiers · Identify pain points and gaps · Improve clarity for internal teams · Enable better decisions
Process Audit · Desk research (with AI) · Stakeholder interviews · Centralized repository · Persona journeys · Adapted silent critique · Synthesis & presentation
Outcomes Clear persona-based journey maps · Centralized knowledge · Improved cross-team alignment · Strong positive feedback from stakeholders and leadership

Note: This project is shared with permission. Sensitive details and company name have been omitted.

02 — Problem

Information was
everywhere.

Journey maps, rules, and documentation lived across multiple tools and formats. Nobody had the full picture — they had pieces of it.

At the same time, the loyalty system was genuinely complex: multiple tiers, rules that varied by context, and interactions that crossed both online and offline channels.

Scattered knowledge
Existing journey maps, studies, and documentation were spread across tools with no shared reference point.
Complex system
Multiple loyalty tiers, overlapping rules, and online + offline touchpoints made it hard to see the journey as a whole.
03 — Challenge

Not just mapping the journey.
Making it understandable.

We needed input from multiple areas to get this right. But the conditions weren't easy.

No time for long sessions
Stakeholders were busy. Traditional workshops weren't going to work.
Too complex to review at once
The material was dense. Presenting everything together would overwhelm rather than align.
Mixed audiences
Many participants were unfamiliar with journey maps and design artifacts.
Journey map overview
04 — Opportunity

Turn complexity
into clarity.

The goal wasn't just to document the journey. It was to make it usable for decision-making.

When teams can see the full picture — across tiers, personas, and touchpoints — they stop working from assumptions and start working from shared understanding.

05 — Approach & Process

How I got
from scattered to structured.

1
Audit and research
Reviewed existing journey maps, documents, and previous studies to understand what already existed — and what was missing.
2
Responsible AI usage
To accelerate desk research in a complex domain, I used Cody AI — grounded only in official Help Center documentation, with no internal or sensitive data. AI supported the process; decisions were validated with stakeholders.
3
Structuring knowledge
Created a centralized repository so journey maps and resources were accessible in one place — instead of scattered across tools.
4
Stakeholder interviews
Interviewed internal stakeholders to gather domain knowledge, validate assumptions, and capture what existing documentation couldn't show.
5
Persona-based journey mapping
Instead of one large map for everything, we split the experience into multiple persona-based journeys — each with actions, pain points, opportunities, and online/offline interactions.
6
Adapted silent critique
Traditional critique didn't work for this level of complexity. I broke the journey into smaller parts, ran short focused sessions, and collected independent feedback — so every voice had equal weight without influencing others.
7
Synthesis and presentation
Consolidated feedback into refined journey maps and presented results to designers and leadership.
06 — A note on AI

Using AI
responsibly.

This work was developed in early 2024, when AI tools were still evolving rapidly. The domain was complex — many rules, edge cases, and tier-specific logic — and time was limited.

How I used Cody AI on this project
Grounded only in official Help Center documentation — no internal or sensitive data.
Used to accelerate understanding of rules and edge cases during desk research.
All outputs were validated with stakeholders before being used in deliverables.
AI supported the process. Decisions remained human.

Centralized repository or research organization

Centralized repository — all journey maps, documents, and references in one place

07 — Journey Mapping

One map per persona.
Complexity made manageable.

Splitting the experience into 5 persona-based journeys was the key decision. Instead of one overwhelming document, each map focused on a specific user and their path through the loyalty program.

Each journey included actions, pain points, opportunities, and both online and offline touchpoints — giving teams a complete view without the noise.

Persona-based journey map

One of the 5 persona-based journey maps — actions, pain points, and opportunities across touchpoints

Full journey map overview

Overview of all 5 journeys organized in the centralized hub

Journey map detail
08 — Adapted Silent Critique

Feedback that works
for non-designers too.

Traditional critique sessions weren't going to work here. The material was too complex to review at once, and most participants weren't designers.

I adapted the silent critique format: broke the journey into smaller parts, ran short focused sessions, and collected feedback independently — so no one voice anchored the rest.

Why this matters: When participants review independently, the feedback reflects what they actually think — not what they heard someone else say first.

Silent critique session

Adapted silent critique — short, focused sessions with independent feedback from cross-functional stakeholders

09 — Results

A shared reference
teams could actually use.

The journey maps became the go-to reference across teams. Complex flows that were previously difficult to discuss became easy to navigate and act on.

The feedback was strong — from stakeholders and leadership — specifically for clarity, structure, and how the work was communicated.

Final presentation

Final synthesis presented to designers and leadership

10 — External Writing

I documented
this approach publicly.

After this project, I wrote about how the silent critique method can be adapted for complex journey maps — so other designers could use it too.

11 — Key Takeaway

Complexity is not
the problem.

Lack of structure is. When information is clear and accessible, teams align faster and make better decisions.

The work wasn't about simplifying the loyalty program. It was about making it possible to understand — so the people who needed to act on it actually could.

Back to
All case studies
Next case
Scaling a White-Label Banking Platform