User interviews product

[Twixes]

Is your feature request related to a problem?

Gathering feedback is a crucial part of building a product and it needs a system. PostHog can step in here with its breadth with a solution that we'd also definitely dogfood.

Describe the solution you'd like

Here's a concept:
PostHog should have a User Interviews tab. It should contain a list Interview Sessions, an Interview Session being a list of multiple Interviews, with the Interview model having elements:

• date (by default today)
• interviewer (PostHog user, by default the author)
• person (PostHog person, searchable by email)
• segment (options: Potential, Casual, Core, Power, Churned – @paolodamico more thoughts appreciated)
• company (preferably a PostHog group when we add the group feature, but can be just the name or URL until then, or empty)
• points and takeaways (just a Markdown-formatted string would probably be best)
• actionables (a list of GitHub issues/Jira tickets/otherwise links to an issue tracker)

Interviews relevant to the PostHog person should also be listed on their person page.
The outline above is basically what we do now in Google Docs, but systemized better, which'd already make it useful (and rather simple to implement). Additionally we should consider use cases for a wider audience, and related to gathering feedback beyond just interviews.

Describe alternatives you've considered

Google Docs at scale. 🙈

Thank you for your feature request – we love each and every one!

[jamesefhawkins]

segment (options: Potential, Casual, Core, Power, Churned – @paolodamico more thoughts appreciated)

This would be cool to convert into a cohort automatically.

[jamesefhawkins]

These are mainly ideas for how to build something that takes advantage of us as a platform...

Filtering

By the user

Other random idea, and again probably beyond the MVP: we could enable filtering of these interviews by the same things you can filter our analytics by.

• "I wonder how the feedback looks if I should considered users from Twitter", for example
• I just want to see feedback from users that have used X feature (look at just the feedback from those users in a particular cohort)

## Tags

Customisable tags so you can track themes emerging over time.

Again definitely not what should go in first version.

I could even see engineers then doing something like they do with github issues. ie A PR could reference a hashtag_number, which would then get connected up to all the feedback.

Actionables

We often ourselves could do with a link to our CRM as we solve user feedback. As for example, if we then had the tags<>github thing above, you could then ping your sales team "hey these users who wanted X, it's now live, go speak to them"

Also way beyond MVP

[kpthatsme]

I like this idea. I also think there's some additional functionality that can add a lot of value and make this very interesting.

A lot of teams rely on PMF surveys, such as NPS or the more recent "How would you feel if you could no longer use this product?" type of survey in product.

Given that teams are already loading our JS on their site, I think this could be an incremental feature that could add a lot of value. I think such a feature could be a great way to source feedback automatically and start populating some research for our users.

I imagine a workflow where they can go in and view all survey responses and proactively reach out to users that have left interesting feedback.

[EDsCODE]

+10000

[posthog-bot]

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

[posthog-bot]

This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.