.png)
This end-to-end project highlights the development of Flöka’s course building feature. This project was featured as it exemplifies my skills with the discovery process and my adaptability to the non-linear design process.
Flöka is a startup that facilitates connections between female practitioners with female patients to help them in their health care journey. Our core product was a comprehensive dashboard that funnelled in our patient's app & wearable data. It was intended to help our practitioners identify health trends more quickly.
Disclaimer: This project will only be reflecting one user flow (course creation for the providers) attached to this particular feature.
Practitioners are searching for a solution that minimizes time investment yet provides a sustainable method for maintaining engagement within their community. Click to enlarge.
“I feel like I have so much potential to help so many other clients, but I only have so much time for 1:1s.”
How might we alleviate the follow-up and engagement demands on our busy practitioners when it comes to their previous clients?
Two major iteration sprints were conducted. The first iteration prototypes were tested with our existing advisory team (4 Flöka practitioners/coaches).
After working on user flows and running feasibility exercises with the engineering team, I brought our preliminary design ideas to our advisory board.
Initial discussions with our advisory board revealed that many health practitioners were in need for a dedicated space to store their extensive video libraries. However, upon re-evaluation, it became clear that users were looking to create and upload videos within the framework of a course curriculum.
.gif)
Initially, the intention was to keep user experience similar to our programs feature. As a result, practitioners were to be redirect outside the course creator to set up pricing. However, feedback suggested that creating payment plans inside of course creation was something that would result in a clearer course publishing process set up as a series of steps.
.gif)
After our first rounds of feedback we realized we had given priority to existing clients -not considering a second persona. At this point we understood the need to reassess the two distinct personas that should have been analyzed during the "Define" phase.
“I feel like I have so much potential to help so many other clients, but I only have so much time for 1:1s.”
“I am always looking for ways to generate a great experience for my clients! And data collecting is so important for change!”
Once both user personas were established, we had a look through some of the course creation tools that our practitioners/health experts were familiar and comfortable with.
After re-evaluting our user and analyzing other competitors in the market - a new user flow was created. Some of the highlights of this changed user flow - not discussed above - are as follows:
Our second extensive feedback session occurred after course creation flow was tested with our advisors and approved for production. A few new practitioners were then asked to use the beta version of courses to test and receive feedback on.
We were able to add a comprehensive course overview builder within the course syllabus. This was something that was given positive feedback after testing. Content would now be nested within modules. Users could add videos, attachments and information within the lessons.
gif%201%20-%20Iteration%202%20-%20B.gif)
Originally, a Marketplace was integrated as part of this feature to enable Flöka patient/client accounts to discover and purchase courses. However, we discovered providers too busy to market these courses. As a result, we removed the modal screen prompting practitioners to publish their course on the marketplace.
Originally, all data was uploaded and saved after users clicked on "publish" at the end of course creation process leading to a lengthy and frustrating uploading process for users. Consequently, we modified the system to save all copy, attachments, and videos as users set up their course content.
Visual Cues were also added to help course builders see what part of course content might be missing. If content is missing - users would not be able to move on to the next step which involves configuring payment settings.
We moved payments in users flow from below the course creation section into separated steps - to help differentiate and keep users orientated on the main task in each step. Furthermore, we introduced the capability to modify the course type both from the payment page and the course creation page.
Practitioners needed a link to redirect their clientele to once the course was live. This was the reason the third step in course creation now asked for a username to be used in the URL to manufacture this page using the content from the course overview. Early feedback from the resulting landing page suggested that the UI was too outdated and unclean to be used. As a result a second iteration was done.
The following final designs are currently in production! We've included three distinct types of courses: one-time payment, membership courses, and hybrid courses (incorporating 1:1 services).
This project represents a significant undertaking for the product team. Serving as the founding designer on the team, I was on this feature’s journey from end to end.
It is crucial to remain cognizant of all assumptions made during the design process. Ultimately, user testing is the most effective method to eliminate these assumptions.
A key takeaway from this project was the importance of mapping out all user personas associated with the feature. This case study highlighted the significance of user personas.
This case study only walked through the course creation user flow for this new feature. As a result, next steps - most of which were done simultaneously with this sprint - were varied. Feedback has also shown us how we can evolve this feature further to differentiate and answer more to our user’s needs.
The biggest next steps would be mapping out the courses experience from the patient side. This would include the view of courses, payment management and notifications. Additional, smaller user flows are detailed below:
Frequently, successful practitioners/providers using Floka courses were promoting our iOS app as their own, highlighting its tracking/integrations along with it’s capability to showcase their course content. Subsequent discussions and requests from these accomplished users revealed that white-labeling the app would assist their clients in associating the elevated experience with their individual brands, aligning with their desired branding goals.
