How do you say "no" to feature requests from different cultures?
by•
Handling feature requests from users in Japan and the US taught me that directness is not universal. American users usually appreciate a straight "we are not building this right now." Japanese users often expect a softer rejection that acknowledges the effort behind the request and explains the roadmap politely.
Changing how we frame our "no" has kept our churn rate low in both regions.
If you manage global users, how do you politely decline a feature request without offending them?
14 views
p/jot-2-0
p/tabstack
p/gatrends
p/runevr
p/google-cloud-platform
p/producthunt
p/okapi-2
p/rithub
p/flamigo
p/ski
p/dex-by-exmergo
p/replay-11
p/appxiom
p/verse-engine-by-ctruh
p/codedesign
p/reso
p/many-displays
p/dino-kids
Replies
I'm in Japan, so I see the Japanese side every day. What's worked for me is handling most requests the same day, so a no doesn't come up as often as you'd think. When it does, it's usually because I don't use that feature myself, and I'd rather not build something I can't judge as a user.