Sooner or later something on your public roadmap shouldn't be there anymore. You learned the problem was smaller than you thought. A different feature turned out to solve it. Priorities moved. The honest thing is to take it off. The tempting thing is to leave it there and hope nobody asks.
Leaving it costs more. Every week it sits there, more people plan around it.
Decide which kind of change it is
Not every removal is the same, and customers deserve to know which one they're seeing.
- Later, not now. It's still a good idea, just not next. Move it back to review or to a "later" state.
- Solved another way. Something else covers the need. Close it as done, and point to what solves it.
- Not doing it. You've decided against it. Close it with the reason.
Each of those is a different message. "We're not doing this" and "this is coming, just later" mean very different things to someone waiting.
Say it on the post
Move the post with one or two honest sentences. The people following it are owed an explanation, and they'll get one in their inbox.
Moving this back to review. While building the new import, we found it covers most of what people asked for here. We'd like to see what's still missing before planning more.
That message admits a change, gives the reason and invites the conversation. Most people respond well to it.
Don't do it quietly in bulk
Cleaning up the roadmap is healthy, but removing fifteen items at once without notes reads like an organisation in trouble. If you need a big clean-up, write a short changelog entry or a note explaining the change in direction, then move items with a sentence each.
Talk to the people it hurts most
If a large customer was counting on something, don't let them find out from an automated email. Tell them first, directly, and explain what you can offer instead. That conversation is uncomfortable for ten minutes and saves the relationship.
Learn from it
Each removal says something about how things got onto the roadmap. If items regularly come off, maybe "Planned" is being used too early. Tightening what earns a spot on the roadmap is the best way to have fewer things to take off it.