Risk and Safety Solutions
Building case tracking system servicing 1,100+ program admins at university campuses and hospitals
My Role
UX Design Intern leading the development of new Tracking Feature
My Team
UX Design, UX Research, Software Development, and Product Strategy teams
Duration
5 months (July 2025 - Present)
Tools
Figma, Figjam, Dovetail, Zoom, v0, Magic Patterns
COMPANY OVERVIEW
What is Risk and Safety Solutions?
Risk and Safety Solutions (RSS) is a cloud-based B2B SaaS platform for environmental health, safety, and risk management.
RSS serves UC and CSU campuses, healthcare systems, research labs, public health agencies, government bodies, and industry partners.
INITIAL BRIEF
I was asked to design a scheduling tool to streamline event coordination for Ergonomists
My mentor assigned me a project to design a scheduling tool for ergonomists. The initial goal was to streamline how admins scheduled events and meetings across teams.
Target Audience (Who are Ergonomists?)
Ergonomists adjust and optimize workplaces for safety and efficiency. RSS serves ergonomists who support thousands of employees at major university campuses and hospitals, such as UCs and CSUs.
USER INTERVIEWS & JOURNEY MAPPING
Users didn’t struggle with scheduling, they struggled with tracking information
After conducting interviews and gathering insights, I discovered something unexpected: users didn’t struggle with scheduling. Their real challenge was keeping track of key information throughout their workflow, they were losing context and spending extra time finding updates.
The Research Process to Understand Ergonomists' Workflow
Decoding transcripts from 6 interviews
Organizing 400+ key quotes into themes
Discovering the recurring pain point of disorderly tracking
=
“The flood of emails and requests makes it easy for ergonomists to lose messages and feel overwhelmed.”
Ergonomists are distressed from lacking any internal tracking system
Interviewee #1: "But sometimes you have so much in your head and so many different departments that it's, it's hard to go back. Did I miss that or. You know, you're at home, you're like, oh my God, I think I didn't receive an email, but I saw it, but I didn't click on it.."
Interviewee #8: "I've missed a couple emails and…I don't know if it was just an email that was hung up somewhere on your end. My end. I don't know."
HOW MIGHT WE
Reframing the project to address the real user need: information tracking
I presented these findings to my mentor and proposed reframing the project. Instead of building another scheduling tool, what if we designed a tracking system that helped admins monitor information more efficiently?
After discussing business implications and user value, we redefined the problem statement:
HOW MIGHT WE?
How might we create a tool to help Ergonomists be more organized in managing and tracking the employees they serve, ultimately reducing their overall stress?
CONCEPT EXPLORATION
Imagining the dream vision to guide our product forwards
With a clear problem in mind, we ideated what an “ideal state” could look like. This "north-star" design visualized the most seamless experience for ergonomists.
Main features
Tracking by person
Initially, ergonomists' dashboard would just be a list of submitted documents. This didn't allow ergonomists to view one person's history or information all in one spot. We changed this by using a table that tracked by person.
Prioritized to-dos
In the dashboard, we surfaced what needs direct action from ergonomist, prioritizing high-risk cases and upcoming scheduled evaluations.
Multiple views
We added multiple ways to view the information (dashboard, table, calendar, kanban) in addition to a right sidebar that displays all the information for one entry/person.
PROJECT SCALING
Scaling a single solution into a platform-defining experience
Insights from my mentor revealed that tracking challenges weren’t limited to the ergonomics team. Recognizing the broader value, we reimagined the concept as a unified dashboard experience for all program admins. This rescope was huge, as my project went from a small scheduling feature to the main dashboard of all programs in the RSS ecosystem.
Small Scale: Initial Scheduling Tool (Ergonomics Program)
Helping ergonomics admins manage scheduling efficiently. Focused on a single program’s workflow.
Large Scale: Platform-Wide Tracking Dashboard
The new tracking feature addressed pain points shared across all program admins. Leadership expanded the project into a full redesign of the main dashboard, making it the central hub for every admin’s workflow.
FEATURE PRIORITIZATION
Narrowing the design to focus on core features for the MVP
As we aligned with developers and business stakeholders, we identified which features we believed essential for an MVP, and which could wait until future iterations.
CONCEPT TESTING
Gathering real feedback to guide our next design decisions
I tested the MVP prototype with program admins to observe how it fit into their workflows and identify which features mattered most. I focused on two main goals: validating the solution and learning what else needed more iteration. Their feedback revealed key usability patterns that guided the next stage of synthesis and iteration.
Main Research Goals
Validating the Solution
Is this the correct solution for the problem?
Uncovering other needs
What features were dealbreakers for the user? What features can be cut for the MVP?
Testing Prototype
*the design is purposefully styled in low/mid-fi so participants understand it's just a test prototype
Main goals
Necessary data
What data must users be able to track for the feature to be valuable?
We tracked this by allowing the participant to set up their own table and talk through why they selected what to include in their table
Current workflow
How does tracking need to fit into their current workflow?
We asked questions about their current workflow, and asked how likely they would be to integrate a tool like this into their current workflow
Understanding MVP
How simple or sophisticated does functionality need to be to meet core user needs?
We asked what features are necessary and which ones are just "nice to haves."
PROOF OF CONCEPT
Our prototype validated that tracking filled a crucial gap in admins’ workflows
Our tests confirmed that the new tracking approach solved a genuine pain point. The concept has since expanded into a full-scale redesign effort to replace the main admin dashboard.
Our prototype concept met their needs
Interviewee #3: "It will allow me to see where things are at because right now I don't…I feel like this would just organize it like very nicely where I can see like where everything's at."
Interviewee #5: "Being able to set sort of the status so we can keep track of that and add in notes, that sort of thing. I think it could be a huge help for us. So, I like where you guys are going."
FINAL DESIGNS
Designing the MVP
With feedback from our user testing, I designed the dashboard in Figma, focusing on the main value adds of the project, and what people pointed out were dealbreakers that needed to exist to make the product valuable to them
REFLECTION
Journey in Review
Next Steps
Addressing Other User Needs: Another user testing session will likely be a good measure to test other features (such as automation) that some user testers indicated was essential for their process
Dev Hand-off: After hammering down the MVP with all its necessary features, I will officially hand it off to the devs. The devs are currently being kept in the loop about this project, and expecting to receive it in the near future
Business Goals: To ensure the impact of this project for the business, it's essential for us to get a better feeling of market demand, competition, the cost of production, and the product’s perceived value
What I would do better next time
Getting a grasp of the no-code nature company products: A lot of my designing was spent being oblivious of the no-code nature of our product, meaning I was making things that wouldn't be configurable large-scale. If I were to go back, I would take more time in the beginning to understand how the company's current products function
