GoldenGecko
PlaybooksGuidesFeaturesPricing
  1. Playbooks
  2. /Retention
  3. /Create a public feature request board
Canny, Linear

Users request features in emails and support tickets that get lost

Create a public feature request board

Let users submit and vote on feature requests. Users who feel heard stay longer, and you build what actually matters.

RetentionBeginner
1-2 hours to set up, ongoing to maintain

When to use

You receive feature requests through scattered channels and want to centralize them.

Hypothesis template

If we create a public feature voting board, retention will improve by [target]% because users invest emotionally in the product's future and feel heard.

Method

The problem: Feature requests come in through email, support, Twitter, and DMs. You lose track, users feel ignored, and you build the wrong things.

What works: A public board (Canny, Nolt, or a simple page) where users submit ideas and vote on others. Top requests bubble up. You mark items as "planned" or "shipped."

The result: Users who submit feature requests or vote have 30-40% lower churn than average. They've invested in the product's future.

How to do it:

  1. Set up a feature request board (Canny, Nolt, GitHub Discussions, or a simple form)
  2. Seed it with 5-10 existing requests from your backlog
  3. Link to it prominently in your app: "Suggest a feature"
  4. Respond to every submission within 48 hours
  5. Mark items as "Under review," "Planned," or "Shipped"
  6. When you ship something requested, email the voters: "We built what you asked for"

Key insight: The board isn't about building what users want. It's about making users feel heard. Even declined requests reduce churn if you explain why.

Success metrics

  • •Feature submissions per month
  • •Votes per submission
  • •Retention rate of participants vs non-participants
  • •Shipped requests per quarter

Prerequisites

  • A feature board tool or page
  • Time to respond to submissions
  • A process for reviewing and prioritizing requests

Common pitfalls

  • •Not responding to submissions
  • •Building everything users request (stay strategic)
  • •Letting the board become a complaint forum
  • •Not closing the loop when you ship requested features

Source: Canny, Linear. Feature request participants have 30-40% lower churn than non-participants.

Suggested ICE scores

5Impact
7Confidence
9Ease
retentionfeature-requestsfeedbackcommunityengagement

Ready to run this experiment?

Sign up free to use this playbook with step-by-step guidance and track your results.

More retention playbooks

Users sign up and never come back

Send a 7-day onboarding email sequence

RetentionBeginner

Users try once and never come back

Add a streak counter

RetentionIntermediate

Users have no accountability to keep using

Add friend challenges

RetentionIntermediate

Explore other categories

Acquisition

Get more visitors and sign-ups

Activation

Turn sign-ups into active users

Monetization

Increase revenue per user

Referral

Turn users into advocates

Run experiments like a pro

Get experiment suggestions, track results, and learn what works.

GoldenGecko

Always know what to test next. Proven playbooks, matched to your goals.

Product

  • Features
  • Pricing
  • Playbooks

Resources

  • Guides
  • Common Problems
  • Glossary
  • Comparisons
  • Documentation

Geckoverse

  • Silver Gecko - SEO
  • Local Gecko - local SEO

Company

  • About
  • Privacy
  • Terms

© 2026 GoldenGecko. All rights reserved.

[email protected]