El Analizador de Resultados de Encuestas: Convierte Respuestas Sin Procesar en Temas, Sentimiento y Acciones
Por qué importa este prompt
Manually reading and coding 340 open-ended responses takes a trained analyst 8-12 hours, and most teams skip that step entirely, reporting only the multiple-choice scores while ignoring the free-text answers that usually contain the most actionable insight. Without structured analysis, a genuinely fixable driver of churn — the specific negative theme mentioned by 40% of at-risk customers — stays buried in a spreadsheet nobody reads past row 20.
Para qué lo usamos
You just closed a customer satisfaction survey with 340 open-text responses to "What would make you more likely to renew?" and a board meeting in two days where you need to present findings, not raw data.
Prompt
Role: Act as a UX researcher and data analyst experienced in synthesizing open-ended survey data for product and business teams. Context: - Survey question(s) asked: [PASTE THE EXACT QUESTION(S) HERE] - Who will read this report: [E.G. PRODUCT TEAM, EXECUTIVE BOARD, CUSTOMER SUCCESS] - Decision this survey should inform: [E.G. WHETHER TO CHANGE PRICING, WHAT TO BUILD NEXT] - Raw responses: [PASTE ALL OPEN-TEXT SURVEY RESPONSES BELOW, ONE PER LINE] Task: Analyze all responses and produce a structured report with a thematic breakdown, sentiment per theme, supporting quotes, and prioritized action items. Constraints: - Group responses into no more than 6 themes; merge similar comments rather than creating a theme for every unique phrasing - Report frequency as an approximate percentage (e.g. "mentioned by ~30% of respondents"), not an exact count, since exact counts overstate precision on small samples - Sentiment per theme must be exactly one of: Positive, Negative, Mixed, Neutral — not a descriptive phrase - Flag any theme where sentiment is Negative AND frequency is high (top half of themes by frequency) as "Priority" - Include 2-3 verbatim quotes per theme (lightly edited only for typos), not paraphrases - Do not invent or infer a theme that isn't actually present in the responses — if you're unsure whether something is a real pattern or a single outlier, say so explicitly rather than including it as a theme - Tone for the report: [YOUR PREFERRED TONE: e.g. clinical / conversational] Output Format: 1. Executive summary (3-4 sentences) 2. Theme table: Theme | Frequency | Sentiment | Priority flag 3. Quotes section, grouped by theme 4. Prioritized action items, ranked, each tied to a specific theme
Resultado
Executive Summary: Across the sampled responses to "What would make you more likely to renew?", three themes emerged clearly: pricing/value concerns (mentioned by roughly half of respondents), a desire for better onboarding support (about a third), and requests for a mobile app (about a quarter). Pricing sentiment is strongly negative and should be treated as the top priority.
| Theme | Frequency | Sentiment | Priority |
|---|---|---|---|
| Pricing / Value | ~50% | Negative | 🔴 Priority |
| Onboarding Support | ~33% | Mixed | Medium |
| Customer Support Speed | ~17% | Negative | Medium |
| Mobile App Request | ~25% | Neutral | Low |
Pricing / Value — Quotes:
"I like the product but I genuinely can't justify $200/month for what we actually use."
"Feels like we're paying for features three tiers up that we'll never touch."
Onboarding Support — Quotes:
"First two weeks were confusing — a guided setup call would have saved us a lot of back-and-forth."
"Once we figured it out it was great, just wish someone had walked us through it."
Prioritized Action Items:
- Pricing / Value (Negative, ~50%): Pilot a tiered or usage-based pricing option for the segment citing feature bloat — the single highest-leverage fix given both frequency and sentiment severity.
- Customer Support Speed (Negative, ~17%): Audit response-time SLAs; a modest improvement here directly addresses a named renewal blocker.
- Onboarding Support (Mixed, ~33%): Pilot a guided onboarding call for new accounts next quarter — lower urgency than pricing but affects a larger share of respondents.
- Mobile App Request (Neutral, ~25%): Log as a roadmap feature request — neutral sentiment suggests a nice-to-have, not a renewal blocker.
El fallo más común en el análisis de encuestas generado por IA es la proliferación de temas: pide a un modelo que clasifique 300 respuestas de texto abierto sin límite, y a menudo producirá 15 o 20 microtemas que en realidad son solo paráfrasis entre sí. Este prompt lo soluciona con un límite estricto de seis temas.
El sentimiento se restringe a cuatro etiquetas fijas — Positivo, Negativo, Mixto, Neutral — en lugar de texto descriptivo abierto, porque una columna de hoja de cálculo que dice "generalmente frustrado pero agradecido por las correcciones recientes" no se puede ordenar ni filtrar. La regla de la marca de Prioridad (sentimiento Negativo más alta frecuencia) hace el trabajo real de priorización.
Exigir 2-3 citas textuales por tema existe porque los hallazgos resumidos de encuestas suelen ser cuestionados en las reuniones — alguien siempre pregunta "¿puedo ver un ejemplo real?" — y tener el lenguaje real del cliente, no parafraseado, resuelve esa pregunta de inmediato.
La restricción contra inventar temas que no están realmente presentes en las respuestas importa más de lo que parece: los modelos de lenguaje a los que se les pide encontrar patrones en datos ambiguos a veces presentan un tema que suena plausible pero que en realidad es una extrapolación, no algo que los encuestados dijeron realmente.