UI/UX Designer
Chrome (4) Copy.png

RegimenPro - E-commerce

RegimenPro -
E-commerce

Role:
UX Designer
Key Activities:
Discovery, Flow Diagrams, High-fidelity Wireframing

 
 

Background

RegimenPro is an e-commerce platform within the healthcare/skincare industry. Tasked with building out a custom portal for the doctor’s offices to manage their patients as well as an e-commerce platform where patients can purchase and manage their current Regimen and purchase other skincare products.

Challenge

The current platform is extremely unusable, so much so that doctor’s offices are forced to do all the work on their end for the patients, leaving sales stagnant. The customer facing e-commerce platform left users frustrated - so much so that it didn’t even have the capability to track packages, which was the #1 task that users tried to accomplish after signing in (IF they even could sign in, the platform currently sets a password for the patient, not prompting them to reset, which most users forgot or lost the email to). Usability issues were pretty clear, and our #1 fix in the rebuild. Along with updating current features, we implemented a custom quiz logic, that recommends products to patients and takes some stress off of the physician’s and staff within the office, who may not have advanced knowledge on products.

 

Discovery - Kick-off Workshops

Screen Shot 2019-09-16 at 11.08.41 AM.png

Brand Adjective Workshop

Stakeholder voting for what RegimenPro “is”, we also held another workshop with results for what RegimenPro “isn’t”.

Screen Shot 2019-09-16 at 11.07.48 AM.png

User Journey Map

The 5 E’s framework is a comprehensive way of looking at an experience. It ensures all components of the experience are reviewed and discussed. During the workshop, we looked at the current journey and discussed possible future experiences for both the patient and specialist.

Screen Shot 2019-09-16 at 11.07.07 AM.png

Feature Prioritization Dot Voting

In dot voting, stakeholders place two different color dots on suggested features: a green and a yellow dot. A green dot means they believe the feature is high priority and should be executed immediately. A yellow dot indicates a lower priority and the feature can be executed at later date, or not at all.


High-Fidelity Wireframes