´╗┐Track Blaster - CMS

CHALLENGE AND GOALS

Track Blaster is part of UnitedMaster's internal tool system. The purpose of this CMS is to manage, organize and preview tracks. The users are our internal Artist Support team (OPS). 

By conducting internal stakeholder interviews, we identified the challenge and goals. The internal team wanted an easily digestible experience to organize, filter, and mark tracks. Another goal was to present a more detailed view of a track's analytics such as; all-time numbers in streaming, social followers, audience location, and playlisting. All in all, we needed to present track data into interesting, digestible visual content. 

CREDIT

Kelly Ioerger - Product Designer 
Stephen Blake - Product Lead

PROCESS
The Product Development process consists of an opportunity backlog where we would create a vision board and brainstorm ideas. Understand the opportunities, and understand our stakeholders. Define the problem, validate, evaluate, and refine it. After this cycle of understanding and defining, the team would create a product roadmap and prioritize a backlog of epics and stories for the feature. 
My main responsibilities on a day-to-day basis were to create, explore, validated, and refine.

SCOPE
Approximately 4 weeks end-to-end from research to high fidelity hand-off. Then ideally a post-mortem after launch.

INSPIRATION
Before diving into the explorations of Track Blaster CMS I first did some benchmarking research on other CMS experience flows.

Top Tracks Desktop Filter 32

The main features of the dashboard are a filter component, a table that displays all the data for each track, and a menu to mark tracks as fraud, or quality, and add them to the A&R list. 

View the prototype´╗┐

Track Details Desktop

More insight into the track details was a challenge in how to display the data in a more digestible way. Reviewing the stakeholder interviews we prioritized the data based on what our internal team wanted to view first. We also created two versions of the graph so the internal team could toggle views. One other main feature the team requested was a visual performance rank (billboard progress). 

View the prototype

LESSONS LEARNED

Learning from internal stakeholders and having continuous feedback from the internal team was an advantage and success for Track Blaster. By providing the cycle of conduct build, learn, and measure cycles, review and improve, then analyzing what happened provided a seamless process of creating and validating Track Blaster. 

What is on the horizon? 
Similar to Track Blaster the next generation of our internal tools will be for Producers and the Beat Marketplace. Beat Blaster - where the Ops team can manage, organize and mark beats.