Show HN: An easier way to manage beta tests & get insightful feedback
userdiary.com
userdiary.com
Our mission at UserDiary is to break down barriers between product people and their users. Our goal is to make the process of qualitative user studies painless for the researcher and the participants, so that feedback can be shared freely and data is organized to yeild the clearest insights. The end result, we hope, are better designed products and happier users.
Right now we're in closed alpha with a very raw MVP. But I'd love to hear your thoughts and feedback. Thanks HN community!
The other half of it is to organize the data automatically so that each user's personal story comes through. One way to do that is to get people to register for some blog like tumblr and post to that, but that's a lot of responsibility on your tester and will likely reduce their response rate.
We aim to fix this tradeoff. And we free up your time to actually act on the feedback and insights.
Also, we've got a bunch of ideas to make it richer beyond just emails--lean startup MVP...maybe we were too minimum here?
Think of it as if you wanted each user to use Posterous to send feedback, except their blog is already private, and they just reply to an email prompt from you to post to it.
Does that make more sense and seem valuable? How might you rephrase the last 2 benefits to make it more clear?
It didn't look bad, but wasn't particularly relevant to feedback management either.
The target right now is for people who want to collect a lot of qualitative feedback over time from a select user group. Use cases include beta tests or a screened users from a particular segment (new users, freelancers vs. enterprise, etc.). The goal is to understand user behavior so you can solve real pain points or tweak your value prop to reach them better. One powerful reserach technique is user diary studies (which is where we got our namesake).
We think that user diary studies can be pretty powerful, but they take a lot of time and effort to run. All methods out there are a trade off between ease of use or high maintenance. We want there to be free communication (more qualitative data) yet preserve organization (each user gets their own feed). That way, over time, you get a rich story about Jane, the freelance designer in the midwest, versus John, the cupcake shop owner in Manhattan. Then you can really understand what's driving user behavior for each, and you can take those insights and focus your product accordingly.
405 Method Not Allowed
The method POST is not allowed for this resource.