← Back

Improving the content scheduling process

At Macademia, all of the content on the Azoomee and Da Vinci apps need to be managed and scheduled, by the in-house content team. With hundreds of videos and games, a dashboard management system was created to help facilitate the content scheduling and management side of the operations.

My Role

User Research, Information Architecture, Wireframing and Prototyping.

The Challenge

The specific content (types of videos and games) that the user could view on their app depends on their location, language settings, age preferences, and their device/OS. Before, the scheduling process at Macademia required an excessive amount of spreadsheets, inefficient workflows, and tedious repetitive tasks. This project aimed to provide a solution to this, to design an appropriate user flow and interface that allowed the content team to successfully upload a variety of content in bulk, across different territories, and platforms.


The Solution

To address the issues with the existing scheduling process, the CMS (Content Management System) underwent a drastic redesign. A small team consisting of myself, the designer, and one Java developer, were able to restructure and build a new user interface. This now meant the content team could bulk update content feeds across multiple territories and platforms, all in a few clicks.



Organising meetings with key stakeholders

For the redesign of the CMS to be successful, I had to understand exactly what it was the content scheduling team did. I organised frequent meetings with the team so that I could understand their pain points, frustrations, but also their wants and needs going forward. This was essential as before these sessions took place, the content scheduling process was alien to me.


Mapping out the existing user journey

Wrapping my head around the content scheduling process was tough at first. It was only until I mapped it out that I was able to revisit the rest of the team and iterate on the flow diagram to see if I fully understood it. After a few iterations, I was able to see exactly where it was that their main issues lay. This provided my first visual representation of the process and was an excellent reference point going forward with the redesign.


Adapting the information architecture

Once I understood the user flow, I had to group together all of the separate entities that the content team attributed to the scheduling process. These 'entities' included things such as territory, categories, and languages. The content team had to have an interface where they could assign all of these entities to the unique content type. Therefore the information architecture of this updated CMS had to be in a logical format for the scheduling workflow to make sense.


Wireframing to UI

The wireframing process again involved frequent meetings with the content team. The iterative nature meant that I could nail the structure, layout and general UI design fairly quickly. The clickable prototypes were created in Figma and tested on the team members. However, the UI itself was built from a component library called Vaadin (a web app development platform for Java), so there wasn't much need for a bespoke UI design.

← Back