Return to Answer

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this is an effortless question for a user to answer and might do a better job of hooking the user into the feedback flow. If the user encountered a bug, had a difficult time, or found the experience particularly painless, then they've already decided internally that they have something to communicate. The question, "have something to tell us?" has already been answered by them before they even read it and entering the feedback flow is as simple as clicking a button which reflects what they're already thinking. "Provide feedback" requires the user to stop and think: "is this going to be one of those annoying feedback surveys that websites always have and is what I want to communicate worth risking that it might be?".

A better answer would cite A/B testing results on the verbage that produces the most feedback. This answer is just my opinion

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this is an effortless question for a user to answer and might do a better job of hooking the user into the feedback flow. If the user encountered a bug, had a difficult time, or found the experience particularly painless, then they've already decided internally that they have something to communicate. The question, "have something to tell us?" has already been answered by them before they even read it and entering the feedback flow is as simple as clicking a button which reflects what they're already thinking. "Provide feedback" requires the user to stop and think: "is this going to be one of those annoying feedback surveys that websites always have and is what I want to communicate worth risking that it might be?".

A better answer would cite A/B testing results on the wording that produces the most feedback. This answer is just my opinion

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this an easy question for a user to answer and might do a better job of hooking the user into the feedback flow. By the time the user has finished reading "have something to tell us?" they've already answered the question automatically and only need the minimal effort of clicking the button to communicate that initial answer. "Provide feedback" requires more effort for the user to answer, and no one likes to deliberate more than they already have to.

A better answer would cite A/B testing results on the verbage that produces the most feedback. This answer is just my opinion

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this is an effortless question for a user to answer and might do a better job of hooking the user into the feedback flow. If the user encountered a bug, had a difficult time, or found the experience particularly painless, then they've already decided internally that they have something to communicate. The question, "have something to tell us?" has already been answered by them before they even read it and entering the feedback flow is as simple as clicking a button which reflects what they're already thinking. "Provide feedback" requires the user to stop and think: "is this going to be one of those annoying feedback surveys that websites always have and is what I want to communicate worth risking that it might be?".

A better answer would cite A/B testing results on the verbage that produces the most feedback. This answer is just my opinion

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this an easy question for a user to answer and might do a better job of hooking the user into the feedback flow. By the time the user has finished reading "have something to tell us?" they've already answered the question automatically and only need the minimal effort of clicking the button to communicate that initial answer. "Provide feedback" requires more effort for the user to answer, and no one likes to deliberate more than they already have to.

A better answer would cite user studies on the verbage that produces the most feedback. This answer is just my opinion

Of the options you provided, "provide feedback" seems like the only appropriate one since the other two are too specific and don't seem like opportunities to provide positive feedback.

I would phrase it as "Have something to tell us?". This is generic and would be recognized as an opportunity to ask about a problem, complain about the experience, or praise the experience. Additionally, answering this an easy question for a user to answer and might do a better job of hooking the user into the feedback flow. By the time the user has finished reading "have something to tell us?" they've already answered the question automatically and only need the minimal effort of clicking the button to communicate that initial answer. "Provide feedback" requires more effort for the user to answer, and no one likes to deliberate more than they already have to.

A better answer would cite A/B testing results on the verbage that produces the most feedback. This answer is just my opinion