Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surveys Megaissue #16374

Closed
19 of 37 tasks
liyiy opened this issue Jul 4, 2023 · 5 comments
Closed
19 of 37 tasks

Surveys Megaissue #16374

liyiy opened this issue Jul 4, 2023 · 5 comments

Comments

@liyiy
Copy link
Contributor

liyiy commented Jul 4, 2023

High priority (ordered by priority)

  • Visualise quantitative data
  • Radio button / multiple choice question types
  • Exclude users from targeting who have already seen a survey
  • 'Thank you' toast after responding
  • Calculate Net Promoter Score
  • Tests on surveys app repo
  • Multiple questions
  • Polish UI based on Cory's wireframes: Follow up surveys UX #16018
  • Surveys UI UX issues #17038
  • Templates
  • Surveys as a new product on the website (add to the onboarding flow)
  • Surveys in app onboarding flow

Quick wins do complete alongside sprint goals

  • Restarting a survey
  • Usability: Make it clearer you can’t add a behavioural cohort, update error message to say surveys, not flags
  • Usability: Make it clearer how targeting by flag works
  • Usability: Make it clear that URL filter means contains
  • Usability: Make selector flag clearer, on actions we have more text and a link to the docs
  • Product intro for surveys 
(done, but we should get art from Lottie and link to the docs)
  • Help users debug why their survey is not showing, e.g. detect site app setup, popup shown etc
  • Remove “powered by PostHog” for paying users

Nice-to-have's, side quests for sprints

  • Exporting data
  • Slack notifications
  • Hit web hook after successfully completing survey (in this case to incentivise users for completing)
  • Support regex for page url contains
  • Bug report question type: Includes session ID, connection to screen recording they also have in PostHog, sends Slack notification
  • Surveys for mobile
  • Cory + Eli site app styling 2.0 + Define design for survey popup in a global place
  • qualitative data exposure on ff/experiments/feature success -> make this part of feature success

Useful but complex, work on other high-priority issues first

  • branching logic, e.g. depending on rating scale, show different set up follow up questions
  • behaviour-based targeting

Won't do for now

  • Schedule for surveys, e.g. sending it every 6 months
”set it and forget it”
  • Position survey in different spots
  • Product tours, highlight what’s new survey type
  • Handle popups from multiple vendors, e.g. what happens if you have PostHog and Intercom set up?
  • Multi-language support
  • Survey hierarchy, e.g. if the user is eligible for multiple, which one should he get
  • Full-screen surveys

Link to original RFC: https://github.com/PostHog/product-internal/pull/483
Link to original issue: #15375

PROJECT BOARD LINK: https://github.com/orgs/PostHog/projects/87

@annikaschmid
Copy link

Feedback from @pauldambra:

I stopped a survey in the EU but I expected to be able to start it again 🙈
Would be great to be able to duplicate it or restart it 📈

the URL was pre-filled when I made a new version of it.
Useful in this instance but probably incorrect

(and then the tiniest of nits - when I clicked save both the save and the cancel buttons showed a loading spinner - very nitty but my brain had already shifted into feedback mode so 🤷)

Original convo: https://posthog.slack.com/archives/C034XD440RK/p1688721246388589

@annikaschmid
Copy link

@liyiy A couple of weeks ago, I made a list with UX improvements from my own testing. Could you go over it and tick off what is done / we won't do / what is on your list, so that we can close the issue? Thanks! #16018

@raquelmsmith
Copy link
Member

A user shared in the community slack:

Ok! I think event based targeting is pretty fundamental for surveys. For example, we want to be able to target people who have searched three times on our website for something. So being able to say, if someone has done this thing x number of times, show a survey. Common use case--if a customer is doing something a bunch of times, you might want to know why.

@joethreepwood
Copy link
Contributor

I'm keeping an eye (and commenting here to get further updates) but would also be good to align some content with this as we go so we can do some more marketing support. Would love to get some sneak peeks, changelogs, twitter threads and tutorials out as this feature firms up. I think it's a really, really strong differentiator and want to support it as much as I can.

@annikaschmid
Copy link

Link to Cory's wireframes: #16018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants