How Northwind closed the feedback loop

Northwind ships a project-management tool to 40,000 teams. Eighteen months ago their changelog was a Notion page nobody updated. Today it's the first input to their planning cycle. Here's the wiring.

Step one: stop writing, start approving

The Notion page died the way they all do — the engineer who cared left, and the habit left with them. Northwind's fix was removing the writing step entirely: Signal drafts from merged PRs in their monorepo, path-mapped so each product's changes land in the right feed. A product manager spends five minutes on Friday approving the week's draft. That's the entire process.

Step two: put reactions on everything

Every published update carries reactions and comments. The numbers surprised them immediately: their most-thumbed release of the quarter was a bug fix for a timezone edge case — something the team considered too small to mention. The audience votes on what matters, and it doesn't vote the way the roadmap assumed.

Step three: route comments to the tracker

The load-bearing feature is the smallest one. When a customer comments "any chance exports could include custom fields?", whoever's triaging clicks once and it becomes a Linear issue — with the customer's email, plan, and the release they were reading attached as context.

We used to run quarterly surveys to learn what customers wanted. Now the changelog tells us weekly, and the sample is people engaged enough to read release notes. Dana Whitfield, Head of Product at Northwind

The loop, closed

Watch what happens across a full cycle: a PR merges → Signal announces it → customers react and ask → requests land in Linear with receipts → the next cycle ships the winners → and the changelog announces those too, tagged with the names of the people who asked. Northwind now @-mentions requesters in release comments — "you asked, it's live." Their reply rate on those mentions is comfortably the best retention email they never had to write.

What to copy

• Make approval, not authorship, the human step.
• Publish small fixes — the audience rewards them more than you expect.
• Give every comment a one-click path into your tracker.
• Tell requesters when their thing ships. It's the whole loop, closed in one sentence.