Experience in creating a VOC repository?

26 Feb 2013 - 4:57pm
3 years ago
3 replies
3585 reads

Hey All,

I am working with a small product team with minimal resources. We are currently starting to receive feedback and would like to compile the information in a centralized repository. Essentially, we like to take a baby step into starting a VOC (voice of customer) space for the team reference and track over time. One that allows the team to easily filter and sort thru the information.

In the past I've used excel and sharepoint to do this—Does anyone have other suggestions?

Love to hear your thoughts and thanks in advance!



27 Feb 2013 - 3:45pm

Hi Leslie

We have been working on something like that internally - and have discussed the same with clients. One challenge, it seems, is that you need to support an ever- changing taxonomy of issues. So the question is how much structure to impose in advance in terms of categorization of new issues / feedback by issue type or by the area or function that the issue pertains to. We've assumed that bug-tracking systems are the closest model for this, but there are important differences. What do you view as the MVP functions for this to meet your needs?


27 Feb 2013 - 5:40pm

Excuse my ignorance Nick, but how are you defining MVP? Right now, I am only thinking Most Valuable Player ;)


28 Feb 2013 - 8:25am

Excuse my annoying use of an acronym. MVP = Minimum Viable Product


I was only asking what basic functions you had in mind to address your goals. I really should have spoken English. :-)

Syndicate content Get the feed