The more you know about the learning goal for your learner, the better you can design for them. This project aims to understand what kinds of goals our learners have, how they fit learning to code into their current routine, and what tools and supports have been valuable to them that we could offer to help them set and stick to these goals and routines.
This project is the follow-up project of Streak, but with a more narrowed focus that bund with goal-oriented learning behavior within more committed learners, which are those paid Pro learners.
The team decided to research before jumping into a product design process to obtain insights for a series of future feature development that aims to support successful learning to our learners.
Here are the success metrics we’d like to track and measure for this project:
A “goal setting“ research was conducted with questionnaire surveys and follow up interviews with Pro learners that match certain criteria that are highly related to the study. In this study, we would like to know more about our Pro learners with certain criteria as :
After consolidating and reviewing the research result, one of the strongest hypothesis was formed
Based on the prior research result, for those committed learners, time management has a huge impact on the learning, reminder or calendar were the most used tools that had been mentioned in the research. Thus, a seamless way to connect current learning flow to their (the learners) scheduling tool is the key.
Since the project reminder is an experimental feature that aims for testing the impact for Pro learners’retention, the team decided to make it as the MVP, which leads the focus to an effective and efficient product design approach.
The design decisions were made with two main considerations:
We selected the most common UX pattern when integrating 3rd party scheduling services by making the scheduling steps in a modal view with pre-filled learning-related information, such as where they were at in the learning, pre-set learning duration, and the URL to go back to where they left.
The design looks easy at first glance, but as the concerns I listed below, I've tried different design conbinations with button styles, icon with and without labels, and different types of micro-interactions for the best result that fit into existing design system without breaking the information hierarchy.
Codecademy does have a design system, but because of some technical reason, not every screen on the platform follows it. And design system does not have everything. Thus, add new element to a screen would add on the complexity.
To keep the information hierarchy, we adjust numbers of the original call to actions on institials, and add the reminder call to actions with the simplest style with micro-interaction to indicate learners as the call to action objects.
The reminder feature archives three success metrics we set for this project. Overall, what we’ve learned from this feature are:
Other habit formation solutions could be future potential feature development, another focus on guiding to help the learners to set up the learning goals based on their needs and capability might also be a direction to help learners to be successful in their learning.
I would also like to explore what are other options besides daily streak, reminder, and code challenges could be an effective goal achievement for the learners if we keep working on this project.