This project was something I pushed up the roadmap and stressed the importance to stakeholders to prioritize, backed up by user research. As I gained continuous feedback from users, I noticed a trend that correlated with data analytics around conversion and engagement of a core product feature, Journeys. Well was built around our 21 day habit building Journeys that were very content heavy followed by a tracking experience. These Journeys were built very rigid, in both the code and the experience. Users were forced to complete the content before they would be able to track their habit and see their progress. This was a major hurdle for users who didn’t see any value from this content and got the most value from tracking. This project was aimed to create flexibility and optionality for the user, decoupling our content and tracking and allowing users to choose their own path. The way I designed this also created scalable pathways towards libraries of trackers, separated content and “next steps”, a personalized sandbox post-track that served up relevant widgets (content, insights, etc.).