Lead Designer
I designed the MVP for RCreator - a web application for musicians to discover, participate, and host remix contests.
2 Front End Developers
2 Back End Developers
1 Product Designer (me)
UX Design
UI Design
User Research
12 Weeks
Aspiring hip hop / electronic music producers need a way to showcase their talent to established players in the music industry.
To kick off the project, I sat down with RCreator founder Jeremy Ma. I tried to pick his brain around two key areas: business goals and technical constraints. Here were my takeaways:
🤔 Problems and Solutions at this stage of the project
I conducted seven interviews, six of which participated in past remix contests, one of which hosted a remix contest. Findings were distilled into provisional personas and storyboards in the next design phase.
Questions asked included:
🤔 Problems and Solutions at this stage of the project
I analyzed existing remix apps on the market, read through reviews, and captured screens of key user flows.
I created a provisional persona (Adam Howard) based on qualitative data collected from interviews in the previous stage. Every design decision I made throughout the project was to move Adam closer towards his ultimate goal - to get recognition as an artist.
To help narrate who Adam was and what problem we were helping him solve, I created a storyboard.
To help clarify my research findings, I combined Adam's goal with RCreator's business goals and technical constraints into this diagram:
I also sat down with the RCreator team to re-define our project goals. Here were our conclusions:
User flows were created to clarify how Adam would accomplish key goals within the app.
Low fidelity wireframes were sketched based on user flows defined in the previous step.
Once I established the structure of each screen, hi fidelity mockups were designed.
Problem - When I was nearing the completion of the hi-fidelity design stage, our team realized there were still a number of essential (but not initially obvious) user tasks not woven into the app:
Solution - I eventually had our team write down every essential user task still undefined. My solution (although not elegant) was to rework (or create) various screens to accommodate these new set of tasks. This was a major lesson for me to define every possible user task earlier in the project and create more detailed lo-fidelity wireframes. This would have saved our team many hours of work.
🤔 Problems and Solutions at this stage of the project
Through userinterviews.com, I recruited 5 users that resembled our target persona - all were passionate musicians looking to make a name for themselves in an ultra competitive industry. Participants were asked to complete a series of tasks:
A common problem was shared by all participants - they didn't fully understand the purpose of RCreator when first landing on the homepage. One user thought it was an online community for musicians, one assumed it was a music blog, another thought it was an artist's database. Creating a persuasive, information-rich homepage quickly became a high priority task in the next phase.
Before
After
The biggest lesson I learned during this project was the importance of user feedback. The information I received during our usability testing was invaluable, which I couldn't have received anywhere else. If I could take a time machine back to the start of the project, I would have sought this feedback earlier (and more often), ideally after the first lo-fi mockups were sketched. Various assumptions our team made would have been validated before diving into the time-intensive hi-fi mockup phase.
Click the image to open the prototype in a new tab.
After 12 weeks of hard work, the RCreator team applied for YCombinator and actually got invited for an interview. They were impressed with our work, but ultimately passed as the problem we were trying to solve wasn't big enough. Here is the email they sent us (click image to expand):