Overview
Increase the usage frequency of Remesh and make it the go-to tool for quick qualitative research
Problem
Running a Remesh conversation is a high stake and expensive undertaking. One conversation could take up to 2 weeks to set up and could cost a minimum of $5k. This has made Remesh a high-cost, low-usage tool.
Solution
A simple change in allowing one button to be the one-stop-shop for all user’s needs on Remesh. Giving Pulse a differentiating brand from the rest of the offerings.
Solution
Use our proven researched-backed templates to give the users a starting point for the research that they can customize or edit before or during the conversation.
Solution
The single most important part of this flow is the ability to request an audience instantly with a click of a button. The user does not have to decide the audience breakdown in advance or the date and time of the conversation. On Launch, a user picks the audience demographics and starts the conversation – this step cuts 3-5 days of work.
Research
When I first started to research the problem above was to identify the reasons behind the high cost, low usage, and long set-up process of a Remesh conversation. After a range of internal interviews and speaking to our clients, it was evident that the main issues are:
Solution
As a team, we had two ways to address the problems, find a cheaper and faster sample alternative to our current traditional sample providers and optimize the UX of the conversation setup process to match the instant feel of the sample.
Solution
At Remesh, we have used Amazon’s Mechanical Turks service since the inception of the Remesh app. It was a way for us to quickly test the participant experience and our voting algorithm. Over the past 4 years, Remesh has built credibility and likeness within the Mechanical Turks community.
Solution
After we released the Mechanical Turk integration internally and externally with some of our clients, we realized pretty quickly that we needed to optimize the user experience so it aligns with the fast nature of the Mechanical Turk recruits.
Solution
After we released the Mechanical Turk integration internally and externally with some of our clients, we realized pretty quickly that we needed to optimize the user experience so it aligns with the fast nature of the Mechanical Turk recruits.
Outcome
We released Remesh Pulse and we already started selling to clients who could not historically afford Remesh, expanding our use cases and client base.
Outcome
We released Remesh Pulse and we already started selling to clients who could not historically afford Remesh, expanding our use cases and client base.
Next steps
Evaluate user adoption, expand the demographics of the audience and create more Pulse templates.
