Este prompt de IA transforma datos de encuestas en un plan de acción ejecutable
Why this prompt matters
Survey projects often fail at the last mile. Teams collect hundreds of responses, then waste hours manually clustering comments, arguing over weak patterns, or presenting leadership with a pile of disconnected charts. A strong analysis prompt turns messy feedback into prioritized decisions, which helps teams act faster and reduces the risk of overreacting to the loudest comments instead of the strongest signals.
What we use it for
You have just closed a customer or employee survey and need to brief leadership before the next planning meeting. Instead of dumping charts into slides, you need a fast, decision-oriented readout that explains what changed, what matters most, and what the team should do next.
Prompt
Role: Act as a senior research analyst and insight strategist for [COMPANY / TEAM NAME]. Context: I will give you raw survey data, pasted comments, response counts, rating breakdowns, and background on what decision we need to make. The audience is [EXECUTIVE TEAM / PRODUCT TEAM / CUSTOMER SUCCESS / MARKETING]. The survey goal is [GOAL OF THE SURVEY]. The data may be messy, repetitive, emotionally charged, or incomplete. Task: Analyze the survey results and turn them into an executive-ready insight report that explains what matters, what is noise, and what actions should happen next. Constraints: 1. Separate quantitative patterns from qualitative themes. 2. Identify the 5-7 most important findings, not every possible observation. 3. Highlight contradictions, outliers, weak signals, and data limitations. 4. Do not overclaim causation when the survey only supports correlation or directional insight. 5. If sample size, question wording, or response quality weakens confidence, say so explicitly. 6. Quote short respondent comments only when they sharpen a theme. 7. Prioritize decisions and actions by likely business impact and ease of implementation. 8. If the dataset suggests different conclusions for different segments, split them clearly by [CUSTOMER TYPE / REGION / TEAM / ROLE / TENURE]. 9. Keep the writing concise, specific, and executive-friendly. Avoid generic filler. Output Format: 1. Survey Snapshot - Purpose of survey - Who responded - Sample size - Important caveats 2. Key Findings - Ranked list of the most important findings - Evidence for each finding - Confidence level: High / Medium / Low 3. Theme Breakdown - Top recurring positive themes - Top recurring negative themes - Surprising or contradictory themes 4. Segment Differences - Differences by [SEGMENT TYPE] - What each difference may imply 5. Recommended Actions - Immediate actions for the next 30 days - Medium-term actions for the next 90 days - One action to avoid because the data does not support it 6. Executive Summary - A final 150-200 word summary for leadership Data to analyze: [PASTE SURVEY SCORES, TABLES, COMMENTS, AND CONTEXT HERE]
Result
Survey Snapshot: The survey was designed to understand why trial users of AcmeFlow were not converting to paid plans after the first 14 days. We received 842 responses from users in North America and Europe, including 311 product managers, 228 operations leads, 179 founders, and 124 analysts. The strongest caveat is self-selection bias: dissatisfied users were slightly more likely to leave open-text feedback than satisfied users. We should treat the qualitative comments as directional, not perfectly representative.
Key Findings: First, setup friction is the single biggest conversion blocker. Forty-six percent of respondents who did not upgrade said they were unsure how to configure workflows after initial onboarding. Confidence: High. Second, value perception depends heavily on role. Founders responded positively to dashboard visibility, while operations leads cared more about automation reliability and integration depth. Confidence: High. Third, pricing is a secondary issue, not the primary one. Only 18 percent cited price alone, but 39 percent said price felt too high relative to the value they reached in the first week. Confidence: Medium. Fourth, support quality is performing well but is underused. Many respondents praised support once they engaged, yet only 22 percent of struggling users contacted the team. Confidence: Medium. Fifth, European respondents showed higher concern about data export and compliance documentation than North American respondents. Confidence: Medium.
Theme Breakdown: Positive themes included fast reporting, clean UI, and strong cross-team visibility. Negative themes clustered around confusing setup steps, unclear templates, and unreliable first-time integrations with Slack and HubSpot. A surprising contradiction emerged in workflow complexity: advanced users wanted more control, while new users felt overwhelmed by the same flexibility.
Recommended Actions: In the next 30 days, the team should simplify first-run setup into a guided path with three opinionated templates, add an in-app prompt to contact support after failed integration attempts, and rewrite pricing-page messaging around time-to-value rather than feature volume. Over the next 90 days, the team should create role-specific onboarding for operations leads, expand integration diagnostics, and publish clearer compliance documentation for EU buyers. One action to avoid: cutting price immediately. The survey does not show a pure pricing problem; it shows a delayed value realization problem.
Executive Summary: Users are not rejecting the product’s promise. They are struggling to reach the moment where that promise becomes obvious. The biggest opportunity is to reduce setup friction, especially for operations-heavy teams, while clarifying role-based value much earlier in the trial. Pricing pressure exists, but it is mostly downstream of weak onboarding and uneven activation. If AcmeFlow improves first-week guidance and integration reliability, conversion should rise without requiring broad discounting.
La mayoría de los equipos no tienen problemas para recopilar datos de encuestas. El verdadero desafío es explicar lo que significan sin ahogar a todos en gráficos, comentarios e interpretaciones contradictorias.
Este Prompt está diseñado para cubrir exactamente esa brecha. Convierte respuestas desordenadas de encuestas en un análisis estructurado que separa la señal del ruido, jerarquiza los hallazgos más importantes y termina con acciones concretas en lugar de observaciones vagas.
Por qué funciona este Prompt
La estructura obliga al modelo a hacer más que solo resumir. Tiene que separar patrones cuantitativos de temas cualitativos, asignar niveles de confianza, señalar evidencia débil y evitar la certeza falsa. Esto es importante porque el análisis de encuestas suele fallar cuando los equipos tratan todos los comentarios por igual o confunden correlación con causalidad.
También incluye análisis por segmentos, que es donde suelen estar los verdaderos hallazgos. Un único puntaje promedio puede ocultar diferencias marcadas entre clientes nuevos y usuarios avanzados, o entre una región y otra. El Prompt hace explícitas esas diferencias en lugar de homogeneizarlas.
Por qué vale la pena guardarlo
Este no es un Prompt de un solo uso para una demostración bonita. Es útil para encuestas de compromiso de empleados, investigaciones de satisfacción de clientes, retroalimentación posterior al lanzamiento, análisis de abandono, formularios de seguimiento de eventos y revisiones de procesos internos.
El resultado final está pensado para la toma de decisiones real. En lugar de entregarle al liderazgo una hoja de cálculo y un montón de citas, obtienes hallazgos jerarquizados, contradicciones, diferencias entre segmentos y próximos pasos inmediatos. Eso hace que el Prompt sea práctico para ciclos de informes semanales y mensuales.
Cómo usarlo bien
Pega tanto los números como los comentarios. Incluye el número de respuestas, el tamaño de la muestra y cualquier limitación conocida. Si deseas un resultado más sólido, especifica la audiencia y la decisión que depende de la encuesta.
Una buena entrada mejora drásticamente el resultado. Si el modelo sabe si el informe es para producto, operaciones, RRHH o la dirección ejecutiva, puede priorizar los hallazgos correctos y escribir con el nivel de detalle adecuado.
Mejores casos de uso
Este Prompt es especialmente eficaz cuando la retroalimentación es desordenada, emocional, repetitiva o está dispersa entre múltiples grupos de encuestados. Ayuda a crear una narrativa limpia a partir de datos incompletos sin fingir que los datos son más precisos de lo que realmente son.
Ese equilibrio es el verdadero valor. Un resumen útil de una encuesta no solo describe respuestas. Ayuda a un equipo a decidir qué hacer a continuación.