1 of 4
Meet the playground
Why it exists
Patients don't see one version of a screen. What they see depends on their membership, the clinic they scanned at, whether they're new or returning, what was found, and where they are in their journey. Across more than 200,000 scans, that adds up to hundreds of thousands of possible states, far more than anyone can draw by hand.
For a long time we designed with static mockups. We'd start building. Engineering would find a case nobody had drawn, so we added a Figma frame. The ticket still linked the old one, and two months later nobody was sure which was right. Empty states, loading, errors, VIP and physician-first patients, clinics outside Health Cloud and international, critical cases... some situations get lost. We built this to be more intentional about who we design for and how we ensure their experience is solid end-to-end.
This playground is built on three principles:
- Check every path, not just the happy one. Each synthetic patient stands for real people in a real situation: a returning patient on their third whole body scan, an executive with a critical finding, a physician-first patient in London, a rescan after claustrophobia. They're our bias check. Switch patients and journey stops, and you see who a design works for and who it leaves out. We won't design for every patient, but we choose who we cover instead of forgetting someone by accident.
- Start from production, not from memory. Every kit is a copy of the real code, because designing from how we think the product works builds in wrong assumptions. The synthetic patients are shaped the same way: their records have the same fields and statuses a real patient's has, so what you see is what that patient would see. And if we don't know whether a design is feasible, it isn't done.
- Know why. Why something is the way it is matters, and it's hard to remember months later. So decisions document themselves as you work. Each project keeps its brief, decisions and critiques next to the prototype, and anyone can see why it looks the way it does.
Underneath all three are the five promises Prenuvo makes to patients. We hold our own work to them too, and the hub's Practices (opens another site) tab shows how.
How it works
A place where designers, PMs and engineers build working prototypes in code, mostly by talking to an agent (Claude or Cursor). A prototype starts as a copy of the real Prenuvo app, so it looks and behaves like production. You change only the part your idea is about, and everyone can see exactly what you changed.
Every prototype runs on the same named synthetic patients, at any point in their journey. They're who we design for: people who book a whole-body MRI scan, get it at one of our clinics and review their results, on the website, booking, the patient dashboard and the mobile app. Behind them are the staff who care for them: radiologists writing findings in the Findings Capture Tool, and clinic and care teams in Salesforce Health Cloud and the admin console. So instead of designing one happy path, you can check the same screen for Wallace Worried, Victoria VIP, Louise-Hélène Longitudinal, or any of their friends.
The patient journey
Every patient moves through five phases: Commit, Prepare, Scan, Review and Return. What they see in each depends on who they are, and some skip a phase entirely. Here is one synthetic patient's arc, from the journey explorer:
- CommitHeard about Prenuvo through her employer and a podcast. Booked the Comprehensive Membership through work.
- Prepare SkippedSkipped the bloodwork before the scan. She has a strong fear of needles.
- ScanWhole Body Scan in Las Vegas. Her third scan.
- ReviewOnly Minor (CSD-2) findings. Had a Results Review with a Prenuvo provider.
- Return SkippedSkipped the six-month bloodwork. Plans another scan next year.
A screen built for the common path would assume Louise-Hélène did her bloodwork. The journey explorer shows every synthetic patient this way, so you can see whose path a design has to hold up for.
Projects and kits
A project is one problem, such as "make the cart total clearer". It changes only what that problem needs, and borrows everything else from a kit.
A kit is a copy of one production surface. There's one for each:
- Dashboard
- Booking
- Mobile
- Findings Capture
- Admin console
- Health Cloud
- Comms
Every prototype carries the same small toolbar, so you can test any screen against any patient, at any point, in any design option:
Hi, WallaceLouise-HélèneSkye
Your scan · Thu, Jan 14Your scan · Thu, Jan 14Your scan · TomorrowScan done · Jan 14
8:00 AM8:00 AM8:00 AMResults soon
Prep · 3 stepsPrep · 2 steps leftPrep · 1 step leftPrep · all done
Try it
Done when
You've walked two synthetic patients through the journey explorer on the internal hub.
- Open the patient journey explorer (opens another site) on the internal hub. It works today, with your Google sign-in.
- Pick a synthetic patient and walk them through all five phases.
- Switch to another patient at the same stop, and look at what changes.
Once you have GitHub, the playground hub (opens another site) adds Meet the patients, with each synthetic patient's story, and the Practices tab on how we work.