Product & Strategy 8 projects

Other collectionsBuilt 3Claude in Daily Life 2Strategy Decks 2PRD Library 5

Product case study

Vyry Quest

Getting to the fun part of a campus quest sooner.

Two PM intern assignments on Vyry Quest 4.2, a multiplayer quest played on campus. Running it with two peers showed a loop that works but explains itself too late, so I ranked five fixes with DHM and wrote the PRD, then tried a hotspot in person.

  • Product Strategy
  • User Research
  • Onboarding
  • Prioritization
  • PRD
peers debriefed
2
bugs reported
6
issues ranked
5
personas
3
10 sections · 6 original artifacts

Brief

Assignment 1

Core loop evaluation

  • Run a Vyry Quest 4.2 quest as a three-person party
  • Ask two peers the same five questions afterwards
  • Summarise their answers, with a recording from each
  • Write a one-pager: PM analysis, peer insights and a reflection

Asked of each peer

Five questions

  • What felt intuitive, and what felt confusing
  • Whether the quest created togetherness or in-person collaboration
  • Moments of delight
  • Any slowdowns or unclear steps
  • What would have improved the experience

Assignment 2

Anchoring and hotspot, in person

  • Walk to a hotspot and find the Xfiti in AR
  • Reflect on the moment: what worked, what did not
  • Note a friend's reaction from the outside
  • Give one top suggestion, with media from the visit

Under ExtrasThe one-pager closes with three extras: a bug report on existing usability issues, a prioritization of the challenges to solve next, and a detailed PRD for fixing them. Sections 04 to 06 come from those.

The product

Term

Quest

A scavenger-hunt-like activity done by a small party. The PRD's primary users are university students in groups of three.

Term

Signal

What players record, and then go and find around campus. Signals are public: anyone in the same world can view them.

Term

Xfiti

The co-created output of a quest. After the hotspot visit I called it social digital graffiti: a digital artifact left in the real world.

Term

Beaming

The shared finale a quest builds toward, the payoff of the loop.

Term

Channels

Campus-specific or World. A party drawn from different universities may need World instead of its institute's channel.

Term

Hotspot

A place where players anchor an Xfiti, return later, decompose it, leave a dash signature and see who else has been there.

Pieced together from my own documents. A first-time player gets no such glossary, which became the main finding.

My read

PM analysis

Core loop strengths

The multiplayer quest has a real social core. Once the group understands the flow, it creates movement, coordination and a shared goal that feels different from a typical mobile app.

PM analysis

Friction points

The biggest issue is not the loop but activation clarity: what an Xfiti is, how to find the right quest, when to pick a campus channel over World, and why to care early on.

PM analysis

Top improvements

A 3-step onboarding layer before users act, and quest entry and next-step prompts that always answer: what do I do now, who am I doing it with, and how close am I to done.

What surprised meThe product's strongest value only appeared after we pushed through the weakest part of the experience. That usually signals a good underlying mechanic paired with weak onboarding, rather than a broken concept.

The ideaFive changes around Vyry Quest's loop, not to it, so a new user understands the quest in the first minutes: onboarding, quest routing, next-step guidance, Signal visibility and a focus mode.

01

Two exercises, one app

I ran a quest with two peers, then went to a hotspot in person, and wrote up what each showed.

The problem

02

A steep understanding gap

New users do not immediately understand what an Xfiti is, how Signals work or which quest type to choose, so the shared payoff arrives late.

The problem

03

Heard from the peers themselves

My notes and the two peers' own words show what felt intuitive and what stayed confusing until the group worked it out.

The research

04

Five issues, ranked

Five issues were rated on Delight, Hard to copy and Margin moving, and three rank P1 as one package.

The ranking

05

Five changes around the loop

Guided onboarding, clearer quest routing, persistent next steps, Signal visibility and a focus mode, none of them touching the core loop.

The five changes

06

One north star, proposed

Quest completion rate to Beaming, with four supporting metrics. All proposed, none measured.

The metrics

Problem

The problem

A steep understanding gap

New users do not immediately understand what an Xfiti is, how Signals work, which quest type to choose or what to do next. The social value is delayed, and they rely on group trial and error to progress.

The opportunity

Make the loop legible earlier

If users understand the what, why and what now of the quest in the first moments, the product surfaces its strongest value much faster: shared movement, coordination and a co-created payoff.

Why it matters to the business

User activation

Early confusion raises drop-off before the first moment of delight. Clearer onboarding should raise quest starts and the share of users who reach Beaming.

