How to Say No to Feature Requests Without Losing Customers

Every product team says no more than they say yes. The hard part isn't the decision — it's communicating it without alienating the user who asked. A public board changes the dynamics of saying no.

Why Saying No Is Hard

When a user emails a feature request and you decline, it feels personal. They asked, you rejected. There's no context for why, no visibility into competing priorities, and no sense that their input mattered.

This is where most teams lose goodwill — not by declining the request, but by making the user feel unheard.

How a Public Board Changes the Conversation

On a public Linear board, saying no happens in context:

• Users see other priorities — The board shows what's in progress and what's planned. A declined request doesn't feel like rejection when users can see what you're building instead.
• Votes validate decisions — If a request has 3 votes and the top item has 200, the prioritization is self-evident.
• Status communicates without confrontation — Moving an issue to "Won't Do" or "Considered" is less personal than a rejection email.
• Other users weigh in — Sometimes the community explains why an alternative approach is better, taking the burden off your team.

Frameworks for Declining Gracefully

When you need to decline a request on your public board:

• Acknowledge the need — "We understand why this would be useful"
• Explain the trade-off — "We're prioritizing X because it affects more users"
• Leave the door open — "We're not building this now, but we're tracking interest"
• Suggest alternatives — "Here's how you can accomplish something similar today"

The Transparency Advantage

Users who can see your full board understand that resources are finite. They know you're not ignoring them — you're making choices. That context turns a rejection into a reasonable decision.

Teams that use public boards report fewer angry responses to declined requests because users have the context they need to understand the why.

Keep the Relationship Intact

A well-run public Linear board turns "no" from a dead end into a conversation. Users stay engaged because they can still vote, comment, and follow the issue. Even declined requests keep users connected to your product.