Healthcare digital product kick off in 2 weeks 🚀
This case study describes creating the first version of a digital healthcare product from scratch with minimum effort and maximum effectiveness.
In the process, I was involved with two more teammates: the client who played the role of the Product Manager and the Full-Stack Engineer, Meir Shalev, who did a great job operating all the technical aspects. Some of the titles, diagnoses, and names in this study were changed due to the NDA contract and data sensitivity, but the UX & design process did not blur.
The Results
Numbers
As a result, we’ve launched the demo version in 2 weeks as a team of 3 people, had more than 15 products compared, 4 flows tested after analyzing 1500+ interviews.
What’s been done:
Market research and benchmarking
User Personas based on the qualitative and quantitive research results
Userflows, wireframing, user testing
UX Strategy for the future product implementation
UI concept for mobile App
The Approach
I have to be honest for the client's sake: the process seemed (and was) perfect because of the small team size and its highly experienced members. It was a true pleasure working with such qualified people on such an important product. We went with a flow and set the milestones by dividing the whole process into 6 simple steps (scheme above).
The Task
What did it start with?
The client came with an idea and (happily) with the pale of beneficial research results. As it often happens, the brand guidelines were in the creation process, so User Experience became the primary focus for my attention. During a bit more than 2 weeks, we went through the perfect process from the very first brainstorm the actual demo version of the product.
So, what is Astrid?
Astrid is the first end-to-end, customized care program for the specific diagnoses, designed with you in mind: includes a holistic care, personalized program and advice you can trust.
Market Research
Nowadays, the online market is full of products within the healthcare industry: mental health recovering programs become viral once launched. But most of the applications, digital platforms, and SaaS products are very generic and focused n the overall health condition.
Astrid, in its turn, focuses n the specific health condition. There is no similar product in the market.
Desktop web experience: Landing pages comparison
Mobile app (iOS) market research, zoom out. Discovering branding and color languages.
User Research & Numbers
Who are the users? Women in their 20-30th
What they came with? Recently got diagnosed / looking for PCOS treatment / trying to conceive / can’t loose weight
Based on the quantitive and qualitative research, we’ve discovered implications, main frustrations, goals, needs, and values for the average user. See data is hidden for security reasons and concerning the respondents, the client, and the interviewers.
The User Persona was created and named Cara. Because she cares.
Information collected for persona: surveys, waitlist information from respondents, interviews, etc.
User Persona, zooming in: Cara, diagnosed with this condition.
User Stories & Scenarios
The product implies 2 sides of the user and 3 user roles. For sure, at the first launch of the demo version, we’ve taken the most common case for each side, the frequent patient and the responsive provider. For each, I created the task flow, focusing on the mobile for the patient and the desktop for the caregiver.
Main task flow: the most common product use case, mobile experience
Onboarding flows for testing on patients side: 2 ready-to-go mobile low-fidelity prototypes
Responsive design planning
In the beginning, the client planned to have the invite-only system for profile approvals. However, a few providers were ready to work even before the launch day, so theoretically, we would have a chance to test the platform. Since the timing was very tight, we decided to go with the existing APIs and use it as much as possible, so more time could be spending n the UX, not the UI. My job was to provide the logic fr the platform responsiveness, define its flexibility, and outline the main points for scalability. For the provider’s side, we went with a desktop web experience for objective reasons.
Scalability testing: Responsive web grids and components
Layout testing: main navigation types + responsive blocks of the provider’s side
Open Source Market Magic
After the layout approval (the client has chosen option 2 on the image above), the relevant API was found n the web, and throughout the whole process, I did not have to create the UI part at all. It saved at least 50 hours of work.
Outcomes
UI concept: Some of the final screens for the deck
Also, the Demo version is all about showing up. So beside of having the logic of the platform and the demo, we went with a nice UI concept for mobile on the patient’s side. It helps to understand what this is built for: having a caring assistant of your diagnose on the go. The product now growing fast and works perfectly.
The Challenges and Takeaways
This health condition is pretty unique, and it was hard to reach out to the users, but the client helped on this part a lot. The biggest challenge fr us all were time frames, but we sped perfectly thanks to the genius data scientist, who could find most solutions ready for usage. From my side, we did most of the work on the research part, which was crucial for defining the most relevant features for the launch.
I enjoyed working on the project and became a step closer to the digital healthcare industry that I love working in. Astrid was my third project in this area, and I’m looking forward to working on the next one.
The critical aspects of the successful project:
everyone’s (in the team) awareness of the main problem
clarifying directions by setting relevant time frames
the prioritization and frequent syncing