Differentiated experience

The moat is physical movement, multiplayer coordination and a shared payoff. If users cannot reach it smoothly, it stays hidden.

Retention and word of mouth

A cleaner first run should make users likelier to invite peers, replay quests and call the experience social, not confusing.

Operational efficiency

Clearer guidance should cut support questions and repeated explanation across universities and quest types.

Assumed throughoutThe quest mechanic is promising and the issue is activation clarity; cutting time-to-understanding in the first two minutes will lift starts, completion and delight; and simpler language, routing and guidance can ship without changing the core social mechanic.

Solutions

Proposed solutionWhat it doesPain points addressed
Guided first-run onboardingA 3-step layer that explains the quest goal, core terms and the shared Beaming payoff before users begin. Simple language first, branded language second.Unclear terminology, weak motivation to start, delayed understanding of product value
Quest routing and entry redesignMake the campus-specific or World choice explicit, simplify quest discovery, and state why a user is seeing each option.Difficulty finding the right quest, uncertainty about where to begin, group setup friction
Persistent next-step guidanceAt every stage, answer: what do I do now, who am I doing it with, and how close are we to completion?Mid-flow confusion, stalled progression, heavy reliance on peer interpretation
Signal visibility clarificationExplain clearly whether Signals are public, private, or shared within a world or quest context.Mismatched mental models and uncertainty around content visibility
Main-journey focus modeHide or de-prioritize distracting non-core surfaces during the primary activation flow.Cognitive overload and attention leakage during the first-run experience

Scope

A clearer first-run Vyry Quest experience in three parts. 01 Explain before action: teach Quest, Signal, Xfiti and Beaming in simple language before exploration begins. 02 Route the party correctly: clarify campus-specific versus World quests and keep all three members in the same flow. 03 Always answer what now: use persistent prompts and progress cues so users know what to do, with whom, and how close they are. Teach the vocabulary in sequence: Quest is a shared activity, Signal is public input in the world, Xfiti is a co-created output, Beaming is a shared AR payoff. Success measures: time-to-understanding (entry to basic comprehension), quest start-to-completion (first-time party progression), time-to-delight (entry to first emotionally meaningful shared win).
The first run, redesigned

Limits

Not a redesign of the mechanic

The PRD does not redesign the core quest mechanic; it improves activation and comprehension around it.

First run only

It does not solve long-term content depth, replay loops or community growth mechanics beyond first-run activation.

Quest design still matters

Some confusion may still come from quest design quality, not only UX clarity.

More iteration likely

Further iteration may be needed by campus type, party composition or quest complexity.

Trends

TrendWhat it meansWhere Vyry standsImplication
Low-friction onboarding expectationsUsers expect consumer products to explain themselves in seconds, not minutesDepends on peer deduction and experimentationFront-load orientation and shorten time to first success
Shared mechanics beat solo ones when the payoff is obviousGroup products work when roles, goals and progress are visibleThe shared payoff is strong, but not explained up frontMake collaboration visible before the first action
Plain language beats branded terms during activationNovel vocabulary can add identity later but adds friction on first useTerms like Xfiti and Signal are memorable only once understoodPair branded terms with simple explanations, or stage them
Contextual guidance beats static discoveryUsers learn faster from in-flow prompts than from searching across screensQuest discovery and next steps feel under-guidedUse what-to-do-now prompts inside the journey
Focus is critical during early activationNon-core information distracts while the primary job is still unclearFeature-request visibility and unclear screens add noiseReduce or hide distracting surfaces during the first-run flow

Borrowed from adjacent products

Borrowed fromWhat they doImpactOpportunity
Multiplayer mobile gamesExplain the objective, role and first win within the first minuteFaster activation and clearer motivationA lightweight tutorial that explains the group goal before exploration begins
Scavenger hunt and geolocation appsUse progress cues, nearby prompts and contextual nudgesFewer what-now momentsClearer waypointing, progress feedback and next-step prompts
Consumer onboarding practiceIntroduce one concept at a time instead of the full vocabularyLower cognitive load and higher completionTeach Quest, then Signal, then Xfiti and Beaming, in sequence
Collaboration toolsClarify who is involved and what each participant is expected to doShared accountability and togethernessShow party state, shared goal and progress at the top of the quest

Roadmap

