Bonnier - Brillbee
The challenge
Our goal was to develop a new tool for creating online courses, moving away from the outdated EPI server method. Rather than having someone at Bonnier develop the courses, the authors themselves could create them.
In this project i used the very effective MoSCoW method (Must have, Should have, Could have, Won’t have) with internal stakeholders to prioritize features for the new tool’s first version. Next, we met with the main user group (the course creators) and provided them with poker chips and cards representing features. They sorted these cards into “buy,” “want to buy,” and “not necessary” with each card assigned a cost based on size and development time.
This process prioritized features for a minimum viable product and set user expectations, clarifying that not all features could be included at once and allowing them to choose the most important ones.
Based on interviews and research, I created a flow chart to guide design decisions and developed a simple prototype, which I tested with the same stakeholders before finalizing it in high fidelity. While designing components, I established a design system in Sketch to efficiently manage design elements and implement large-scale changes. This approach ensured a coherent and user-friendly design.
I created new branding and a design system that felt simple and user friendly.
Development
Collaborating closely with our two developers, we built the tool iteratively, integrating design and code to avoid a waterfall approach. Course production on Brillbee transitioned from the EPI server to the new tool, significantly improving workflow. This change allowed external profiles to create courses independently, reducing the workload on our internal producers and enabling them to focus on adding more value.