Currently taking
12 weeks sprint project (August to October, 2023)
~3 weeks of design sprint
Teamed up with Product manager, Tech lead and 4 developers
iOS App feature
Currently taking is a part of a big release known as Active plan
Working with a Senior designer on different features of the same release
View currently taking web experience
This video shows the web parity experience named “current. supplement intake.” Note: the web experience was built in 2024 a fast follow based on the iOS currently taking feature.
Design process and priority for this project
Why do we need a feature like this? — Problem area
A patient’s ability to stay on track with their supplement plan requires several different management actions such as ordering, reordering, knowing how and when to take and creating and cancelling subscriptions.
Supplements purchased outside of Fullscript are excluded from the patient experience, creating a fragmented experience that prevents patients from effectively and holistically managing their supplement plan.
Patients aren’t able to use Fullscript to stay on top of their supplement plan since they don’t have a consolidated view of the supplements they are actively taking.
Currently taking scope map and opportunities across the practitioner and patient journey
With this feature, we can:
Introduce patients to Fullscript much earlier
Patients will be able to access Fullscript and benefit from the tools available before seeing their practitioner for the first time.
Provide value beyond dispensing supplements virtually
Fullscript isn't just for supplements anymore!
Practitioners now have a much better way of obtaining key information about their new and existing patients that will help them prepare for appointments, make quicker assessments and ultimately craft better supplement plans for their patients.
Allowing patients to add and manage supplements purchased outside of Fullscript and providing practitioners visibility into those decisions means that the entirety of a patient's chosen supplement routine can be managed from within Fullscript.
Currently taking IA and flow map
With instrumental new features being plugged into a bigger platform, it’s crucial for the designer to make sure the solution will be scaleable and flow seamlessly with existing features.
This project heavily relies on information architecture, object-oriented UX, and flow mapping at the analysis stage to ensure we are creating value at the right point in the patient’s journey.
Test, iterate, test, iterate and repeat
After this project moved into concept design, we kept testing the low-fidelity designs both internally and externally, with non-Fullscript users and Fullscript users to make sure we are:
Naming the feature in a digestible way
Not leaving any gaps in the flow
Fault tolerance is high enough to cover most edge cases
Address the right pain points
Easy for our target users to use
Utilizing expected iOS patterns for the user to feel familiar
Consistent with current design language
The design is engaging with simple work flows
Final release
Ship it to the beta group! - Release plan
Who is in the beta
We handpicked 21 practitioners and their patients to participate in the beta launch and provide meaningful 1:1 feedback on the Active Plan.
We chose a variety of modalities and clinic sizes to learn how the Active Plan works or doesn't work within a broad cross-section of our practitioners.
How did we do? - Insight report (Dec 2023)
How are we doing now (March 2023)? After GTM, web parity and added practitioner experience?
The numbers are trending super well since the beta release.
We now have 4k active plans since the October release. And more are using this feature organically.
Challenges, reflections and more
A project like this is rewarding but also challenging. Let me be real here and jot down some challenging moments and my reflections.
Time. It’s about a 3-week design sprint with a net new feature on the new iOS App. Making sure the solution is feasible and scaleable and that on-time delivery is also a major challenge.
Team changes. Unfortunately, I went through 2 team changes right before and after this project. The first one resulted in me getting moved from a Web team to an iOS team, meaning I had very limited onboarding time to learn iOS patterns. The latter team changes resulted in me being moved away from the Active plan, meaning I had no involvement in further iterations and feature builds.
Alignments. A high visibility project like this equals to ALL EYES ON YOU. Getting buy-ins from my developers, my design lead, division leads, VPs, Marketing division and all the way to the C-levels took a lot out of the design focus time.
