Product feedback with the problem attached

“Add an export button” is a request. Diaform asks users what they need it for, so you can fix the real problem instead of guessing.

Speech bubble peeled back like a sticker to reveal a broken gear underneath

Why product feedback is hard to use

  • Requests without the problem

    A feature request is the customer’s idea of a fix. It isn’t always the best one.

  • Ratings without context

    A three-star rating tells you something is wrong. It doesn’t say what.

  • The loudest users set the roadmap

    Feedback boards fill up with power users. Quiet users leave without a word.

Behind a feature request

  1. Diaform

    You asked for an export button. What would you do with the export?

  2. Customer

    Just have the data in Excel.

  3. Diaform follows up

    What do you do with it once it’s in Excel?

  4. Filter it by region and send each sales rep their own list.

  5. Diaform follows up

    How often do you do that?

  6. Every Monday. If the app emailed each rep their list, I wouldn’t need the export at all.

Collect product feedback in three steps

  1. 1

    Ask about real use

    Ask what they were trying to do and what got in the way.

  2. 2

    Put it inside your product

    Add the link to your app after a key action, or to your release emails.

  3. 3

    Share it with the team

    Get a Slack message for each reply, or send results to your own tools with webhooks.

What your roadmap gets

  • The problem behind each request

    Build the fix that solves it, which may be smaller than what was asked for.

  • Context for every rating

    Know what a low score was about, in the user’s own words.

  • Feedback from quiet users

    Ask everyone you choose, not only the people who post on your board.

  • Sentiment over time

    See whether people feel better or worse about your product after each release.

Feedback widget vs. feedback conversation

Feedback widget or boardDiaform product feedback
A text box and a vote countA short chat with follow-up questions
Requests with no reason attachedThe task and problem behind each request
Mostly your most active usersAny user you send the link to

Frequently asked questions.

Quick answers before you get started.

Ask users soon after they use a feature, and ask what they were trying to do. Diaform does this as a short chat and follows up when an answer is vague.

Your customers have more to say.

Stop guessing from one-word survey answers. Let Diaform ask the follow-up questions and find out what your customers really think.

Set up your first conversation in minutes.