Use este prompt de IA para transformar resultados brutos de survey em um resumo executivo
Why this prompt matters
Survey data often dies in dashboards because teams summarize averages and miss the story hiding in comments, segments, and contradictions. A good analysis Prompt turns raw feedback into decisions, which means fewer wasted roadmap debates and less risk of leadership acting on the loudest anecdote instead of the strongest pattern.
What we use it for
You have a product review meeting tomorrow and 1,200 customer survey responses sitting in a spreadsheet. Leadership does not want a wall of charts. They want to know what customers are actually unhappy about, whether premium users feel differently from free users, and which findings should change the roadmap this quarter.
Prompt
Role: Act as a senior research analyst and executive communications lead who turns raw survey results into decision-ready insights. Context: I have survey data from customers, employees, event attendees, or product users. The raw results include a mix of quantitative scores, multiple-choice answers, open-text comments, and possibly demographic or segment information. I do not want a generic summary. I need a brief that shows what matters, where the signal is strong, where the contradictions are, and what leaders should do next. Task: Analyze the survey inputs I provide. Identify the most important quantitative patterns, the strongest qualitative themes, any segment differences, and the top contradictions or risks. Translate the findings into a concise executive brief with specific recommendations. If the sample size, question design, or data quality creates limits, explain those limits clearly instead of overclaiming. Constraints: - Do not repeat every survey result. Prioritize what changes a decision. - Separate strong signals from weak or noisy signals. - Quote short representative comments only when they add clarity. - Flag contradictions between scores and comments. - If sentiment differs by segment, role, geography, or product tier, call that out explicitly. - Avoid vague phrases like “overall positive” unless you explain what that actually means. - Preserve important business and technical terms in English when appropriate, including NPS, churn, retention, ROI, KPI, API, and SLA. - If data is missing, state what assumption you made. Output Format: 1. Executive summary in 5 bullet points 2. Top quantitative findings 3. Top qualitative themes 4. Important segment differences 5. Contradictions, risks, or blind spots 6. Recommended actions for the next 30 days 7. One-paragraph version a VP can paste into an update email Inputs: - Survey goal: [WHAT YOU WERE TRYING TO LEARN] - Audience: [WHO RESPONDED] - Sample size and response rate: [NUMBERS IF AVAILABLE] - Quantitative results: [PASTE TABLES, SCORES, OR STATS] - Open-text comments: [PASTE COMMENTS] - Segments: [OPTIONAL BREAKDOWNS SUCH AS ROLE, REGION, TIER, OR TENURE] - Business context: [WHAT DECISION THIS WILL INFORM]
Result
1. Executive summary - Satisfaction is stable at the headline level, but the underlying story is a split between happy power users and frustrated new customers. - The strongest quantitative risk is onboarding: respondents in their first 30 days scored setup 22 points lower than users with more than six months of tenure. - Premium customers value reporting depth and support responsiveness, while free-tier respondents are far more sensitive to speed, simplicity, and pricing clarity. - Open-text comments show a repeated contradiction: users like the product once configured, but many describe the first-week experience as confusing, slow, or dependent on documentation they did not know existed. - The next 30 days should focus on onboarding friction, feature discoverability, and segmentation of support content rather than shipping another advanced analytics feature.
2. Top quantitative findings Overall satisfaction averaged 7.8 out of 10 across all respondents, which looks healthy until segmented. Users with more than six months of product usage averaged 8.4, while new users averaged 6.2. NPS among enterprise admins was +31, but only +4 among self-serve teams. Feature usage data attached to the survey also shows that customers who completed the initial integration flow within the first week were significantly more likely to report high renewal intent.
3. Top qualitative themes The most common positive theme was reliability after setup. Respondents repeatedly described the platform as dependable once workflows were established. The most common negative theme was first-use confusion. Comments frequently mentioned unclear setup steps, too many settings exposed at once, and documentation that answered technical questions without helping users decide what to do first. A smaller but important theme was that support quality is strong when tickets reach a human quickly, but slower first-response times amplify frustration during onboarding.
4. Important segment differences Enterprise admins care most about audit controls, reporting granularity, and support access. Individual contributors care more about ease of use and speed. European respondents mentioned compliance confidence more often than North American respondents, while North American respondents were more likely to ask for faster templates and stronger integrations. New customers were much more likely to leave long explanatory comments, which usually signals unresolved confusion rather than simple dissatisfaction.
5. Contradictions, risks, or blind spots The biggest contradiction is that retention intent is solid among existing customers even though onboarding feedback is weak. That suggests the product becomes sticky after activation, but the company may be losing expansion or early retention before that value is reached. Another risk is sample bias: highly engaged customers were slightly overrepresented, which means passive or churn-prone users may be undercounted.
6. Recommended actions for the next 30 days Redesign the first-run setup sequence, create role-based onboarding checklists, and split support content for admins versus end users. Instrument the first-week activation path more closely and review whether account managers should intervene earlier for larger customers. Delay lower-priority feature work until the onboarding gap narrows.
7. VP-ready email paragraph The survey results show that the product’s core value is not the issue; onboarding is. Experienced customers are broadly satisfied and see the platform as reliable, but new users struggle to reach value quickly, especially during setup and first integration. Premium accounts care most about reporting and support responsiveness, while self-serve teams want simpler early workflows. The clearest short-term opportunity is to improve activation, not add more advanced features. If we reduce first-week friction, the data suggests both retention quality and expansion potential should improve.
Os dados de survey parecem enganosamente simples. As equipes coletam pontuações, comentários e segmentações, e então assumem que a parte difícil está feita. Na realidade, a parte difícil começa depois que as respostas chegam. A maioria das organizações não tem escassez de gráficos. O que lhes falta é uma maneira rápida de separar sinal forte de ruído, explicar contradições e transformar feedback em decisões que os líderes possam realmente colocar em prática.
Este Prompt foi projetado para essa lacuna. Ele enquadra o modelo como analista de pesquisa e líder de comunicação executiva, o que é importante porque a análise de survey não se trata apenas de descrever resultados. Trata-se de decidir quais resultados merecem atenção, quanta confiança depositar neles e que mudança operacional deve seguir.
A estrutura é deliberada. O Role incentiva a IA a pensar além das estatísticas resumidas. O Context diz a ela que espere uma mistura bagunçada de pontuações, comentários em texto livre e desagregações de segmento, em vez de um relatório limpo e pronto para análise. O Task força priorização, síntese e recomendação, em vez de um resumo genérico. Os Constraints tornam o Prompt mais afiado, impedindo que o modelo faça alegações exageradas, aplaine nuances ou esconda incertezas por trás de uma linguagem vaga.
O formato de saída é o que torna isso especialmente útil em locais de trabalho reais. Ele começa com um executive summary, depois passa para descobertas quantitativas, temas qualitativos, diferenças de segmento, contradições, riscos e próximas etapas concretas. Essa sequência reflete como equipes internas de pesquisa fortes se comunicam quando precisam influenciar um roadmap, apoiar uma política, plano de retention ou decisão de experiência do cliente.
O exemplo de saída mostra a diferença entre relatórios e análise. Ele não diz apenas que a satisfação é boa ou ruim. Ele identifica uma lacuna de onboarding, explica como diferentes grupos de usuários vivenciam o produto de forma diferente, destaca uma contradição entre retention e frustração no primeiro uso, e transforma essas descobertas em uma lista de ações de 30 dias. Esse é o tipo de saída que as equipes podem levar para uma revisão de liderança em vez de mais uma dashboard review.
Se você coleta feedback regularmente, mas tem dificuldade para transformá-lo em uma recomendação clara, este é um Prompt que vale a pena salvar. Ele ajuda as equipes a passar de 'aqui estão as respostas' para 'aqui está o que devemos fazer a seguir', e é aí que a análise de survey se torna genuinamente valiosa.