SaaS UX Design — Brief to Figma
Expert Radiology was building a cloud-based medical SaaS platform. Engineering had requirements but no UX flows. The product needed a full UX design pass before development could proceed.
12
Screens, 2-week delivery
The problem
Engineering requirements existed in text form with no visual translation. Without UX flows and prototypes, developers were building blind — no shared understanding of how users would move through the platform.
Goals
Translate engineering requirements into interactive UX prototypes
Design core user flows for the medical platform
Deliver a handoff-ready prototype for development
Complete the full design cycle within 2 weeks
Approach
- 1
Conducted requirements review sessions with engineering lead to clarify user needs and technical constraints
- 2
Mapped 4 core user flows: onboarding, study submission, review workflow, and reporting
- 3
Built wireframes in Figma for all screens — desktop-first with mobile considerations noted
- 4
Iterated through 2 rounds of feedback with stakeholders
- 5
Delivered interactive prototype with annotated handoff documentation in FigJam
Systems used
Figma
UX flows, wireframes, interactive prototypes, component library
FigJam
User flow mapping, stakeholder collaboration, annotation
Notion
Requirements documentation and feedback tracking
Results
12 screens designed from brief to final prototype in 2 weeks
Zero scope creep — delivered exactly to brief
Prototype approved in first stakeholder review
Development team began sprint planning immediately after handoff
Strategic takeaway
Moving fast on UX requires discipline before speed. Locking requirements before opening Figma — even for a day — prevents the expensive design rework that comes from building on shifting assumptions.