Add persona section to Surveys team page #14213
Conversation
Defines primary personas (product engineer, product manager, growth engineer), secondary support (UX researcher), and explicitly non-target users (marketing, support/CS). Each persona includes JTBD and reasoning for prioritization level. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| - Somewhat support (should work, churn acceptable short-term): | ||
|
|
||
| - **UX researcher** |
There was a problem hiding this comment.
maybe not UX research specifically... but my gut says we should maybe prioritize these "non-tech roles" a bit higher
TL;DR i think my feedback is our product should be accessible to anyone at a given company:
- the UX should be sexy, buttery smooth, self-explanatory
- if we water down any controls for the sake of better UX, everything should still be accessible to "power users" - e.g. technical roles
- i think we can do this without sacrificing our attention to core persona. we don't necessarily need to build more features specifically for marketing/UXR/support, but a bit of polish on the UX unlocks a lot of potential users, i think
- i'm realizing this might all sound like word salad and maybe not even super relevant to this particular doc, but pls give me your thoughts haha
looking back to some of the highest value user interviewers i've done (for product tours and surveys, i think ICP overlaps) and support tickets, the users are generally somewhat technical, but not always developers - and i think there's a bit of "survivorship bias" in play there too (in the current state, a user has to be pretty technical to use our product)
examples:
- support ticket; user building surveys; asked dev team to update sdk version: https://posthoghelp.zendesk.com/agent/tickets/44614
- user interview (we've had several with this person) - not a developer, i think, but very technical: https://app.buildbetter.app/calls/534478
- user interview (product tours); chat was with one technical and one non-technical user, the non-technical one seemed to be more interested in creating the surveys/tours, technical one was just asking implementation questions: https://app.buildbetter.app/calls/544295
maybe this goes against the posthog ICP as a whole(?) but i think as a company grows, the dev teams end up with a task "implement posthog", and it's non-developers actually using the platform from there
the trend i think i'm seeing is small companies / startups => developer / product eng / solo founder / etc is creating surveys (ex1, ex2). then as company grows => it's someone else entirely (examples above)
| - JTBD: Collect feedback at scale for lightweight/high-frequency product triage | ||
| - Why somewhat: Will churn to specialist tools for complex and rigorous research. Acceptable while we build intelligence layer. | ||
|
|
||
| - Not building for (actively okay with churn): |
There was a problem hiding this comment.
when we say "actively okay with churn" here, can you clarify?
is this churn in the sense that a marketing team or support team signed up for posthog on their own, decided it was too complex or lacked features, and then churned? or like an existing company uses posthog, support/marketing tries to adopt surveys, they decide they do not like it?
Defines primary personas (product engineer, product manager, growth engineer), secondary support (UX researcher), and explicitly non-target users (marketing, support/CS). Each persona includes JTBD and reasoning for prioritization level.
🤖 Generated with Claude Code
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist