Operation Safe Escape supports survivors of domestic violence, stalking, and harassment. I designed several flows for FLOW, a secure case-management platform intended to bring parts of their email-and-spreadsheet workflow into one centralized system.
For a small team, keeping up with that information took time away from supporting survivors.
OSE tracked survivor cases through email threads and spreadsheets while working with a small staff and volunteer team.
That made case history harder to follow and left the team without one consistent place to review what had already happened.
Admins and volunteers could spend time piecing together information before they could figure out what someone needed next.
OSE needed a secure way for admins and volunteers to understand a case quickly, keep its history in one place, and hand work off without losing context.
They needed the current need, case history, and next action to be visible in one place.
To open a case and understand how urgent it is, what the survivor needs, and what has already happened — then leave a clear update for whoever works on it next.
Where he came fromRobert represents the volunteers OSE relies on alongside its small staff. I don’t have interview notes from this project, so he stands for the volunteer workflow described to us rather than a specific person I spoke to.
My work focused on translating OSE’s case-management requirements into flows for reviewing cases, communicating securely, collecting survivor information, and maintaining forms after handoff.
FLOW handles sensitive information about people seeking help, so privacy and safety had to come before convenience.
A case can move between survivors, admins, and volunteers over time. The workflow needed to preserve enough history that someone new could understand what had already happened.
Each case could contain a lot of information. I focused on making the most important details easy to find first, with deeper information available when someone needed it.
OSE didn’t have a full product design system when we started, so our design team built the shared components FLOW needed around its existing logo and typography. Those patterns gave the team a consistent foundation as different flows were designed in parallel.
The intake needed to work well on a phone so survivors could complete it without depending on a desktop experience.
OSE doesn’t have developers on staff, so the team needed to be able to update intake questions after handoff without relying on us for every change.
The dashboard puts every case in one place, so an admin can tell status, priority, and case type apart without opening each one.
Opening a case brings the important information into one view, so an admin or volunteer isn’t piecing the story together from separate records.
Secure messaging gives survivors, volunteers, and admins one place to talk instead of personal email threads.
The intake starts the record, admins review and update it, volunteers can pick up assigned work, and secure messaging keeps communication connected to the same workflow.
I handed off five connected FLOW experiences: the survivor case dashboard, case card, secure messaging, mobile-first intake, and form builder, along with the shared component patterns used across them.
Most of my earlier projects were about making a task faster. Here privacy and safety came before convenience, and that changed which options were even on the table.
I started thinking less about whether one person could finish a task and more about whether the next person could understand what happened before them. Designing the handoff became part of designing the workflow.
Sortable lists and CSV exports weren’t the exciting parts, but they replaced work OSE was doing by hand. I pay more attention now to whether a feature actually takes work off someone’s plate.
05Designer
Brilliant Cities
Helping parents keep habit goals going at home, between programs.
01Product Design Intern · Summer 2026
Terraform
Making read-only access clearer without removing the context people still needed.
02Product Manager · Spring 2026
Anda
Deciding which driver-support work to build first, before the real data was ready.