PhaseTeamActivities and objectivesDependencies
1. Diagnose and defineProductMap the first 2-minute user journey, identify key drop-off moments and define success metrics for activationParticipant feedback, product observation, quest flow audit
DesignTranslate confusion points into revised onboarding copy, routing concepts and progress statesProduct problem statement
EngineeringAudit current quest entry points, event instrumentation and surfaces that can support prompts and tooltipsScope alignment with Product and Design
2. Design and specificationProductSpecify the onboarding sequence, quest selection logic and success eventsDesign concepts and engineering feasibility
DesignPrototype the first-run tutorial, route selection and in-flow guidance statesApproved feature scope
EngineeringBuild a lightweight onboarding framework and support for context-aware promptsDesign specs
3. Development and prototypingProduct and ResearchRun rapid usability tests with small student groups; compare time-to-understanding and completionWorking prototype
EngineeringInstrument funnel metrics across quest start, first Signal, Xfiti creation and BeamingPrototype integrated in app
4. Launch and initial rolloutProductShip to limited cohorts; monitor confusion signals, completion and qualitative feedbackStable release candidate
Growth and Campus OpsCollect campus-specific learnings and check whether World versus institute routing still confuses usersLaunch monitoring

Launch note

Launch PR note, as written in the PRD

Introducing a clearer first-run Vyry Quest experience

We are improving the Vyry Quest experience by making the first run easier to understand and easier to start. New onboarding will explain the quest goal, core terms, and shared payoff in simple language, while updated routing will help parties get into the right quest faster. We are also adding stronger next-step guidance throughout the journey so users always know what to do, who they are doing it with, and how close they are to completion. Together, these changes aim to reduce confusion, surface the social magic earlier, and increase quest completion without changing the core multiplayer mechanic.

The PR note is part of the exercise, written as if the changes had shipped. The PRD is my proposal, not a record of anything Vyry built.

Notes

4 notes

Felt intuitive

  • Recording Signals
  • Creating an Xfiti
  • Starting quests
  • Switching quests

Confusing · 5 of 10

Understanding the product

  • No tooltips or walkthrough to show what needs to be done
  • Core features not explained in a timely manner
  • Not understanding what an Xfiti is to begin with
  • Not knowing that Signals are public
  • No clear motivation to complete a quest

Confusing · 5 of 10

Finding and finishing a quest

  • Not able to find quests
  • Unable to start a UT Austin specific quest
  • Difficult to complete a World quest
  • A list of users, with nothing to say what to do with it
  • Feature requests behind the top-right icon, which a player does not need to see

Togetherness?Yes, once we figured out what to do.

Moment of delightOnce we figured out what needed to be done: going around places trying to find the signals.

My notes from the two peers who ran the quest with me, plus my own run. A sample of two: directional, not a measurement. Open the notes (PDF, opens in a new tab).

Quotes

My overall experience with the Vyry quest started out a little confusing, but once our group understood the flow, it became much more engaging. A few things felt intuitive, like recording signals, creating the Xfiti, and moving between quests once we knew where to go. The most enjoyable part for me was actually walking around together trying to find the signals, because that was the moment when the product started to feel social and different from a normal app experience. I also liked that the end goal felt shared instead of individual. Where I struggled most was in the beginning, because the app did not explain what an Xfiti was, how quests were supposed to work, or why I should care right away. I think a short walkthrough and clearer guidance on the first few steps would make the experience much smoother and help users reach that fun collaborative part much faster.
Peer 1
For me, the biggest issue with the Vyry quest was not the core idea, but the clarity of the early experience. The concept became interesting once we figured it out as a group, and at that point it did create a real sense of togetherness because we had to coordinate in person and work toward the same outcome. But the app made us do too much interpretation on our own. I was not sure what an Xfiti meant, I did not immediately understand that signals could be public, and it was not always obvious how to find or start the right quest, especially campus-specific versus World quests. I also found some screens distracting, like seeing things such as feature requests during the main journey. The product has a strong collaborative mechanic underneath it, but I think it needs simpler language, better onboarding, and clearer next-step prompts so users do not get stuck before the delight actually begins.
Peer 2

Each peer's statement in full, as it appears in my documents. Quoted without names; a sample of two.

Journey

Vyry Quest core loop, as four steps: 01 Join the same quest (3-person party), 02 Record Signals (shared IRL inputs), 03 Create Xfiti (co-created output), 04 Beaming (shared AR finale). Under it, the observed emotional journey in three steps. Confusion: unclear terminology, quest discovery and first actions. Coordination: the group aligns and starts moving together. Delight: finding Signals and progressing toward a shared outcome. PM synthesis: the primary issue is activation clarity, not the underlying multiplayer mechanic. The highest-leverage opportunity is to reduce time-to-understanding before the first collaborative action.
Core loop and journey

