Every product team should care to build products that users love. But many teams, especially in a B2B context, don’t have enough, if at all, contact to real users/customers.
How can they build the right product, when they do not get a deep understanding of the user and her problems?
How often do your teams talk to an actual user? My response in 95% of all cases will be “not good enough!”
I’ve seen teams that get told, that user interaction is the job of the customer-facing teams, like sales or customer success/support. I’ve experienced how teams get told, that an executive who requested a feature knows the users best and the only job for the dev team is just to implement it.
I can tell you one thing: You’re wasting the best “resources” you have. Your product teams. Namely product manager, ux designer and especially the developers and testers.
All of these people want to solve problems. All of them are highly educated and skilled. Let them work on the problems that matter most: Your customers problems.
Give your people the purpose of why they want to implement something and you will be positively surprised how much they will care about the customer/user. They will come up with completely new solutions and most likely even new innovative products.
“But that’s too expensive”
I’ve heard this couple of times. Developers are so expensive, that’s what product managers are for, if they not are purely backlog administrators.
In this series I want to show you how you can create a product feedback machine and why it’s important to involve the entire team. Why this will enable you to create the most important factor for real agile development: A fast feedback loop.
Some of the topic I’ll cover within this series:
- How to deal with sales (feedback)
- How to collaborate with your internal stakeholders
- Interview with three people, always!
- Why representative data is overrated
- Your product is the best source for feedback, use it!
- How to organize and share all the collected feedback
- Get fast feedback on your solutions. No code required
- How to share your roadmap publicly to get even more feedback
- Reduce the overhead by automation
In most parts this series covers the first steps of the product discovery: value – what do your customers value and which problems are worth solving. But will also help you while dealing with the usability risk.
Is there anything missing? What are your biggest hurdles, when it comes to user/customer feedback? I love to talk about it – just get in touch.