top of page

Case study

From opportunities to solutions.

How I turn ambiguity into aligned, validated solutions.

Process flow vertical.png
Research.png

Understand the Problem & Identify Opportunities

I start by grounding every project in evidence by analyzing behavioral data, interviewing users and stakeholders, and mapping workflows to uncover friction. This turns vague problems into clearly defined, high-impact opportunities.

FaceThinking.png

Validate & Test Solutions

Before committing to any direction, I explore multiple concepts, prototype quickly, and test assumptions with real users. This ensures we invest in solutions that actually solve the right problems.

Build.png

Design & Collaborate

Once a solution is validated, I translate it into detailed requirements, flows, and high-fidelity UI. I work closely with engineers throughout to ensure feasibility, shared understanding, and zero ambiguity at handoff.

Measure.png

Build & Measure Success

After launch, I collaborate with engineering and product to monitor performance, assess impact through data, and gather user feedback. Insights from measurement feed the next iteration — because meaningful design never ships once.

Upgrading the digital pathology workflow.

A case study in turning complex clinical workflows into intuitive, scalable product experiences.

Understand the Problem (aka Opportunity) & Ideate Solutions

For pathologists, efficiency isn’t a preference — it’s survival. Depending on their specialty, a single pathologist may complete anywhere from 10 to 100 cases per day, which means every click, pause, and decision compounds. As one user told us:

 

“Clicks are the Antichrist.”

 

That line ironically became our unofficial product north star.

 

Using Pendo analytics, workflow mapping, and continuous user interviews, we identified the most critical friction points slowing users down and impacting turnaround time. These insights became a structured opportunity space the entire team could align on.​

Understand Problem.png

What we learned:

  • Key steps in the diagnostic workflow required unnecessary clicks

  • Important context was hidden or scattered across screens

  • Interactions were inconsistent, forcing users to stop and think

  • The UI made simple tasks cognitively heavier than they needed to be

 

To ensure shared understanding, we pulled in engineering early. Together we reframed raw user pain into clear, actionable opportunities.

Solutions 1.png

Of 100+ insights collected, we narrowed the list to 28 high-value opportunities tied to product outcomes and business goals. From there, we prioritized the solutions offering the highest user impact for the lowest effort, establishing a roadmap rooted in evidence not just opinions.

Solutions 2.png

Validate & Test Solutions

With a prioritized opportunity set, we prototyped multiple concepts across 8 core solutions aimed at improving speed, reducing cognitive load, and minimizing clicks.

 

We ran rapid validation loops through moderated user tests, gathering behavioral data and qualitative feedback to refine direction. Every iteration brought us closer to the simplest experience that still respected clinical rigor.

Prototype.png

Design & Collaborate 

Once we had validated solutions, I translated them into detailed workflows, requirements, and high-fidelity UI.

 

I wrote the first draft of every user story in Confluence, ensuring clarity around logic, edge cases, and real workflow constraints. In parallel, I designed modular UI using our new Vue-based design system which enabled engineering to build faster and maintain consistency with minimal back-and-forth.

Confluence.png

This phase was highly collaborative: daily conversations with engineers, async reviews, and negotiation when technical constraints surfaced. The shared outcome: a solution that was both beautifully simple and technically feasible.

Designs in Figma and Zeplin.png

Build & Measure Success (& update)

Development took just three weeks, thanks to clear requirements, tight collaboration, and a scalable component system. After release, we A/B tested the new workflow and tracked key efficiency metrics:

​

21.5% decrease in clicks per case

25% decrease in time to complete a case

 

These weren’t small wins either. They represented a meaningful reduction in cognitive load and a noticeable impact on daily throughput. Pathologists felt the difference immediately.

 

Of course, we continued interviewing users post-launch, folding new insights back into product improvements. Iteration doesn’t stop once something ships.

Skills used

  • Continuous user interviewing & discovery

  • Translating user insights into strategic opportunities

  • Prototyping and validating assumptions

  • End-to-end UX/UI design

  • Writing clear, actionable requirements

  • Leading cross-functional alignment

  • Communicating complex logic simply

  • Systems thinking and modular design

  • Facilitating decision-making with product & engineering

  • Staying grounded in data, not opinions

  • Iterative product improvement

  • Making hard tradeoffs without losing sight of outcomes

bottom of page