Bugs

Bug 01

App launch

Sometimes, even on a strong connection, the app does not open: a short error toast and a black screen, which can leave the user confused.

Bug 02

Create quest

Create quest does not work.

Bug 03

Signal visibility

Nowhere is it shared that Signals are public in nature.

Bug 04

Quest list

Scrolling through quests lags at the bottom of the screen.

Bug 05

Challenge readout

The quest challenge readout is too robotic.

Bug 06

Beaming

Beaming existing Xfitis does not always render.

Personas

Three roles shape the quest experience. Primary, Student Participant. Job: understand the experience quickly, join the right quest, and complete it without external explanation. Needs: clear explanation of the quest, Xfiti, Signals and what to do next. Worries: not understanding the product or dropping before the fun part begins. Primary, Party Organizer / Inviter. Job: get everyone into the same quest instance and keep the group moving toward the shared payoff. Needs: routing guidance, strong progress cues and reassurance that the party is in the correct flow. Worries: choosing the wrong quest or becoming the unofficial explainer. Secondary, Campus Growth / Community Lead. Job: drive successful first experiences that can scale through word of mouth and repeat participation. Needs: visibility into drop-off, confusion and the improvements that increase activation. Worries: strong core value being hidden by early friction and external explanation.
Three roles

From the PRD: personas based on the assignment brief, direct product observation and recurring pain points in the peers' feedback.

Jobs to be done

Primary

Student Participant

  • Figure out what the product is
  • Join and progress through a quest
  • Enjoy a shared in-person experience with friends
  • Decide whether this is worth doing again

Coordinator

Party Organizer / Inviter

  • Select the right channel or quest
  • Help all members enter the same flow
  • Keep the group progressing
  • Make sure the group reaches the shared end state

Secondary

Campus Growth / Community Lead

  • Identify the highest-friction points in activation
  • Improve clarity without killing novelty
  • Increase quest completion and replay
  • Enable campus-scalable onboarding

Ranking

Biggest pain pointActivation clarity. Both peers struggled to understand what an Xfiti is, how to find or join the right quest, what to do first, and why the experience matters before the collaborative payoff appears.

Activation issues, prioritized with DHM, as a table of Delight, Hard to copy and Margin moving ratings, a priority and a proposed product change. Unclear onboarding and terminology: High, Medium, High, P1 High; a 3-step first-run walkthrough with plain-language definitions. Weak quest discovery and routing: High, Medium, High, P1 High; clear routing logic, eligibility copy and default recommendations. No clear next-step guidance during the quest: High, Medium, High, P1 High; persistent next-step prompts, progress states and completion cues. Signals visibility is ambiguous: Medium, Low, Medium, P2 Medium; education on signal visibility at creation and discovery. Distracting surfaces in the main journey: Medium, Low, Low, P3 Medium/Low; remove or hide non-essential surfaces from the primary quest journey. Key metrics: time-to-understanding in the first 2 minutes, first-time party quest start-to-completion, drop-off before the first collaborative action.
Issues ranked with DHM

The ratings are the table's; the proposed changes are shortened here, and why each issue ranks where it does is in the document. The PRD's shorter table rates next-step guidance Medium on margin, and its priority is High in both. Open the table (PDF, opens in a new tab).

DHM

D

Delight to customers

How much the solution enhances user experience and satisfaction.

H

Hard to copy

The level of difficulty competitors would face in replicating the solution.

M

Margin moving

The potential impact of the solution on revenue generation or cost savings.

How priority followsHigh priority scores high across all three; medium is a mix of high and medium; low scores lower on one or more. Here priority reflects both how severe the pain is and its leverage on quest completion.

SequencingShip the three P1 items together as the activation package for the next release. Then address signal visibility and distraction cleanup as secondary clarity improvements.

Objective of the launchReduce time-to-understanding and increase the share of users who reach the first collaborative payoff.

North star

  • Quest completion rate to Beaming, the shared finale: a direct measure of whether users reach the product's core payoff

Level 1

  • Quest start rate after landing on quest entry: improved activation at the top of the funnel
  • Time to first meaningful action: whether onboarding reduces hesitation

Level 2

  • Drop-off rate before the first Signal or Xfiti action: confusion in the early stages
  • User-reported clarity score after the first quest: whether the product feels understandable, not just usable

