Notes on answering every request.
How we run a feedback board, close the loop with the people who asked, and decide what to build next. Written by the people building HeedPost.
Start here · Nº 01 · Product practice · 2 min
A public board is a promise, not an inbox.
How to keep feedback useful for your team without leaving customers wondering whether anyone is listening.
Read the noteOne email per person, per release
Why we send each person one email about a release, however many of their requests it answers.
Changelog · Oct 19, 2026New, Improved, Fixed, and when you need more
A small set of labels makes a changelog skimmable. A big set makes it a filing system nobody uses.
For founders · Oct 19, 2026Why we price per workspace, not per seat
Seat pricing makes teams decide who's allowed to hear from customers. We didn't want anyone making that choice.
-
ChangelogNº 38 · Oct 19, 2026
One email per person, per release
Why we send each person one email about a release, however many of their requests it answers.
-
ChangelogNº 37 · Oct 19, 2026
New, Improved, Fixed, and when you need more
A small set of labels makes a changelog skimmable. A big set makes it a filing system nobody uses.
-
For foundersNº 36 · Oct 19, 2026
Why we price per workspace, not per seat
Seat pricing makes teams decide who's allowed to hear from customers. We didn't want anyone making that choice.
-
Building on itNº 35 · Oct 18, 2026
Letting an AI agent work your feedback board
Agents can file, triage and ship from the tools your team already uses. A few principles let them in safely.
-
LanguagesNº 34 · Oct 18, 2026
Plurals, dates and digits: the small things that sound native
A translation can have every word right and still read as foreign. Usually it's the counting.
-
LanguagesNº 33 · Oct 17, 2026
Translate what it means, not what it says
Product words are shorthand. Translating them word for word produces sentences that are correct and wrong at once.
-
LanguagesNº 32 · Oct 17, 2026
Right to left is not a mirror image
What we learned making HeedPost read properly in Arabic, Hebrew and Urdu, and what doesn't flip.
-
Product practiceNº 31 · Oct 16, 2026
A calm weekly rhythm for a busy board
Triage new posts, resolve duplicates, and publish only the updates that matter, in about an hour a week.
-
LanguagesNº 30 · Oct 16, 2026
A board in 21 languages: what changes
When customers can read and write in their own language, more of them speak up. This is what changes for your team.
-
Product practiceNº 29 · Oct 15, 2026
Keeping a board alive after launch week
Launch week brings a rush of posts. What happens in the following month decides whether customers keep coming back.
-
Building on itNº 28 · Oct 14, 2026
Moving feedback tools without emailing anyone
How to switch tools without losing votes, threads or your customers' trust, and without a single surprise email.
-
For foundersNº 27 · Oct 12, 2026
A customer advisory board on a budget
You don't need a conference room and catering. A private board and a monthly hour will do most of the work.
-
Building on itNº 26 · Oct 10, 2026
Your roadmap, on your own website
Draw what's planned in your own style, from live data, with a read-only key and an afternoon of work.
-
Building on itNº 25 · Oct 9, 2026
Webhooks you can trust, in plain words
Signatures, retries and duplicates explained for the person who has to write the receiving end.
-
RoadmapsNº 24 · Oct 7, 2026
Taking something off the roadmap
Plans change. How to remove a planned item without people feeling the promise was broken.
-
ResearchNº 23 · Oct 5, 2026
What the people who never vote are telling you
Most visitors to a feedback board read and leave. Their behaviour is quiet feedback worth reading.
-
Product practiceNº 22 · Oct 3, 2026
The internal note: where your team's context lives
The most useful thing on a feedback post is often the part customers never see.
-
RoadmapsNº 21 · Oct 1, 2026
How much should be in progress?
A short "In progress" column ships more than a long one. A little queueing theory explains why.
-
Product practiceNº 20 · Sep 30, 2026
Weighing requests by revenue without losing the plot
Money behind a request is a real signal. Use it well and you won't turn into a custom shop for your biggest customer.
-
FeedbackNº 19 · Sep 28, 2026
How to say no on a public board
A clear, kind no is better for the customer than a maybe that lasts a year, and it takes two minutes to write.
-
ResearchNº 18 · Sep 26, 2026
Five questions before you build the most-voted request
A short conversation with a few voters can save a quarter of building the wrong version.
-
RoadmapsNº 17 · Sep 24, 2026
Should a public roadmap have dates?
Mostly no. A date helps in a few cases, and you can share timing without making promises you'll break.
-
Product practiceNº 16 · Sep 22, 2026
RICE, ICE and the limits of a score
Scoring frameworks are good at making you ask the right questions and bad at answering them for you.
-
ChangelogNº 15 · Sep 21, 2026
Release notes people actually read
Lead with what people can do now, write for the person who asked, and stop before it becomes a newsletter.
-
FeedbackNº 14 · Sep 19, 2026
Bugs and ideas don't belong on the same board
They need different questions, different people and different promises. Give each its own board.
-
ResearchNº 13 · Sep 17, 2026
The request behind the request
People ask for a feature when what they want is a job done. Reading for the job changes what you build.
-
RoadmapsNº 12 · Sep 15, 2026
Now, next, later: a roadmap people can read
Three columns that tell customers what's happening without promising dates you'll miss.
-
FeedbackNº 11 · Sep 13, 2026
What to do about the loudest customer
Every board has one. How to give them a fair hearing without letting them steer the product.
-
ResearchNº 10 · Sep 11, 2026
The Kano model, for teams without time for it
A forty-year-old idea about which features make people happy, and how to use it in an afternoon.
-
ChangelogNº 09 · Sep 10, 2026
Closing the loop without another generic email
Connect the shipped work to the people who asked, then tell each of them what changed for them.
-
RoadmapsNº 08 · Sep 8, 2026
A public roadmap is a conversation, not a contract.
Use visible states to show direction without turning every request into a deadline.
-
FeedbackNº 07 · Sep 6, 2026
The worst field on your feedback form
"How important is this to you?" feels useful and tells you almost nothing. There are better questions to ask.
-
Product practiceNº 06 · Sep 4, 2026
When two requests are actually the same request
Merge the overlap without flattening the different reasons customers asked.
-
Product practiceNº 05 · Sep 2, 2026
Votes are a signal, not a plan.
The most-voted list is a great place to start a decision and a bad place to finish one.
-
FeedbackNº 04 · Sep 1, 2026
What a useful status tells a customer
Statuses should explain what changed for the person who asked, not merely label your internal workflow.
-
ResearchNº 03 · Aug 30, 2026
Votes tell you what is wanted. Events tell you why now.
Read the activity around a request before turning feedback into a score.
-
FeedbackNº 02 · Aug 28, 2026
Three questions a request form should ask, and one it shouldn't.
A good form asks for the context you'd otherwise chase by email, and nothing that makes people give up halfway.
-
Product practiceNº 01 · Aug 26, 2026
A public board is a promise, not an inbox.
How to keep feedback useful for your team without leaving customers wondering whether anyone is listening.
Want us to write about something? Tell us, and a person reads it. Or follow the notes by RSS.