Zwift ran on a proprietary system called Support Portal. This tool hosts all of the platforms customers, progress tracking, and all content. It is a complex system that has been built over time and with little to no design direction since its’ inception.
There began to be a strong need to create a more streamlined way for the company to produce content. The system as it was set up allowed for only certain types of content to be implemented, and in an unproductive way.
The problem became:
How can we create a new tool that does all the things the old one could do, plus be scalable for new content types?
My role
Lead Product Designer
Team
Cross-functional product team. Including:
- Project Manager
- Engineering Manager
- Systems Architect
- Web Developer(s)
- QA Tester
- QA Automation Engineer
Problem / Challenges:
Early discovery efforts uncovered several processes at play in the production of content in the platform. The main use case is “Event Creation”. This became the basis of all discovery, because it used all the relevant pieces of functionality in question.
We documented all the pain points that stakeholders were experiencing and made sure these were addressed first in the creation of a more streamlined tool.
Discovery
Solution:
The solution became titled “Progression Content Tool” to remain generic and that it is a flexible tool to be used for all of Zwift’s content. V1 of the new tool would generate newer pieces of content (missions, quests, etc.) and as it is proved and iterated, all content will then be migrated to the new tool.
Final Solutions
Hi-Fi dev ready designs in Figma