There are customers that are easy to get feedback from and who are qualified for beta testing. And then there are customers who aren’t. How do you choose?
Tips and tricks for building great products
Open customer feedback can be scary. What if someone asks for a “faster horse”? You’re going to have to build it, right? Nope.
Most companies focus on transparency for customers as the main benefit of having a public product roadmap. However, there’s a whole other side to it.
62% of product managers say that their biggest challenge is to validate whether the market needs what they’re building.
Product roadmaps—whether they’re internal or public—are a great asset for any SaaS company. However, they’re only truly useful if a few key practices are followed.
If you’ve worked in a customer-facing role at a SaaS company, then you’ve received feature requests before. How do you manage these customer expectations?
Internal product roadmaps have benefits way beyond keeping development work organized. Getting to them requires pulling them out of their narrow context.
When people think of “feature voting tools”, they imagine a basic upvote-downvote system. However, feature voting has come a long way since then.
Rejecting customers’ ideas is never easy. However, the right tone and attitude can make a huge difference. Here’s how to say no to feature requests the right way.