From aefe41b16e44a8b22f3f2095fdd17b2566029a50 Mon Sep 17 00:00:00 2001 From: Lucas Faria Date: Mon, 6 Apr 2026 11:51:48 -0300 Subject: [PATCH 1/2] Update surveys team Q2 2026 goals --- contents/teams/surveys/objectives.mdx | 53 +++++++++++---------------- 1 file changed, 21 insertions(+), 32 deletions(-) diff --git a/contents/teams/surveys/objectives.mdx b/contents/teams/surveys/objectives.mdx index be792240c5df..1eab89bf19d2 100644 --- a/contents/teams/surveys/objectives.mdx +++ b/contents/teams/surveys/objectives.mdx @@ -1,43 +1,32 @@ -### ðŸŽĻ Goal 1: Survey Platform UX Simplification +### 🔍 Goal 1: Surveys – Research & Pricing Exploration -> Why: The current survey creation flow is complex. We need to simplify it by organizing surveys by purpose and use case. +> Why: We're in exploration mode on surveys. We need to determine the product's future direction by understanding willingness to pay and testing a simpler pricing model. -> Who: - -Restructure the surveys experience around specific survey types and use cases: -- Create dedicated pages for different survey types (hosted surveys, metric-based surveys like NPS/CSAT, small in-app feedback collection) -- Figure out our current North Star metrics (Usage + NDR) -- Make it intuitive for users to pick the right survey type for their needs - -### ðŸŽŊ Goal 2: Product Tours on Public Beta - -> Why: Product Tours is a highly requested feature that complements our surveys and feedback collection capabilities. +> Who: , -> Who: +Talk to customers and explore a new pricing model: +- Identify ~10 customers who have consistently created surveys or received responses recently +- Conduct 1:1 calls throughout the quarter, framed around rethinking the future of the product +- Explore a flat monthly fee for a set number of responses, with a reduced free tier +- Explore including branding removal in the paid tier +- Use research outcomes to decide whether to invest further, change pricing, or sunset the product -Ship a limited feature set (Tours, Announcements, Banners) for Product Tours to Public Beta: -- Deliver core Product Tours functionality -- Enabled for everyone (self-serve) -- Come up with a pricing plan +### ðŸŠķ Goal 2: Surveys MCP & Skills -### 🌎 Goal 3: Collective Qualitative Feedback on Autopilot (Surveys Everywhere v2) +> Why: Make surveys usable from agentic workflows by exposing it through MCP and skills. -> Why: Users shouldn't have to think about "creating a survey" — they should just tell us how they want to collect feedback. - -> Who: , , and +> Who: -Evolve the surveys paradigm from "create a survey" to "how do you want to collect feedback": -- Enable feedback collection from feature flags, experiments, and errors -- Make qualitative feedback collection feel automatic and contextual +Ship surveys MCP tools and skills so users can create and manage surveys from AI clients. -### ðŸĪ– Goal 4: PostHog AI User Interviews +### 📊 Goal 3: MCP Analytics -> Why: AI-powered user interviews could be a game-changer for qualitative research at scale. +> Why: As MCP usage grows, we want to capture the *why* behind MCP calls — not just cost/latency — and whether users accomplished their goal. -> Who: , , and +> Who: -Explore and validate AI-powered user interviews: -- Talk to customers to understand if this is a real problem worth solving -- Write an RFC on what we're trying to solve -- Understand how to integrate with PostHog's AI Platform -- Benchmark against competitors +Build bare-bones infrastructure for MCP analytics: +- Ship an initial version in the PostHog MCP server +- Capture user context around MCP calls (intent, outcome), not just telemetry +- Work closely with the analytics and growth teams +- Potential naming: "MCP Insights" or "MCP Feedback" From 0755660df3b1da772ae086d831797dc6833bfa7b Mon Sep 17 00:00:00 2001 From: Lucas Faria Date: Mon, 6 Apr 2026 22:37:11 -0300 Subject: [PATCH 2/2] Address PR review feedback --- contents/teams/surveys/objectives.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/contents/teams/surveys/objectives.mdx b/contents/teams/surveys/objectives.mdx index 1eab89bf19d2..8dc5864aa83a 100644 --- a/contents/teams/surveys/objectives.mdx +++ b/contents/teams/surveys/objectives.mdx @@ -1,27 +1,27 @@ -### 🔍 Goal 1: Surveys – Research & Pricing Exploration +### 🔍 Goal 1: Surveys research & pricing exploration -> Why: We're in exploration mode on surveys. We need to determine the product's future direction by understanding willingness to pay and testing a simpler pricing model. +> Why: We're in exploration mode on Surveys. We need to determine the product's future direction by understanding willingness to pay and testing a simpler pricing model. > Who: , Talk to customers and explore a new pricing model: -- Identify ~10 customers who have consistently created surveys or received responses recently +- Speak with ~10 customers who have consistently created surveys or received responses recently - Conduct 1:1 calls throughout the quarter, framed around rethinking the future of the product - Explore a flat monthly fee for a set number of responses, with a reduced free tier - Explore including branding removal in the paid tier - Use research outcomes to decide whether to invest further, change pricing, or sunset the product -### ðŸŠķ Goal 2: Surveys MCP & Skills +### ðŸŠķ Goal 2: Surveys MCP & skills -> Why: Make surveys usable from agentic workflows by exposing it through MCP and skills. +> Why: Make Surveys usable from agentic Workflows by exposing it through MCP and skills. > Who: -Ship surveys MCP tools and skills so users can create and manage surveys from AI clients. +Ship Surveys MCP tools and skills so users can create and manage surveys from AI clients. Add it as an Early Access feature so users can opt in and signal interest. -### 📊 Goal 3: MCP Analytics +### 📊 Goal 3: MCP analytics -> Why: As MCP usage grows, we want to capture the *why* behind MCP calls — not just cost/latency — and whether users accomplished their goal. +> Why: As MCP usage grows, we want to capture the *why* behind MCP calls – not just cost/latency – and whether users accomplished their goal. > Who: