SKIO is a curated community where artists and labels can network, engage in direct licensing deals and access tools to collaborate. Labels can uncover the next big talent while earning revenues and engagement insights for content owners. Below is some of the work I've done during my time at SKIO.
Research, UX, UI
Users can browse among newly uploaded music label content from for the next track to remix, or check out content from other users that they want to collaborate with.
PURCHASING A REMIX LICENSE
Creators want to create, not worry about paperwork. SKIO's platform enables instant purchasing of top quality audio stems from any track on the platform without dealing with complex contracts and legal procedures.
ARTIST GROWTH METRICS
SKIO allows artists to explore their fanbase analytics and strategically target collaborators in specific genres or geographic markets. Analytics provide valuable insights for artists developing their careers and record labels seeking talent.
PARTNERS ENGAGEMENT DASHBOARD
SKIO collects data and analytics on remixers who engage with label content and deliver insights and trend reports so labels can learn about their fans.
Through communication with the SKIO Community and hours of interviews with users and other stakeholders, we were forming a picture of what SKIO should aim for. In the end, the hypothesis was that artists want to get signed and labels want to find the hottest talent. The SKIO creative marketplace was the way to enable that.
To keep growing the userbase, and expand the content catalogue, SKIO needed to provide value in order to create engagement. To achieve this, we developed a model for how we would deliver that value and through which tools.
Understanding the behaviour of our most engaged users was crucial for focusing on building the right features. After reviewing our site analytics , I constructed a list of six metrics that I believed correlated with lasting user engagement.
FROM NEEDS TO FEATURES
In parallel to understanding the pain points to solve, we needed to translate our solutions into concreate product features. As the list of possible implementations grew, knowing when to build was as important as knowing what to build.
Instead of User Stories, we used Job Stories to define motivation and context to de-emphasize any particular implementation. We framed every design problem in a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome.
To communicate the structure of the site to stakeholders, "wireflows" were created, combining wireframe-style page layout designs with a simplified flowchart-like way of representing interactions.
After defining and mapping out a feature, interactive prototypes were created where basic functionality and interaction could be tested and vetted. The prototype would be demoed to the team and receive feedback on viability and feasibility.
MOCKUPS & SPECS
Once the wireframes had been vetted and approved, sharp mockups would be created to show how the feature would look and feel in real life. After revisions, specifications on layout and implementation woudl be created for the development team.
After launch, each feature is monitored to see how it performed against the defined goals. These metrics are then used to measure progress towards key objectives, and drive product decisions.