Patient Sense
Patient Sense
A proof of concept that redesigned the workflows (Access Solution and Voice of Customer) inside a live patient data platform, replacing blank charts and unclear next steps with personalised, actionable insight.
Role
UX Researcher
Product Designer
Team
Design Director
Life Sciences Director
Data and AI Lead
Timeline
2023 - 4 weeks
Full Time
OVERVIEW
Pharma companies run several teams to support patients, from getting insurance approved to collecting feedback. Each team worked in its own tool, charts broke if they weren't set up correctly, and nothing suggested what to do when a problem showed up.
PatientSense becomes: one shared home where every team sees the whole picture, opens into views built for its own questions, and gets a suggested next step.
MY ROLE
I led design on the proof of concept. I ran co-design workshops with the SME, shadowed support analysts, defined the recommendations, and designed the Access Solution and Voice of Customer workflows end to end.
1.
Turned dense hundreds of row of raw data counts into visual formats, each shaped around the specific story that team's data needed to tell.
2.
Closed the gap between insight and action - next step exists the moment a problem is spotted, instead of a dead end.
3.
Reduce cohort-to-individual navigation down to a couple of clicks, with no filters to rebuild between the cohort lens and the individual lens.
Patient Sense
A proof of concept that redesigned the workflows (Access Solution and Voice of Customer) inside a live patient data platform, replacing blank charts and unclear next steps with personalised, actionable insight.
Role
UX Researcher
Product -
Service Designer
Team
Design Director
Life Sciences Director
Data and AI Lead
Timeline
2023 - 4 weeks
Full Time
OVERVIEW
Pharma companies run several teams to support patients, from getting insurance approved to collecting feedback. Each team worked in its own tool, charts broke if they weren't set up correctly, and nothing suggested what to do when a problem showed up.
PatientSense becomes: one shared home where every team sees the whole picture, opens into views built for its own questions, and gets a suggested next step.
MY ROLE
I led design on the proof of concept. I ran co-design workshops with the SME, shadowed support analysts, defined the recommendations, and designed the Access Solution and Voice of Customer workflows end to end.
1.
Turned dense hundreds of row of raw data counts into visual formats, each shaped around the specific story that team's data needed to tell.
2.
Closed the gap between insight and action - next step exists the moment a problem is spotted, instead of a dead end.
3.
Reduce cohort-to-individual navigation down to a couple of clicks, with no filters to rebuild between the cohort lens and the individual lens.
Why Patient Sense?
Why Patient
Sense?
A pharma company runs several teams to support patients on its medicines. One helps them get insurance approved. One collects their feedback. Others handle education, free medication and medical questions. All of them draw on the same patient data. In 2023, the tools they used each covered only one slice of it.


They didn't lack data.
They lacked a way to
read it and act on it.
They didn't lack
data.They lacked
a way to read it
and act on it.
A market scan showed that every tool covered only one slice of patient support. With the scope set on Access Solution and Voice of Customer, I ran co-design workshops with the SME for Access Solution. For Voice of Customer, I audited the feedback forms and benchmarked customer-experience tools. Shadowing the SME and support analysts showed where the work broke down day to day.
Research, as a sole designer
I had to understand market trends, workflows and data.
Access Solution
Market Research
I looked at the tools each team used. Every tool covered one slice: feedback, case work or insurance access. None I found gave the teams a shared view.
Co-design workshops with SMEs
I worked with the SME to map which numbers the team relies on to make decisions: denials, prior authorisations and turnaround times.
Voice of Customer
Survey form audit
I went through the feedback forms end to end: branching, role-based questions, satisfaction scores. The forms collected good data. The trouble started after collection, when scores sat in raw tables that took effort to read.


