Learn about Savio
- Getting Started
- How Savio Works
- Triaging Feedback
- Managing Users
- Closing the Loop
- Voting Boards
- Importing People, Companies, and Attributes
- Connecting Your Support Tool
- Chrome Extension
- Emailing Feedback
- Slack Integration
- Creating Feedback Templates
- Tips for Triaging Effectively
- Managing Custom Attributes
- Canned Filters
- Hubspot Integration
- Importing Historical Data
- Using Savio's API
- Setting “Feedback From”
- Exporting Your Data
- Feature Request Details Page
- Setting Up Savio
- How To Be Successful with Savio
- The Four Problems Savio Solves
- Segment Integration
- Help Scout Integration
- Zendesk Integration
- Intercom Integration
- Salesforce Integration
- Customizing Feature Request List Columns
- Customizing Feature Request Status Options
- Moving Feedback
- Savio's Integrations and Their Features
- Daily Digest Email
- → Running a Product Meeting
- Zapier Integration
- Voting on Behalf of (VOBO)
- Single Sign-On
- Configuring Voting Board Access
How To Run Your Product Meeting Using Savio
Savio solves four main problems:
It centralizes your customer feedback.
It helps you organize your feedback into feature requests.
It makes it simple to close the feedback loop and tell your customers when you build a feature they asked for.
And it helps you run the meeting where customer feature requests are communicated to the product team (we’ll call this the product meeting).
This article is about the last on that list: how best to use Savio to run your product meeting. We’ll cover:
Before the meeting: Triage your customer feedback
Use Savio to communicate status of requests that Product put on the Dev queue in the last meeting
Slice and dice your feature requests to decide what to build next
Before the meeting: Triage your customer feedback
The first step to using Savio in your Product meeting is to ensure your feedback is categorized into feature requests. Having your feedback categorized will give you an up-to-date view of what your customers are asking for.
To ensure your feedback is up-to-date, triage your customer feedback. We recommend having your feedback triaged a few days before the meeting. As good practice, we suggest regularly triaging your data—either at the same cadence as your product meeting or more often.
Use Savio to check the status of previous requests
With your feedback triaged, you can use Savio to run your product meeting. Savio can quickly give you a list of the features that Product has put on the development queue.
To find the features that are either planned, in progress, or shipped, do the following:
1. Log into Savio and navigate to the “Feature Requests” page.
2. Click the filter icon in the top right of the page. Then click the “Status” dropdown and select “Planned”, “In Progress”, and “Shipped”. Next, click “Filter Requests” to apply the filters.
Now you’ll have a list of the feature requests that Product has agreed to build. Go through each of the feature requests one at a time and ask for a status update. Change the status when appropriate.
To change a feature request’s status:
3. Hover over the feature request and click the edit icon.
4. Choose a new status and click “Save”.
Go through that process for each of the features until the status of each feature is reflected in Savio. At the end of this process, your team should have a complete understanding of what Product has built and what they’re working on.
Tip: When you mark a feature as “shipped,” don’t forget to kick off your close-the-loop workflow.
Slice and dice your feedback data to decide what to build next
After that process, you should know the status of existing feature requests. Now, you can discuss the data to decide what Product should build next.
As Customer Success, your finger is on the pulse of your customers. You know what they want because you’re constantly talking to them. But even though you know what your customers want, it can be hard to explain to Product everything you’re hearing.
Having hard data helps. Savio makes it easy to show Product what your customers are asking for and, most importantly, who is asking for what. Here’s how to use Savio to decide what features to build next.
To get a list of the features that you have under consideration:
1. On the Feature Request page, click the filter icon. Click the “Status” dropdown and select “Under Consideration”. Then click “Filter Requests”.
You’ll now have a list of the feature requests that are under consideration.
From here, you can slice and dice your data to figure out which feature requests you’d like to prioritize. Here are some potential ways you could do that:
Find the most popular feature requests
Find your most recent feedback
Find your most popular feature requests from lost deals
Find your most popular feature requests from churned customers
Find your most popular feature requests from enterprise customers
Option 1: Look at overall vote counts for each feature
One crude way to prioritize features is to simply look at the number of customers requesting a feature. This gives you a sense of its overall popularity. Higher vote counts suggest that a feature is more popular.
Here, the Salesforce Integration and the Permissions: Reader Role feature requests are the most popular with three requests each.
Tip: While it’s tempting to just look at what’s popular among everyone, this may obscure important information. For example, your “Free” plan subscribers may want one feature, but your Enterprise customers may want another. That’s why we suggest using your product meeting to drill down into the data to find out which features are important to your most important customers.
Option 2: Look at your most recent feedback
In our own product meetings, we typically spend some time to understand which features customers have asked for recently. To do that:
Click the filter icon and select the “Feedback received between” dialog box. Then choose your preferred date range. We typically use the “Last 30 Days” option. Finally, click “Filter Requests” to apply the filters.
Now you’ll have a list of the requests with counts of feedback from the date range you chose (for example, from the last 30 days).
These are the features with feedback given in the last 30 days. The “Feedback” column gives the count of feedback provided in the last 30 days for each feature request.
Option 3: Find your most popular feature requests from lost deals
Imagine your company had a goal to increase the number of deals you win. You could adopt a strategy of building the features requested most by lost deals. To find those:
Click the filter icon and click the “Feedback from” dialog box. Then select “lost deal” from the drop-down menu. Click “Filter Requests” to apply the filter.
This will give you a list of the features requested by lost deals.
In this case, there’s only one piece of feedback from a lost deal to feature requests that are under consideration and it was a request for a Reader Role permission.
Option 4: Find your most popular feature requests from churned customers
Now imagine your company’s primary goal this quarter was to increase retention. You could adopt a strategy of building the features requested by churned customers. To do it:
Click the filter icon and click the “Feedback from” dialog box. Then select “Churned customer” from the drop-down menu. Click “Filter Requests” to apply the filter.
This will give you a list of the features requested by churned customers.
In this case, two churned customers have asked for a Reader Role permission and one has asked for a mobile app.
Option 5: Find the most popular requests from your Enterprise customers
Maybe you want to increase retention by keeping your current Enterprise customers happy. You could choose to prioritize feature requests from your Enterprise customers. To do that:
Click the filter icon and click the “Plan (Company)” dialog box. Then select “Enterprise customer” from the drop-down menu. Click “Filter Requests” to apply the filter.
This will give you a list of the features requested by your Enterprise customers.
In this case, there are two pieces of feedback from Enterprise customers: one for a Salesforce integration and one for a Reader Role permission.
Once you’ve decided, change the request status to “Planned”
Those are just a few of the ways you could filter your feature requests to find out what certain customer segments are asking for. It gives you a powerful way to prioritize your feature requests to build a product targeted at a particular customer segment.
Once you and your Product team have decided what to build, change the feature request status to “Planned”. That way, at the next meeting, you’ll remember to follow up on its status. To change its status:
1. Click the edit icon.
2. Click the “Status” dropdown menu and select “Planned” from the list. Then click Save.
Get started with Savio
Looking for a lightweight and powerful way to manage your feature requests and customer feedback? Get set up with Savio on a free trial.Last Updated: September 20 2021