For SaaS product teams
Feature Feedback Survey Software
A new feature is only as good as the cohort that finds it easy to use. Survey users right after they try it, while the experience is fresh.
Mapster fires in-app surveys after a user completes a feature for the first time. Every response is linked to the user, the plan tier, and the role, so teams can segment by cohort and see which users find the feature easy.
In-context feature feedback beats broad NPS
A quarterly NPS tells you how users feel about your product. A feature feedback survey tells you why. The first is a thermometer. The second is a diagnosis.
96%
of high-effort users become disloyal (Gartner/CEB). Feature effort is the same effort.
20-40%
response rate for in-app feature surveys versus 5-15% for email.
<24h
is the window for capturing accurate feature feedback before users reconstruct the experience.
Three feature feedback scenarios
The right metric and trigger depend on where the feature is in its lifecycle.
After first use of a newly shipped feature
Trigger: Custom event fired on first successful completion of the feature
Metric: CES + open-text follow-up
"It was easy to use [feature name]." (CES 1 to 7)
The week after launch is when feature usability problems are most visible. Surveying every user who completes the feature on day one gives you a fast read on whether the design works for real users.
When running a feature variant test
Trigger: Custom event fired with variant attribute (A or B)
Metric: CES + CSAT
"How easy was it to complete [task] just now?" (CES 1 to 7)
Pass the variant as a custom attribute so you can compare CES across A and B. Combined with a usage metric, this tells you whether one variant is winning because it is easier, faster, or just more discoverable.
After a user has used the beta feature 3+ times
Trigger: Session count >= 3 on the beta feature
Metric: PMF + CES
"How would you feel if [feature] was removed?" (PMF) + "How easy is it to use?" (CES)
For beta features, you care about both usability (CES) and demand (PMF). A feature that is easy but nobody would miss has no signal. A feature that users would miss but find difficult has a redesign opportunity.
Which metric for which question
Three different signals. Each one answers a different question about your feature.
Is the feature easy to use?
Default choice for usability. Strongest predictor of whether users will adopt the feature long-term.
Learn moreAre users satisfied with the result?
Use when the feature delivers an outcome and you want to know if it met expectations.
Learn moreWould users miss it if it was gone?
Use for major feature launches or beta opt-ins where demand is the question, not usability.
Learn moreA feature can be easy for one cohort and broken for another
An overall score of 5.2 hides that admins love it and end-users cannot find the button. Segmentation is where the design fix lives.
Without segmentation
“Mixed. Hard to tell what to fix.”
- Cannot tell which role finds the feature confusing
- Cannot tell whether free or paid users adopt it
- Cannot prioritise where to invest design effort
With segmentation
Action: redesign the end-user entry point, run a feature tour for free users.
Feature feedback survey best practices
Six rules that separate feature surveys that ship roadmap items from the ones that pile up in a dashboard.
01
Trigger on success, not on entry
Fire the survey when a user finishes the feature, not when they open it. A user who clicked in and bounced gives noisier feedback than one who completed the workflow. Define success per feature: a saved object, a sent message, a confirmed action.
02
Keep it to 2 questions
One rating, one open-text. The qualitative answer is where the design idea lives. Surveys longer than 3 questions in-app see completion rates below 40%.
03
Tag every response with the feature variant
If you are running an A/B test, pass the variant as an attribute. If the feature has a free and a paid version, pass the plan. Without these tags, you have an average. With them, you have a cohort comparison.
04
Cap the audience to recent first-time users
Only survey users who completed the feature for the first time in the last 24 hours. Power users who have used the feature 100 times give different feedback than first-time users. Each is useful, but mixing them muddies the signal.
05
Route low scores to product in real time
A CES of 2 on a newly launched feature is a usability bug, not a customer service issue. Send a Slack alert to the product lead so they can investigate the same day, while the user session data is still fresh.
06
Sunset the survey after a sample
Do not keep a feature survey running forever. Once you have 200 to 500 responses (enough for cohort analysis), turn it off. Otherwise it becomes background noise and stops getting acted on.
How to set up a feature feedback survey in 3 steps
Fire from a custom JavaScript event, no redeploys needed to change questions or trigger conditions.
Pick the success event
Identify the moment a user has actually finished the feature: a saved object, a sent invite, a confirmed action. This is the trigger. Fire a custom JavaScript event from your code at exactly that moment, passing user ID, plan, role, and feature variant.
Build the survey from a template
Start from the CES template inside Mapster. Edit the feature name in the question. Set the trigger to match your custom event. Add an optional open-text follow-up. Choose whether to suppress for repeat users (recommended).
Watch the cohort breakdown
Responses arrive in your dashboard with user, plan, role, and variant attributes attached. Compare scores by cohort to find which user type the feature is failing. Route low scores to your product lead via Slack for same-day investigation.
Frequently asked questions
Survey your next feature launch
Trigger CES, CSAT, or PMF after first feature use. Tag every response with plan tier, role, and variant. Find the cohort the feature is failing and fix it.
Run a Free Feature Feedback SurveyNo credit card required