Create a destination where Reverb users can engage with what they own and be inspired to make their next sale or purchase.
Have a clear overview of what they own and what it’s worth. Keep track of how they enjoy configuring their gear, and find opportunities to fill in gaps in their collection. Share their knowledge with other Reverbers.
Create a feature that unlocks inventory that may otherwise go unlisted and leverage the expertise of our Reverb community to make the buying and selling journeys more likely to lead to purchases and sales.
To create scope constraints for the MVP, we identified a specific goal and a specific hypothesis for how we might reach that goal. We believed that by creating a destination on Reverb where users could keep track of what they own and what it is currently worth, we could entice at least 1,000 users to create a gear collection. We felt that would be enough of a signal that there was real demand for this feature. It would also give us a large enough sample size to observe how the feature was being used (or not used) and to have a pool of users to speak with directly to gain insight for future features.
We looked at other collection-oriented websites to get inspiration for how items are created and displayed.
Early on in the design, I was directing the product designer focused on gear collections. After the release of the MVP, this designer rolled onto a different squad and I took over the product design.
We collaborated on the customer journey and user flows to establish where a user enters the experience and what the steps are to create each collection item.
In order to meet our deadline, we parallelized much of the design and engineering work. Designers quickly went from user flows to a prototype in Figma while engineering was working on the backend. Having the prototype not only made the layouts clear, but also the interactions, once engineering was ready to work on the frontend.
Design was then able to put the flow in front of internal users early and validate the experience before launching the MVP.
Product worked with product marketing to identify users who had a regular purchase history on Reverb, which we felt was the ideal target user.
We released the MVP and immediately conducted qualitative research with a panel of users, alongside measuring adoption and engagement.
In addition to usability testing the MVP, we also introduced prompts to begin getting signal for evolution beyond the MVP.
MVP launched in 10 weeks to 1,000 users, including selling flow and automatically adding purchased items to users collections. By end of Q3 there were 100k collections with 500k items in them
