Should you have a public roadmap?
Public roadmaps show everyone what you’ve been working on. This can be a little intimidating. So, should you have a public roadmap, or are they a bad idea?
Tips and tricks for building great products
Public roadmaps show everyone what you’ve been working on. This can be a little intimidating. So, should you have a public roadmap, or are they a bad idea?
There are many benefits to having a public roadmap. However, finding good public product roadmap examples can be hard.
Most of us have used a spreadsheet as a product feedback “tool” at some point. However, there comes a time where a solution that simple isn’t enough.
Product and support are often portrayed as the two parts of a business that just “can’t get along”. Improving communication between these teams can be challenging.
You’ve built a piece of software. You think your product value is through the roof. It’s useful, functional, and overall amazing. There’s a problem, though.
Effectively communicating a product roadmap can be tricky. Here’s how to tailor the information to different stakeholders.
Many of us like to think we know how to give good feedback for a SaaS product. However, that might not always be the case.
As a product manager, it’s natural for you to feel like your product is your “baby”. However, being overprotective isn’t good for you or the product. Here’s how you can make sure not to get too attached.
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?