Lumere – Healthcare Cost Optimization SaaS Platform
Role
Senior UX Designer
Domain
Healthcare · SaaS · Enterprise Data Systems
Skills
SaaS Product Design · Data-Heavy Interfaces · Information Architecture · Workflow Design · Stakeholder Facilitation · Executive Presentation
Overview
Lumere is a healthcare SaaS platform designed to help hospital systems reduce supply chain costs by providing detailed pricing and utilization data for medical products. The platform supports physicians, value analysis committees, and purchasing leaders in making informed decisions about high-cost items such as implants and surgical components.
My role focused on organizing highly complex medical product data into clear, actionable workflows that reduced decision friction and supported cost transparency at scale.
The Problem
Hospital procurement and physician decision-making involve deeply complex product structures:
A “replacement hip” is not a single product
It consists of multiple components (ball, stem, socket), each with its own SKU and cost
Products vary by vendor, compatibility, clinical outcome, and pricing contract
Physicians request items based on preference and clinical judgment
Purchasing teams negotiate contracts and aim to reduce cost
The platform needed to:
Surface meaningful comparisons
Clarify component relationships
Support physician trust
Enable purchasing leaders to identify cost-saving opportunities
Reduce manual analysis time
The data was available — but not organized for effective decision-making.
My Role
As a UX Designer at Lumere, I worked across product design and stakeholder engagement. My responsibilities included:
Designing workflows that organized multi-component product systems into understandable groupings
Creating interfaces that reduced cognitive overload in dense data environments
Supporting executive-level presentations and hospital board discussions
Working directly with physicians and value analysis teams to understand needs
Reducing process friction in evaluation and approval workflows
Aligning product design with business objectives around cost reduction
This role required both detailed interface work and high-level strategic communication.
Research & Insights
Through collaboration with internal teams and external stakeholders, key insights emerged:
Physicians require clinically relevant context to trust cost data
Purchasing leaders need clear comparative structures, not raw tables
Data grouping must reflect real-world product bundles
Too much granularity overwhelms decision-makers
Process inefficiency often comes from poor information hierarchy, not lack of data
The solution needed to organize complexity without hiding it.
Design Approach
1. Structuring Complex Product Hierarchies
Rather than presenting components as disconnected SKUs, I designed grouping patterns that:
Visually bundle related components
Show aggregate cost at the system level
Allow drill-down into individual parts
Preserve transparency while simplifying comparison
This helped decision-makers evaluate complete product systems rather than isolated items.
2. Reducing Cognitive Load in Data-Dense Interfaces
I introduced clearer visual hierarchy by:
Grouping related data fields
Prioritizing high-impact cost indicators
Using expandable sections for deeper detail
Designing tables that emphasized comparison over raw volume
The goal was clarity without oversimplification.
3. Supporting Physician & Executive Conversations
Because this product influenced real purchasing decisions:
I participated in discussions with hospital board members
Presented interface concepts and cost-reduction scenarios
Ensured the design supported strategic narratives around savings
Refined visualizations to improve clarity in executive settings
The platform needed to be persuasive without being misleading.
4. Improving Workflow Efficiency
Design refinements reduced friction by:
Clarifying evaluation stages
Simplifying product selection flows
Reducing redundant analysis steps
Making cost deltas and contract implications easier to see
This resulted in measurable reductions in user process time.
Key Design Decisions
Grouped component-based products into system-level views
Emphasized comparison rather than static data browsing
Designed visual hierarchy to support high-stakes decisions
Avoided over-visualization that might obscure detail
Balanced physician autonomy with cost transparency
Solution
System-Level Product Views
Component grouping (ball, stem, socket)
Aggregated cost presentation
Expandable drill-down views
Comparison Interfaces
Vendor comparisons
Cost variance highlighting
Clear differentiation of contract impact
Workflow Improvements
Reduced time required to evaluate alternatives
Improved clarity in product substitution discussions
Better alignment between physicians and purchasing teams
Impact & Results
Improved clarity and confidence for patients scheduling online
Reduced friction in a high-stress workflow
Supported accessibility compliance across the flow
Helped shift more scheduling activity to self-service
Provided a foundation for continued refinement
Even small improvements had meaningful impact in a healthcare context.
What I Learned
SaaS UX often lives at the intersection of business and human judgment
Complex product hierarchies require thoughtful grouping
Decision-support tools must balance persuasion and neutrality
Executive-facing UX requires clarity and composure
Organizing information can create more value than adding features
Artifacts (Optional)
Product grouping explorations
Before/after data layouts
Comparison table iterations
Executive presentation screenshots
