Solutionreach

The Problem

Medical practices wanted more patients to leave online reviews

Reviews were difficult to track across multiple sites

Discovery Research

Our first priority was to figure out if there was any need for our product, and if so, why people wanted to use it.

We started with assumptions and questions we had about how our customers handled online reviews.

Initial Surveys

We sent out a preliminary survey to our existing customers asking some basic questions.

We learned a lot about user habits and conventions from the responses we received.

But we wanted to dig deeper.

So, we conducted in-depth interviews with a handful of our customers.

Research Takeaways

Practices were struggling to manage their online presence

Patient feedback was decentralized and difficult to access

Ideation

Now that I had a deeper understanding of the user's needs, I worked with PMs to define business requirements and identify a minimum viable product. Using this information, I started building low fidelity mock-ups.

Building user flows helped me develop the information architecture for the product.

Through validation testing and weekly UX team showcases, I fleshed out and prototyped the product design.

Outcome

By the end of the project, I had overseen the production and integration of the first complete version of the product

I built full prototypes of future iterations that were used to build the product six months past my project

Validation testing showed that existing customers were excited about the features our product offered

Smart Reviews is still used as a selling point to attract potential customers and showcase the SR Health platform

What I Learned at Solutionreach

Building a product from conception to production

Designing over multiple iterations and increasing fidelity

Wireframing screens for web design with Sketch

Creating interactive prototypes with Invision

Conducting discovery research and user interviews

Working with PMs and engineering to deliver the product

Smart Reviews