top of page

Case study

From opportunities to solutions.

Here's a look at my approach.

Process flow vertical.png
Research.png

Understand the Problem &
Ideate Solutions
By analyzing user behavior in Pendo and empathizing with users with in-person and remote interviews we identified major pain points in the main user flows. 

FaceThinking.png

Validate & Test Solutions
Next we come up with solutions, prototype them when applicable then test to validate those solutions fast with more user interviews.

Build.png

Design & Collaborate
Now that our solutions have been revised and validated we can create in-depth requirements and pixel perfect UX/UI.

Measure.png

Build & Measure Success
Then we begin development, collaborate with engineers as issues arise. We measure the impact by analyzing the data and, you guessed it, more interviews... SHOCKER!

Upgrading the digital pathology workflow.

A case study.

Understand the Problem (aka Opportunity) & Ideate Solutions

For pathologists, efficiency is the name of the game. Most pathologists complete anywhere from 10 to 100 cases in a day depending on their specialty. So in their day-to-day, efficiency is the name of the game. Their feeling is that clicks really count and the less clicks the better. As one user put it "clicks are the Antichrist".

​

By analyzing data in Pendo and conducting continuous interviews with users and stakeholders we identified the key aspects of the workflow that were hindering the efficiency of our users, and hurting our KPIs. 

Understand Problem.png

Next our team brought in developers and engineers so we were all on the same page. Together we identified opportunities and brainstormed solutions.

Solutions 1.png

Of the 100+ takeaways from our user interviews we identified 28 opportunities that aligned most with our outcomes. We then prioritized the solutions that offered the highest value and the lowest effort that could accomplish our product and business outcomes. 

Solutions 2.png

Validate & Test Solutions

We prototyped multiple versions of 8 solutions that we assumed would offer maximum efficiency to the user. We tested those assumptions and validated our solutions by conducting user testing.

Prototype.png

Design & Collaborate 

Now that our solution was tested and validated by real users, the feasibility was validated by the developers and engineers, it was time to refine the designs and document the functionality and requirements.

​

We started by writing user stories and requirements in Confluence.

Confluence.png

Creating pixel perfect UI in tandem with the requirements was a breeze with the new modular design system based on Vue's framework.

Designs in Figma and Zeplin.png

Build & Measure Success (& update)

Finally it was time to develop and iterate. The new feature was developed in 3 weeks. Then we A/B tested and to measure the impact using various metrics, the main two being clicks made by the user, and time to complete a case. We saw a 21.5% decrease in the amount of clicks made by our users to complete their task, and a 25% decrease in the time it took to complete a case, resulting in a drastic increase in efficiency.

Skills used

  • UX Research,

  • Wireframing

  • UX/UI Design

  • Prototyping

  • Making it happen

  • Creativity

  • Interpreting user feedback into actionable items

  • User interviewing (continuously)

  • Communicating technical things to non-technical people (and vice versa)

  • Not losing it when solutions fail

  • Collaboration,

  • Involving devs at every step

  • Making hard decisions

bottom of page