Every team leaves some posts open forever because closing them feels unkind. Customers can tell. A request that's sat in "Under review" for fourteen months isn't being reviewed, and everyone knows it. That quiet maybe is worse than a no. It keeps people waiting, and it makes your other statuses less believable.
A good no is short, honest and useful. It takes two minutes to write.
Say it plainly
Start with the decision. "We're not going to build this." Not "at this time we've decided to deprioritise", not "this isn't on our immediate roadmap". People read hedged language as either a secret yes or a brush-off, and neither helps them.
Give the real reason
People accept almost any honest reason. The common ones:
- It doesn't fit where the product is going. "We're keeping HeedPost focused on feedback, so we won't be adding time tracking."
- Something else covers it. "The new API lets you do this with a short script. Here's the guide."
- The cost is out of proportion. "This would mean rebuilding how we store data, which we can't justify for this alone."
- Not enough people need it. Say so, kindly. It's often the truth.
What they won't accept is no reason at all.
Offer what you can
A no often has a partial yes inside it. A workaround, an integration, a related feature you are building, a different tool that does it well. Pointing someone to a competitor for one narrow need is not a failure. It's the kind of honesty people remember.
Leave the door open, honestly
If things could change, say what would change them. "If more teams on larger plans need this, we'll look again." Then mean it. If you say "we'll revisit", put a note somewhere you'll actually see.
Lock it if it keeps going
Sometimes a closed post keeps attracting comments arguing the decision. After a while that helps no one. Lock comments with a short note saying why, so the thread stays readable and the decision stands.
Saying no well builds trust
Customers learn from your no's how much your yeses mean. A board where everything stays open forever is a board where "Planned" might mean anything. A board that closes things with clear reasons is a board where "Planned" means planned.