Whose input should you seek?
When Sachin Tendulkar would fall for low scores, everyone would give him batting tips. There is a famous story of how a waiter in a Chennai hotel helped Sachin spot a defect in his elbow guard. However, such inputs are rare and often give the impression that every feedback must be acted upon.
We have to be deliberate in whose input we seek.
Feedback is supposed to be a flow of information back to us that helps improve whatever we are making. To help improve means it must be actionable. It also must be valid and objective.
We usually get advice that is broad and often unhelpful.
Broad feedback is vague, doesn't help you spot a key problem. I also want to cover negative feedback here. Receiving input thats something like your product doesn't work or your team is incapable is not helpful.
So, we shouldn't seek such input?
Not at all. Try making it actionable. If someone is passionate about sharing such input, take it to the next level. Ask them to explain the vague parts by seeking for details.
For negative feedback - if someone is so passionate that they share 20 things wrong with your product, thank them. Note all these points down because they have hit a chord.
Should you seek input from everyone?
I doubt if Sachin went asking every person for batting tips. You should be also choosy in whom to approach.
Here are some recommendations:
Users who love working with you and who care for your product.
Stakeholders who will be sponsoring your programs
The stakeholder input is to help create guardrails. You should inform them for significant updates only.
The users are the most important piece of the puzzle. They allow you to validate assumptions. These folks help you learn high quality FEEDback. Anything they say must be looked at seriously. Such passionate folks are rare to find.
For product development, a small number of users with one stakeholder is sufficient.
Keep the list small, high quality, and have a high touch approach.
That's it for today.
Happy Ideating!
Hemang.