Mithril Consulting | Client: Ticketmaster Agent: Galadriel (Lead Designer) Slogan: "See what could be." Date: 28 April 2026 Document type: Delta Memo — extends the Iteration 11 design with the Octalysis Framework consolidated as a Fan Loyalty Engine across the eight sanctioned journey moments (G1–G8).
I have received Saruman's Iteration 12 Research Brief and Aragorn's Review 1 approval. The Iteration 11 design canvas — all-in pricing with the Fair Price Indicator tooltip, personalised discovery with a social layer, ARIA with human escalation, the Confirmation screen, and the "Your Year in Live" retrospective — is retained without modification.
The single substantive direction I have been asked to act on is Focus Area 5: apply the Octalysis Framework (Yu-kai Chou, 2015) to consolidate the existing social and post-event features into a coherent Fan Loyalty Engine that sits across the customer lifecycle, and design Octalysis Core Drives onto each of the eight journey moments Saruman has sanctioned (Opportunities G1–G8). Saruman has flagged where and why — Core Drive selection and mechanic shape are mine to determine, within the binding ethical constraints he has laid out.
Three findings shaped this design pass most:
Retained from Iteration 11: "When a customer opens the Ticketmaster app, they should feel the same trust they feel when a knowledgeable friend recommends a show — and after the show, they should feel like part of a community that celebrates live music together."
Extended for Iteration 12: "...and across that whole relationship, the platform should remember them — recognising the fan they are becoming, not just the ticket they are buying."
The product evolves from a transactional search tool (Iterations 1–9) → a trusted companion (Iteration 10) → a social platform (Iteration 11) → a fan-relationship platform with continuous memory (Iteration 12). The customer is no longer re-entered at zero on every visit. Their attendance, status, and contribution to the wider fan community become legible to them and to the platform.
Principles 1–6 from Iteration 11 are retained:
One additional principle is added for Iteration 12:
The Fan Loyalty Engine is the visible product surface that consolidates Iteration 11's social and post-event features into a coherent lifecycle architecture. It is what makes Problem 10 (purely transactional engagement) addressable.
Every customer has a Fan Profile. It is the persistent identity layer that the rest of the engine reads from and writes to. A Fan Profile is composed of:
Four tiers, named to feel like recognition rather than corporate loyalty banding:
| Tier | Threshold (illustrative — Aragorn / Ticketmaster commercial to confirm) | What unlocks |
|---|---|---|
| Newcomer | 0–1 events attended | Welcome content; first-show recognition badge; basic recommendations |
| Regular | 2–5 events / year | Personalised pre-event content; presale notifications for genres they attend |
| Devoted | 6–14 events / year | Verified-fan presale eligibility for relevant artists; richer post-event recap; "concert companion" suggestions for group booking |
| Lifer | 15+ events / year or 50+ lifetime events | Highest verified-fan presale priority; lifetime "Year in Live" archive; founding-fan invitations to artist-direct moments where available |
Critical design decisions on the ladder:
The Fan Loyalty Engine surfaces appear at the eight sanctioned journey moments. Each surface carries the EU AI Act Art. 50 disclosure where AI personalisation is in use. Each surface degrades to a sensible non-personalised default if the user has opted out of profile-driven features.
For each of Saruman's Opportunities G1–G8, this section names the Core Drive(s) selected, the journey phase, the White/Black Hat balance, and the design decision. The full table appears in §10 (Octalysis Design Rationale).
Core Drives selected: CD7 (Curiosity), CD5 (Social), CD1 (Meaning), light CD3 (Creativity through personalisation choice). White / Black Hat: White Hat dominant. CD7 used only to surface delight (a "you might love this" reveal), never to manufacture compulsion. Design decision: The Home feed is reorganised into four named sections — Because you went to [past event], Friends are going, Fits your fan profile, New in [your city]. Each section header carries a one-tap "Why am I seeing this?" affordance that opens a plain-language explanation. The "Friends are going" section appears only if the user has opted into social features.
Core Drives selected: CD2 (Accomplishment — fan tier earned through attendance), CD4 (Ownership — your fan history is your verification), CD5 (Social — fan-of-this-artist community), CD6 (Scarcity — presale window, used truthfully). White / Black Hat: White Hat foundation (recognition); CD6 used only because presale windows are genuinely time-bounded. Design decision: A new screen — Fan Presale — appears when an artist the customer has previously attended announces a tour. It shows the user's verified fan history with that artist ("You've seen Hozier 3 times. You qualify for the Fan Presale on Tue 5 May, 9am."), a calendar reminder action, and a transparent explanation of how presale eligibility is determined. The presale countdown is real, the eligibility is real, and the rationale is one tap away.
Core Drives selected: CD2 (Accomplishment — productive use of queue time), CD3 (Creativity — seat preference selection while waiting), light CD5 (you and N others are in the queue with you, framed neutrally). White / Black Hat: White Hat only. No Black Hat mechanics in the queue. No "if you leave you lose your place" beyond the literal queue mechanic; no "tickets selling fast" overlay during wait. Design decision: The Smart Queue surface (designed in Iteration 11) is extended with three productive in-queue actions: (a) lock seat preferences (price ceiling, area, seated/standing) so checkout is one tap, (b) verify payment method, (c) view the venue map. The queue progress shows literal position, an estimated wait, and a price-guarantee ("the price you saw on entry is the price you pay") banner. Anxiety mechanics are deliberately absent.
Core Drives selected: CD1 (Meaning — "you're going"), CD4 (Ownership — your commemorative ticket artefact), CD2 (Accomplishment — milestone badge if applicable), CD5 (Social — invite friends). White / Black Hat: White Hat only. Design decision: The Confirmation screen (designed in Iteration 11) is extended with a Commemorative Ticket Artefact — a designed, savable, shareable digital ticket card carrying the event identity, the user's tier, and (where relevant) a milestone badge ("Your first show!" / "Your 10th show!" / "Your first show at this venue!"). This artefact lives in the Fan Profile under "My Shows." The Confirmation screen also retains the "Invite Friends" and "Add to Calendar" actions from Iteration 11, with the addition of "Save commemorative ticket."
Core Drives selected: CD3 (Creativity — make a setlist wishlist; share what you want to hear), CD5 (Social — see who else is going, group chat), CD7 (Curiosity — staggered drops of pre-event content), light CD1 (artist-direct messages where available). White / Black Hat: White Hat dominant. CD7 used for delight (mystery support act announcements, content drops), never as a monetised loot mechanic. Design decision: A new in-app surface — Pre-Event Hub — appears in My Tickets for any upcoming event in the next 30 days. It carries: (a) a setlist wishlist tool (CD3), (b) a venue logistics card (parking, gates open, accessibility) (CD2 — productive preparation), (c) a "Friends going" list with optional group chat via ARIA (CD5), (d) staggered content drops where the artist makes them available (CD7 — used for joy not for compulsion), (e) the Ticket Fairy-style ambassador mechanic for users who want to invite friends (CD5+CD2 — see G2 referrals).
Core Drives selected: CD2 (Accomplishment — your show-attendance count visible), CD4 (Ownership — your ticket, your tier), CD5 (Social — see who else from your network is at the show). White / Black Hat: White Hat only. No friction added to the gate-entry path. All gamification is additive and optional. Design decision: The Event-Day flow keeps the existing Iteration 11 ticket display as the primary action — barcode visible immediately, no extra taps. Below the barcode (only after the user scrolls), an optional "At the show" surface exposes: (a) tier-status display ("You're attending as a Devoted fan"), (b) a "Friends here" tile if friends have also opted in, (c) a venue check-in moment that adds the show to the user's attendance graph the moment they scan in (no user action required).
Core Drives selected: CD1 (Meaning — "you were there"), CD3 (Creativity — share what the show meant to you), CD4 (Ownership — the show now lives in your collection), CD5 (Social — see what friends thought). White / Black Hat: White Hat only. No Black Hat mechanics anywhere in the post-event window. The customer is in a peak emotional state; anything anxiety-inducing here would be grotesque. Design decision: The Iteration 11 post-event recap is consolidated into a Show Memory card that arrives via push within 4 hours of the event ending. The card carries: the commemorative ticket artefact (now stamped "attended"), a private 1-tap "How was it?" mood input (1–5 plus optional text), a "Friends who were also there" list (opt-in), 2–3 "you might love" recommendations grounded in the show's genre, and a "Share your night" action that produces a tasteful, branded shareable card. The "How was it?" input is private by default — never shown to the artist or venue without explicit permission.
Core Drives selected: CD1 (Meaning — your year as a story), CD4 (Ownership — your lifetime concert collection), CD3 (Creativity — your artefacts, your way), CD5 (Social — share your year, see your concert companions). No CD8. White / Black Hat: White Hat only. The lapsed-fan loop must never use loss-avoidance threat language. Design decision: The "Your Year in Live" retrospective (designed in Iteration 11 as Screen 9) is retained and now sits within the Fan Profile as a permanent annual archive — the user can revisit prior years, build a multi-year live-music identity, and share any year. For lapsed fans, the re-engagement surface is a welcome-back card ("We've missed you. Three artists you've followed are touring near you.") — never a "you're about to lose your status" mechanic. Status, once gained, is permanent.
Iteration 11 Solution Concepts 1–4 are retained:
One additional Solution Concept is added:
Problem (from Saruman): Problem 10 — purely transactional engagement architecture; carrier for Problems 7 (no social layer) and 8 (no post-event engagement). Solution concept: A persistent Fan Profile, four-tier Fan Status ladder, Fan Artefact collection, and personalised Fan Surfaces at each of the eight sanctioned journey moments — all working as one coherent lifecycle architecture rather than as a bolt-on points programme. Why this works (evidence basis): Saruman §6 competitive landscape — Ultra Passport, Manchester United, Sephora, Starbucks, Spotify Wrapped all evidence that a coherent identity-and-recognition layer drives 30–60% engagement gains and meaningful retention uplift. No primary ticketing platform has yet implemented this comprehensively (first-mover opportunity). How AI enhances it: Recommender System (the personalisation surface for discovery, pre-event content, post-event recommendations, lapsed-fan re-engagement) + Intelligent Agent extension (proactive lifecycle nudges via ARIA — "your favourite artist just announced a tour"). Not a chatbot.
Iteration 11 Screens 1–10 are retained. The following are new or refined for Iteration 12:
Layout: Single-column, mobile (375px). Top: optional avatar + display name + tier badge ("Devoted · 8 shows this year"). Below: four collapsible sections — My Shows (chronological attendance list with commemorative tickets), My Status (current tier, what unlocks at each tier, how thresholds work, link to "How do tiers work?"), My Artefacts (milestone badges, Year in Live cards), Privacy & Data (granular toggles, export, delete). Interaction: Tap any past show → opens that show's commemorative ticket and Show Memory. Tap "How do tiers work?" → opens explanatory modal. Tap any Privacy toggle → state change is immediate; no save button needed. States: Default (returning user with attendance history), Newcomer (no shows yet — shows "Your fan story starts here" + nearest upcoming events), Lapsed (no recent shows — shows welcome-back card, never a downgrade threat). Accessibility: All tier badges and milestone badges have text labels for screen readers. Toggle states announced. WCAG 2.2 AA contrast on all tier-badge colours.
Layout: Hero with artist image; user's verified history with that artist ("You've seen Hozier 3 times — qualifying you for Fan Presale"); presale countdown (real, accurate); a one-tap "Set reminder" action; a transparent "How does Fan Presale work?" link. Interaction: Tap "Set reminder" → adds calendar event + push notification scheduled. Tap "How does Fan Presale work?" → opens explanation modal. States: Eligible (default, with countdown), Eligible — presale live (CTA changes to "Enter presale"), Not eligible (shows what would qualify, with no pressure), Past (shows the user got a ticket if they did, or did not if they did not). Accessibility: Countdown is text-readable, not just visual; presale window also stated as absolute date/time for users with disabled animations.
Layout: Card stack within My Tickets → upcoming event detail. Cards in order: Setlist wishlist (CD3), Venue logistics (CD2), Friends going + group chat (CD5, opt-in), Pre-event content drops (CD7), Invite a friend (Ticket Fairy-style referral, CD5). Interaction: Setlist wishlist — drag-and-drop or tap-to-add favourite tracks; visible only to the user unless explicitly shared. Group chat — opens ARIA in group mode. Invite a friend — generates a referral link; if the friend buys, both users get a small thank-you (recognition, not discount-led). States: Default (event 30+ days away — content sparse), Anticipation rising (event within 7 days — more cards visible), T-1 (final logistics surfaced), Live (transitions into Event Day flow). Accessibility: Setlist wishlist has both drag and tap-to-add interactions; all cards keyboard-navigable; group chat inherits ARIA's existing accessibility.
Layout: Full-screen card on first open. Top: commemorative ticket artefact ("attended" stamp); below: "How was it?" 1–5 input (private by default, with explicit toggle to share); "Friends who were there" tile (opt-in); 2–3 "you might love" recommendations; "Share your night" action that opens a tasteful, branded share sheet. Interaction: Mood input — single tap on a star, optional text. Share — opens system share sheet with branded image attached. States: Default (event in last 72 hours, fresh recap), Archived (after 72 hours — moves into the show's permanent record in the Fan Profile under My Shows). Accessibility: Mood input is keyboard-accessible; share image has alt text for screen readers; no auto-playing media.
Iteration 11 AI Features 1–4 are retained:
One additional AI feature is added (consolidating and extending Feature 4):
What it does for the user: Maintains the persistent Fan Profile and serves the personalised surface at each sanctioned journey moment — Discovery sections, Fan Presale eligibility, Pre-Event Hub content, Show Memory recap, Year in Live, lapsed-fan welcome-back. AI system type: Primarily a Recommender System (collaborative + content + social filtering against the attendance graph). Extended by an Intelligent Agent capability via ARIA for proactive lifecycle nudges. Explicitly not a chatbot. Data needed: Attendance history (already held by Ticketmaster for transactional purposes), user-supplied preferences from onboarding, friend graph (opt-in only), event metadata (genre, artist, venue), location (opt-in). What it shows the user: Tier status, milestone badges, personalised recommendations explained in plain language, "Why am I seeing this?" affordance on every personalised surface, EU AI Act Art. 50 disclosure on each surface, granular controls in the Privacy & Data section of the Fan Profile. When it fails or is unavailable: Surfaces degrade to non-personalised defaults. The Home feed falls back to a chronological "What's on near you" list. The Fan Presale screen states clearly: "Personalisation unavailable — please try again later." The user is never blocked from buying a ticket because the engine is down. Privacy: Loyalty engine functions only with explicit consent. Fan Profile and attendance graph deletion is one tap from the Privacy & Data section, with a 30-day completion window in line with GDPR Art. 17 expectations. No vulnerability-targeting logic — the engine has no inputs that signal user financial, emotional, or attentional state, and it is explicitly prohibited from timing nudges to exploit such signals (binding constraint per Saruman §8.1 / EU AI Act Art. 5).
Iteration 11 accessibility requirements are retained in full. The following additions apply to the new screens:
Per the Iteration 12 system prompt, this table maps every gamification-bearing Solution Concept to its activated Core Drive(s), the journey phase it targets, the White/Black Hat balance, and the design intent. No Solution Concept activates a Black Hat drive without an explicit transparency-and-truthfulness condition stated in the Design Intent column.
| Feature | Core Drive(s) | Phase | White / Black Hat | Design Intent |
|---|---|---|---|---|
| Home — Because you went to / Friends are going / Fits your fan profile / New in your city (G1) | CD7, CD5, CD1, CD3 | Discovery | White Hat (CD7 used only for surface delight) | Convert opaque algorithmic discovery into transparent, fan-relevant curation; "Why am I seeing this?" on every section |
| Fan Presale screen + presale countdown (G2) | CD2, CD4, CD5, CD6 | Discovery → Onboarding | White Hat foundation; CD6 used only because presale windows are genuinely time-bounded | Recognise fan history as the basis for verified-fan presale; presale window is real, eligibility is explainable, countdown is accurate |
| Smart Queue + in-queue productive actions (G3) | CD2, CD3, CD5 (neutral) | Onboarding | White Hat only — no Black Hat mechanics in the queue | Make the most anxious moment in the journey feel productive and fair; keep Iteration 11's price-guarantee promise visible |
| Confirmation + Commemorative Ticket Artefact + tier micro-feedback (G4) | CD1, CD4, CD2, CD5 | Onboarding | White Hat only | Convert a transactional receipt into an identity-affirming moment; tier feedback shown only to the user, never as pressure |
| Pre-Event Hub — setlist wishlist (G5) | CD3 | Scaffolding | White Hat ("Golden Corner") | Creative expression sustains engagement during the dead window without requiring a transaction |
| Pre-Event Hub — Friends going + group chat (G5) | CD5 | Scaffolding | White Hat | Opt-in social presence; ambient motivation, never broadcast |
| Pre-Event Hub — content drops (G5) | CD7, light CD1 | Scaffolding | White Hat (CD7 used for delight, never monetised) | Mystery support-act / artist content as a delight surface, not a loot mechanic |
| Pre-Event Hub — referral mechanic (G5) | CD5, CD2 | Scaffolding | White Hat | Ticket Fairy precedent; both inviter and friend recognised, never via discount-led pressure |
| Event-Day Attend — additive identity surface (G6) | CD2, CD4, CD5 | Onboarding (event) / Endgame (platform) | White Hat only | All gamification additive and below the fold; barcode-first; venue check-in adds to attendance graph silently |
| Show Memory — commemorative artefact + mood input + recommendations (G7) | CD1, CD3, CD4, CD5 | Endgame | White Hat only | Customer is in a peak emotional state; mood input is private by default; share is tasteful, never demanded |
| Year in Live retrospective + permanent annual archive (G8) | CD1, CD4, CD3, CD5 | Endgame | White Hat only | Multi-year fan identity; lifetime collection; shareable but never required to share |
| Lapsed-fan welcome-back card (G8) | CD1, CD5 | Endgame | White Hat only — explicitly no CD8 | Welcome, never threat; status is gained, never lost; no "you're about to lose" framing anywhere |
| Fan Status ladder (Newcomer → Lifer) | CD2, CD4 | All four phases | White Hat — status only gained, never lost | Recognition for being a fan; thresholds visible and explainable; tier framing owned by Pippin |
Aggregate balance: Of 13 design concepts in the table, 13 lead with White Hat. CD6 is used in exactly one (G2 presale), only because presale windows are genuinely time-bounded. CD7 is used in three (G1, G5 content drops, ambient on G5 hub) — only as delight, never as monetised compulsion. CD8 (Loss Avoidance) is used in zero design concepts. This is the deliberate inverse of the current Ticketmaster product (which activates CD6 and CD8 only, both at the customer) and is the core ethical position of the Iteration 12 design.
All Iteration 11 non-negotiables remain (all-in pricing, AI disclosures, ARIA human escalation, queue price guarantee, social features default OFF, Fair Price tooltip, Confirmation screen, real images, info panel beside phone frame). The following Iteration 12 additions are also non-negotiable:
─── HANDOFF TO ARAGORN FOR REVIEW ─── Agent: Galadriel (Designer) Passing to: Aragorn (Managing Consultant) for Review 2 / quality gate Summary: I have consolidated Iteration 11's social and post-event features into a coherent Fan Loyalty Engine — Fan Profile, four-tier Fan Status ladder, Fan Artefacts, and personalised surfaces at each of Saruman's eight sanctioned journey moments (G1–G8). Four new screens (Fan Profile, Fan Presale, Pre-Event Hub, Show Memory) and one new bottom-nav tab (Profile). One new AI Feature (Fan Loyalty Engine). The Octalysis Design Rationale table in §10 is the binding contract for Gimli — 13 design concepts, all leading with White Hat; CD6 used once (truthfully); CD7 used as delight (never as loot); CD8 used zero times. This is the deliberate inverse of Ticketmaster's current product.
Design priorities for Gimli (build order):
Non-negotiable decisions: Profile tab exists; Status only gained; no CD8 mechanics; every personalised surface has Art. 50 disclosure + "Why am I seeing this?"; Fan Presale countdown real; Show Memory mood input private by default; gamification built as working UI.
Flexible areas: Tier thresholds (illustrative), pre-event content depth, setlist wishlist depth, lapsed-fan copy, multi-year Year in Live archive UI, commemorative ticket visual template.
Ready for review: YES
Last edited: 29 April 2026