Pulling admins off a 10-year-old console they had no reason to leave.
- Systems Design
- Migration
- Enterprise
- Data Viz
Data security is the infrastructure of operating businesses — admins prioritize familiarity and utility over polish. I led the systemic redesign that gave them a reason to migrate without breaking muscle memory.
- Role
- Senior Product Designer
- Timeline
- Mar 2022 — May 2023
- Team
- 5 PMs · 2 PDs · 18 engineers
- Tools
- Figma, User Research, Design Systems
Most of my work lives behind NDAs and embargoes. The walkthrough that matters — the why, the things I cut, the calls I'd make differently — happens in conversation, not on a page.
Day-to-day data monitoring (cluster health, job ops, disk replacement) was mature in legacy local software and underdeveloped in the new SaaS — because cloud ransomware detection had taken priority. How do we give admins a reason to migrate without losing what they already trust?
Closed the migration gap
Rebuilt the core data-monitoring surfaces — cluster jobs, disk replacement, health monitoring — inside Rubrik Security Cloud, framed against the legacy console rather than away from it.
Where I made the calls.
- 01Diagnosed the customer-stickiness problem: legacy software's day-to-day monitoring (cluster jobs, health, disk replacement) was mature; the SaaS replacement had been deprioritized in favor of new ransomware features. Re-framed the brief from 'redesign the dashboard' to 'give admins a reason to migrate.'
- 02Mapped the legacy mental model — clusters, jobs, alerts — and rebuilt the SaaS surfaces around it instead of around the new feature taxonomy.
- 03Designed progressive disclosure for power users and sensible defaults for new ones, validated against admin shadowing sessions.
- 04Drove the telemetry-driven IA: Pendo + Looker as the input, dashboard surface decisions as the output.
