Product Strategy

Feature
Prioritization

Stop building features nobody wants. Ask your users what they actually need - directly in your app.

Quick Answer

Use targeted in-app surveys to validate feature ideas before building them. Ask users who actively use related features what they want next. FeedbackWall lets you target specific user segments and collect structured feedback that feeds directly into your roadmap decisions.

The problem

Why most roadmaps fail

❌

Building on assumptions

Teams build what they think users want, not what users actually need.

❌

Loudest voice wins

Features get prioritized based on who complains most, not what helps most users.

❌

No validation

Features ship without knowing if they'll solve real problems.

✓

The solution: Ask first, build later

In-app surveys let you validate ideas with real users before committing engineering resources. You get data, not opinions.

Methods

Three ways to gather feature feedback

Direct ranking surveys

Present 3-5 potential features and ask users to rank them by importance.

Example question: "Which of these would be most valuable to you?"

Dark mode
Offline support
Team collaboration
Advanced export options

Best for: Deciding between a few clear options

Problem discovery surveys

Ask what frustrations or limitations users experience. Let them define the problem.

Example question: "What's the most frustrating thing about [feature area]?"

Best for: Finding problems you haven't identified yet

Feature usage satisfaction

Survey users right after they use a feature. Low satisfaction = opportunity for improvement.

Example: After exporting, ask "How satisfied are you with the export options?"

Best for: Identifying features that need enhancement

Targeting

Ask the right users

Not all users should weigh in on every feature. Target your surveys strategically.

Power users

Ask about advanced features. They know the product deeply and can articulate needs clearly.

traits: ["usage": "heavy"]

Recent converts

Ask about onboarding and getting-started features. Fresh perspective on friction points.

traits: ["signup_days": "<30"]

Paying customers

Ask about premium features. They have skin in the game and higher expectations.

traits: ["plan": "pro"]

Feature users

Ask about improving features they actually use. Trigger surveys contextually.

trigger: "export_completed"

Implementation

Setting up with FeedbackWall

1. Identify users with traits

Pass user attributes when identifying users so you can target surveys later:

// After user logs in
FeedbackWall.identify(
    userId: user.id,
    traits: [
        "plan": user.subscriptionPlan,
        "signup_date": user.createdAt,
        "feature_usage": user.mostUsedFeature
    ]
)

2. Trigger contextually

Show surveys at moments when the feature is relevant:

// After user completes export
func exportCompleted() {
    saveExportedFile()
    FeedbackWall.showIfAvailable(trigger: "export_completed")
}

// After using search extensively
if searchCount > 5 {
    FeedbackWall.showIfAvailable(trigger: "search_power_user")
}

3. Review in dashboard

See responses grouped by user segment and identify patterns across different user types.

Best practices

Tips for better feature feedback

Don't lead the witness

Ask "What would help you?" not "Would you like feature X?" Leading questions give biased results.

Limit options

When ranking, keep it to 4-5 options max. Too many choices overwhelm users and reduce response quality.

Include "other"

Always allow open text for ideas you haven't thought of. The best insights often come from write-ins.

Survey periodically

Run feature surveys quarterly, not constantly. Give users a break and give yourself time to act on feedback.

FAQ

Common questions

How many responses do I need?

For ranking surveys, 100+ responses give reliable patterns. For open-ended discovery, 30-50 often reveal key themes.

What if users want everything?

Force ranking instead of yes/no. Users have to choose, revealing true priorities.

Should I share the roadmap?

Optional. Some teams share what they're considering; others keep it private. Both work.

How do I combine with analytics?

Use analytics to identify underused features, then survey to understand why. Data + context = insight.

Build what users actually want

Use FeedbackWall to validate feature ideas before committing resources.

Start free trial →

14-day free trial. iOS native SDK.

FeaturePrioritization