{"id":2921,"date":"2021-06-05T09:00:00","date_gmt":"2021-06-05T07:00:00","guid":{"rendered":"https:\/\/usersnap.com\/?p=2921"},"modified":"2025-04-13T20:05:34","modified_gmt":"2025-04-13T18:05:34","slug":"how-usersnap-adds-new-product-feature","status":"publish","type":"post","link":"https:\/\/usersnap.com\/blog\/how-usersnap-adds-new-product-feature\/","title":{"rendered":"Your next product feature, backed by product feedback."},"content":{"rendered":"\n

Did you ever release a “game-changing” feature in your eyes, but no one used it<\/a>? In addition, was it even inconvenient for your customers? We’ve heard the horror stories, and created a few of our own along the way. The one thing missing for your product feature: product feedback!\u00a0There is no doubt: releasing the right product features is a cornerstone for every SaaS company’s business success. It brings about product-led growth<\/a> and helps your SaaS scale.<\/p>\n\n\n\n

In this post I\u2019m going to show you how we handle product feedback questions and implement new product features. Everything backed by product feedback.<\/p>\n\n\n\n\n\n\n\n

Side note: for all your customer feedback needs, come check out our ultimate guide to customer feedback<\/a>.<\/b><\/p>\n\n\n

Try Usersnap for Feedback Collection<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

Gathering product and user feedback for your next product feature<\/h2>\n\n\n\n

In other posts I\u2019ve shown you how we interpret and live up to the \u201crelease early, release often\u201d paradigm<\/a> of software development. With that in mind, managing a newly launched product and thinking about the vision and roadmap of your product isn\u2019t that easy.<\/p>\n\n\n\n

We think: The more information you have, the less risky it is. Although, you might have been thinking, Why is product feedback important?<\/b><\/p>\n\n\n\n

Asking customers about the job which needs to be done<\/h2>\n\n\n\n

Continuously ask yourself (and others too) about the problem which your product is solving. Ask for that problem. And verify the solution you\u2019re offering through customer interviews. Here\u2019s how we, at Usersnap, conduct our product feedback survey<\/a>.<\/p>\n\n\n\n

The product feature matrix<\/h2>\n\n\n\n

Our product team basically handles the product roadmap with a so-called feature matrix<\/b>. To be honest, it isn\u2019t that complicated as it may sound. The feature matrix at Usersnap is a Google spreadsheet<\/a> which looks like this:<\/p>\n\n\n

\n
\"product<\/figure>\n<\/div>\n\n\n

The feature matrix includes every new feature we or any customer or user like to see in our future product. Yes, any user. If a user tells us about certain feature requests we put that in the feature matrix.<\/p>\n\n\n\n

We give the request an expressive name (=desired outcome) and a short description (what the feature is about).<\/p>\n\n\n

\n
\"product<\/figure>\n<\/div>\n\n\n


\nWe then basically have 3 columns which are important for prioritizing new features. These are:<\/p>\n\n\n\n