Walgreens STARS (Safety Tracking System)
Digitizing a critical pharmacy workflow
I redesigned the Monthly Peer Review experience within Walgreens STARS, replacing a fragmented manual process with a centralized workflow for tracking meetings, participation, acknowledgments, and compliance.
30% improvement in reporting efficiency
Date: 2025
Users: Users: Pharmacy teams, managers, and operational stakeholders
My contribution: Product strategy | UX design | Interaction design | Prototyping | Usability testing
Role: Lead Product Designer
The Problem
Monthly peer review documentation was across meeting details, attendance, acknowledgements, and historical records. That created unnecessary administrative work and made it harder for pharmacy teams to quickly understand whether required reviews had taken place.
Before: Meeting documentation was disconnected from the primary review workflow, requiring users to manage information across multiple steps.
The Design Challenge
Make compliance visible without making the workflow heavier.
This wasn’t simply a matter of adding another form.
The experience needed to support different pharmacy roles while capturing meeting date/time, attendees, participant acknowledgment, meeting status, historical meeting records, and review activity across stores and organizational levels.
At the same time, the workflow needed to feel like a natural extension of Monthly Peer Review—not another administrative system layered on top of it.
My Approach
I designed the experience around the meeting—not the paperwork. My initial concepts focused heavily on managing individual attendees and acknowledgments.
Testing exposed a more fundamental issue: users thought about the work in terms of meetings first, not individual participants.
That changed the structure of the experience.
The initial design prioritized individual participation and acknowledgment.
What I Learned
Users needed to answer a more basic question first: “What happened at this month’s meeting?”
Participation mattered, but it made more sense in the context of a specific meeting.
I reorganized the experience around the meeting itself, with attendance, acknowledgment, status, and historical information contained within that context.
Shifted the focus of the table from staff-based to meeting-based.
Key Design Decisions
01 — Put meeting status at the center
Users needed to understand completion and compliance without digging through individual records. I made meeting status a primary part of the interface so teams could quickly identify completed, incomplete, or outstanding activity.
02 - Keep participation in context
Attendance and acknowledgments are important, but they’re supporting information—not the user’s primary mental model. I kept them directly connected to each meeting so users could review participation without losing the broader context.
03 - Make history useful, not archival
Attendance and acknowledgments are important, but they’re supporting information—not the user’s primary mental model. I kept them directly connected to each meeting so users could review participation without losing the broader context.
The Final Experience
One place to understand Monthly Peer Review activity.
The final design integrated meeting tracking directly into the existing MPR workflow.
Users could now see meeting activity, attendance, acknowledgments, status, and historical information without leaving the primary experience.