Private previewWorkspaces are by invitation

HeedPost

01Collect

Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.

02Understand

Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.

03Ship and tell

Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.

04Run it

Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.

05Connect

Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Notes/Research

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.

Nº 10 · HeedPost team · Sep 11, 2026 · 2 min read

HEEDPOST NOTESNº 10

In 1984 Noriaki Kano, a professor in Tokyo, published a way of thinking about product features that's still useful today. His insight was simple: not every feature affects satisfaction the same way. Some only matter when they're missing. Some make people happier the more you have of them. Some delight people precisely because nobody expected them.

You don't need the full survey method to use the idea. You need the three categories and an honest afternoon.

The three that matter most

Must-haves. Nobody thanks you for these, and everybody leaves without them. Signing in that works. Data that doesn't vanish. An export when you need to leave. If a must-have is broken, nothing else you ship will be noticed.

Performance features. More is better, in a straight line. Faster search, more integrations, longer history. Customers can tell you about these directly, and they show up on feedback boards constantly.

Delighters. Things people didn't know to ask for and love when they find them. They rarely appear as feature requests, because nobody requests what they can't imagine.

Kano also named features people don't care about either way, and features some people actively dislike. Both are worth spotting before you build them.

Read your board through the three

Go through the top thirty posts and put each in a bucket. You'll probably find:

  • A handful of must-haves in disguise. "Export to CSV" often isn't a nice-to-have. It's someone telling you they can't do their job. These deserve to jump the queue.
  • A long list of performance asks. This is where votes are most useful, because more people wanting more of something is exactly what they measure.
  • Very few delighters. That's normal. Your board won't tell you about them. Watching people use the product will.

Things drift down

Kano noticed something else: features slide over time. Today's delighter is next year's performance feature and the year after's must-have. Dark mode was a delight once. Now people file it as a bug when it's missing.

So revisit the buckets once or twice a year. A request you parked as "nice to have" may have quietly become something people expect.

A shortcut for the survey

The full method asks two questions about each feature: how would you feel if it were there, and how would you feel if it weren't. You can borrow that on a smaller scale. When a request is near the top of your list, ask a few of the people who voted both questions in a short message. The pattern of answers tells you which bucket it's really in.

Kano isn't science, but it starts a better conversation than "how much do you want this?", and that's usually enough.

Start hearing everyone.

Free for your first two boards, with no card.