GuardrailWhat must not get worse

  • Support and feedback mentions of unclear terminology or routing: the core pain point is actually shrinking
  • Completion time inflation: added guidance does not make the journey feel heavier

Proposed metrics from the PRD's KPI pyramid, not measured results.

Two terms the PRD defines

Activation clarity

How quickly a new user understands what the product is, why it matters and what to do next.

Time-to-delight

The time between entry and the first emotionally meaningful shared win.

Finding an Xfiti at a campus hotspot

Stills from my own screen recordings. The app is Vyry's product, not my design.

1 / 5

Step 01

Hotspots near me

The campus map opens on a card: no hotspot yet, create an Xfiti and be the first to drop one on a hotspot. A lime marker on the map reads 3.

  • CardNo hotspot yet! Create an Xfiti and be the first to drop one on a hotspot.
  • ActionJoin quest

An excerpt of my 67 s recording, cut where nobody is in frame. The app is Vyry's product, not my design.

Clip · 12.9 s, no sound

The Xfiti, close up

Standing in the street, I move toward the Xfiti until it fills the screen, then back, and a tray of other Xfitis appears along the bottom.

Stays on screen

One instruction, throughout

Move your phone to detect the ground stays over the Xfiti from the first frame to the last, even after the Xfiti is in place.

Reflection

What worked

The walk was part of it

Walking to the hotspot felt like a meaningful part of the experience rather than friction: it made the product feel physical, social and location-based, not like another mobile app interaction.

What did not land

The moment was not magical yet

I needed clearer cues on what to look for, what decomposition meant and what had changed after I interacted with the Xfiti. I also could not work out the interactions needed to complete a dash signature.

Strongest feeling

Social digital graffiti

Someone had left a digital artifact in the real world and I could discover it later. The earlier quest output was now connected to an actual place.

Would I do it again?Yes, if the hotspot had stronger context, clearer instructions and a more obvious emotional or social payoff after decomposition.

A friend, watchingInteresting from the outside, because the phone felt connected to the physical place; slightly awkward at moments, because I was scanning around without knowing whether I was doing the right thing.

The fix

Hotspots extend the experience beyond quest completion, as six steps: 01 Anchor, leave an X-Fiti at a physical place; 02 Return, revisit or discover a campus hotspot; 03 Reveal, scan to find what is present; 04 Decompose, interact with the anchored X-Fiti; 05 Sign, leave a dash signature; 06 Connect, see or lightly connect with prior contributors. Recommended hotspot arrival mode: What is here? Show how many X-Fitis are present. What can I do? Scan, reveal, decompose, leave a dash signature. What do I unlock or leave behind? Make the emotional and social payoff explicit. Why Hotspots matter: Retention, a reason to revisit physical places after quest completion. Identity, a visible artifact or signature left in the world. Community, others can discover, decompose and build on prior activity.
Hotspot loop and arrival mode

Example copy, from my write-up

You've found 3 X-Fitis here.

Scan to reveal, decompose it, and leave your dash signature. It would reduce uncertainty and make the in-person moment feel intentional instead of exploratory in a confusing way.

Also suggested

Meet who was here

A way to connect directly with the players who invested time in placing Xfitis at the hotspot, to create a feeling of community.

Concept note

Overall viewHotspots are worth having because they give Vyry a strong loop after the Xfiti. Without them the experience risks ending right after creation; with them the Xfiti lives in the real world, can be discovered by others and can pull users back into the app.

Closest existing behaviorSimilar in spirit to Pokémon Go gyms, with more emphasis on co-creation, social discovery and campus belonging. A hotspot should make users curious enough to go there, interact, and feel connected to the people who were there before them.

A hotspot must answer

Why should I walk there?

A hotspot must answer

What will I find?

A hotspot must answer

What happens after I interact with it?

RecommendationA strong idea for after an Xfiti is created, whose value needs to be made clearer. If Vyry answers those three questions, hotspots could become the bridge between one-time quest completion and repeat, real-world engagement.

The note in full: open the concept note (PDF, opens in a new tab).

Original artifacts6

Source documents as written; the PRD has only the targets of its Google links removed. Each is linked from the section it supports.

Download the original documents (zip)
Next in Product & Strategy · 8 of 8LinkedIn Priority AppsApplying is free, so intent is noise: a scarce, refundable slot, wireframes and an experiment.Next project

Sections 10

Original artifacts6