Customer-experience tool benchmark
I compared how leading tools show sentiment, channel response and where patients drop off. The best ones made data easy to scan and suggested a next step. Both were missing here.
Shadowing the SME and analysts
I watched them work in the existing tools. If one value was entered wrong at the source, the chart came up blank. Moving from a patient group to a single response meant rebuilding filters every time. They also said patients had to repeat themselves from team to team.
Insights
Making sense of the research.
1.
The data was fine. Getting it on
screen was the problem.
The data was fine.
Getting it on screen was
the problem.
➔
The feedback forms collected good data. But charts only appeared if someone set them up correctly, and one wrong value at the source meant a blank screen.
➔
2.
Each team asks a different
shape of question.
Each team asks a
different shape of
question.
➔
Access Solution thinks in layers: therapeutic area, then product, then patient group. Voice of Customer thinks in flows: which channel feedback came from, and how satisfied the patient was.
➔
3.
Work happens at two levels, and
switching between cost time.
Work happens at two
levels, and switching
between cost time.
➔
Analysts spotted patterns across groups but acted on single cases. Every move from one level to the other meant rebuilding filters from scratch.
➔
4.
Seeing a problem isn't the same
as knowing what to do.
Seeing a problem isn't
the same as knowing
what to do.
➔
The best customer-experience tools suggested a next step. Making passive to active decision making.
➔
Building
PatientSense
I designed for two people: Mark in Access Solution and Jane in Voice of Customer. Both start in one shared home.
From there, each opens into views built around their own questions, zooms from the big picture to a single case, and, when something needs attention, gets a suggested next step.
Personalisation
How do six teams share one picture
without getting in each other's way?
Every team sees a summary card for every other team, so anyone can tell at a glance what's happening across the patient's support. But each person can only open their own team's work. The trade-off was visibility versus focus. Role-based access was one way in, but the real work was mapping which data points each team actually used to make decisions, day to day, and designing the experience around those, not a generic dashboard everyone had to search through to find their own.
Unified Dashboard
One shared home for every patient-experience team, showing brand, program, and engagement data at a glance before anyone drills into their own workflow.

Version 1
Version 2 (After User testing)
Data Viz and Workflow
How do you make complex data
understandable at a glance?
Raw counts and dense tables meant little without context, a number alone doesn't tell a team if something needs attention now or can wait. Design asked how to turn the data each team already had into something scannable, so patterns, outliers, and priorities could be seen without reading every row first.

Each team's view opens on a chart shaped like its question.
Choosing any slice opens the detail behind it, either a patient group's week-by-week timeline or the requests behind a flow, with no filters to rebuild.
Layers of lenses
How do you move from thousands
of patients to one case without starting over?
The charts are the way in. In Access Solution, choosing a slice of the sunburst opens that patient group's journey timeline, which shows every team's campaigns and support activities week by week. In Voice of Customer, choosing a flow in the Sankey opens the list of requests behind it, and then a single response. Filters carry through at every step, so there's nothing to rebuild.
Every view opens on the whole picture and peels off one layer at a time: from all patients or all feedback, to a group, to a single case.
Each layer keeps the context of the one before it, so the team always knows where it is and never has to start over.
Every view opens on the whole picture and peels off one layer at a time: from all patients or all feedback, to a group, to a single case. Each layer keeps the context of the one before it, so the team always knows where it is and never has to start over.

Recommendation
How do you stop a team from
having to hunt for the next step?
Access Solution thinks in layers, so its view opens on a sunburst: therapeutic area, then product, then patient group. Voice of Customer thinks in flows, so its view opens on a Sankey: channel, then topic, then satisfaction. Both arrive ready-made, with nothing to set up. The trade-off is that sunbursts are poor for comparing exact values, so the Access view pairs the sunburst with a table.

Wherever the data shows a problem, a suggested next step sits right beside it, ranked by likely impact. The team reviews it, adjusts it and acts on it in the same place, so insight turns into action without a hand-off.
Impact
What we see
55%
estimated less time to find the information needed to act
55%
estimated less time to find the information needed to act
30%
estimated faster turnaround on feedback cases
30%
estimated faster turnaround on feedback cases
6 teams
in one shared home, each entering only its own work
6 teams
in one shared home, each entering only its own work