When two requests are actually the same request
Merge the overlap without flattening the different reasons customers asked.
Nº 06 · HeedPost team · Sep 4, 2026 · 2 min read
Every busy board fills up with near-copies. "Export to Excel." "CSV download please." "Can I get my data out?" "Spreadsheet export for finance." Four posts, four sets of votes, and a top-ten list that undercounts the one thing your customers want most.
Merging fixes the count. Done carelessly, it also throws away the most useful part: the four different reasons people asked.
Same request, or same words?
Before merging, ask one question: would a single change satisfy everyone on both posts? If yes, they're the same request. If shipping one would leave the other group still waiting, they're different requests that happen to share words.
"Export to CSV" and "Export to Excel" are usually the same request. People want their data in a spreadsheet. "Export to CSV" and "Sync to our data warehouse every night" share a word and almost nothing else. One is a button. The other is an integration with a schedule, credentials and failure handling. Merge those and you'll ship the button and wonder why half the voters are still unhappy.
Keep the reasons when you merge
The duplicate post usually has its own comments, written in its own words. That's gold. Someone explains they need the export for an audit. Someone else needs it because a manager won't log in. When you merge, those reasons should travel with the votes into the surviving post, so whoever builds it reads the whole story.
A good habit: after merging, add one comment to the surviving post summarising the reasons from the duplicates. "Merged in four requests. The main reasons: quarterly reports for finance, audits, and sharing with people who don't have accounts." Whoever picks this up later will thank you.
Merge into the clearest post, not the oldest
Pick the post whose title a newcomer would understand. Sometimes that's the newest one. You can always edit the title too. The goal is that the next person searching finds it and votes instead of writing a fifth copy.
Count people once
A person who voted on both posts wants the thing once. If your merge adds their votes together, your count is inflated by exactly the people who cared enough to vote twice. Make sure overlapping voters are counted once.
And tell them
Everyone who followed the duplicate should hear where their request went. Not a big announcement, just enough that they don't think it disappeared. When the surviving post moves, they hear about it like everyone else.
Merging is maintenance, and it's worth doing a little every week rather than a big clean-up twice a year. A board with fewer, truer posts is easier for customers to use and easier for you to read.