Feedback: Too much of a good thing?

One my my favorite quotes from Pragmatic Marketing is "Your opinion, while interesting, is irrelevant."  I've been thinking about it a lot recently because I'm aggregating internal feedback about the direction for the redesign of one of the products that I manage.  When is feedback too much of a good thing, and when do you finally say your product is ready?

Aggregating feedback is one of the most frustrating and rewarding parts of product management.  Custer feedback can open your eyes to some of the problems you couldn't have seen yourself.  It is this feedback that will drive your product to success!  Internal feedback and support is extremely necessary, but can sometimes be difficult to decipher.  Not only that, but when do you stop collecting feedback?  I find that too much feedback can send you down a rat hole, kind of like "too many cooks spoil the broth".  At some point, product managers need to rein everyone in and say that we're ready to develop.  This blog gives a good overview of how to aggregate and deal with feedback.  I enjoyed reading it!

A few helpful resources:
I don't have an answer to when you can stop gathering feedback.  I think there is a right and a wrong way to collect it.  At the very least, focus on the customer and what they're looking for.  If your solution(s) solve some of the problems they're having - you'll see success in your product!

Any thoughts on this?  Can you put a time estimate on when to stop collecting feedback?  As product managers, do we have to manage the feedback loop?  And if we do, how to we close the loop?  Does anyone else feel like they're in a constant state of "feedback aggregation"?

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.