Be nice. Or else.
Joined about 2 years ago
=> Usersnap: it's similar to Invision, however, it also allows you to use it on html prototypes and for website feedback.
(great thing: we get notified directly inside a Slack channel when someone leaves a new Usersnap feedback)
My favorite podcasts are:
A while ago, I also wrote this article on some of my fav podcasts: http://usersnap.com/blog/web-development-podcasts/
Thanks for sharing your insights! I started to work on two chatbots (for some side projects) as well, and learned A LOT on how people communicate. :) Thanks for sharing your insights!
As I had experience with both ways (not transcribing entire interviews + transcribing them) - I see the following pros + cons:
Pros of transcribing interviews: + you have the entire interview at your finger tip, searching for certain words is easy when you have the entire interview. + people do not listen to the audio files (at least that's my experience) + having a written document helps to provide further context
Cons of transcribing interviews: - transcribing takes time (or costs money) - some transcripts might never be used
All in all, I think that it's more important to have a summary of the key points of each interview somewhere easily accessible.
I've used rev.com in the past for transcribing user interviews. It's a great service and works super fast (usually you get the ready transcript within 24 hours).
Awesome post and great inspiration! :)
I like this one as well ;-) #freecookie https://usersnap.com/404
I completely second that! There are so many projects/situations where I see myself in such a situation. What I found helpful was trying to stay focus. I know this sounds kind of obvious, but if you think about ways how to stay focused (and on track on your projects) you get work done (and finish it). I recently published this post about staying focused and productive which may help others too: http://usersnap.com/blog/productivity-tips-web-developers-efficient-time-management/