El convertidor de SWOT a plan de 30 días: convierte una reunión estratégica en un calendario de ejecución
Why this prompt matters
Strategy sessions produce a burst of clarity that decays fast once everyone returns to their normal workload — without an immediate translation into owned, dated actions, a SWOT analysis becomes a slide that gets referenced once at the next quarterly review and never again, while the weaknesses and threats it identified keep compounding untouched in the meantime.
What we use it for
A 12-person SaaS company just wrapped a quarterly strategy offsite with a completed SWOT analysis on a whiteboard — churn is flagged as a weakness, rising AWS costs as a threat, a competitor's weak enterprise tier as an opportunity — but the founder has to walk into Monday's all-hands with a concrete 30-day plan, not a photo of a whiteboard nobody will look at again.
Prompt
ROLE: Act as an experienced operations consultant who specializes in converting strategic analysis into executable plans. You are not a strategist generating more ideas — you are the person who turns ideas into a schedule. CONTEXT: Here is our completed SWOT analysis: Strengths: [PASTE YOUR STRENGTHS LIST] Weaknesses: [PASTE YOUR WEAKNESSES LIST] Opportunities: [PASTE YOUR OPPORTUNITIES LIST] Threats: [PASTE YOUR THREATS LIST] Team size available to execute this plan: [NUMBER OF PEOPLE] Approximate hours per week each person can dedicate to new initiatives (beyond regular work): [HOURS PER WEEK] TASK: Convert this SWOT analysis into a 30-day action plan broken into 4 weekly blocks. Every single action item must: 1. Be specific and measurable (not "improve X" but "do Y, measured by Z") 2. Cite exactly which SWOT item it addresses (e.g., "Addresses Weakness #2") 3. Be sized realistically to the stated team capacity — do not assume unlimited hours CONSTRAINTS: - Maximum [NUMBER, e.g. 5] action items per week — prioritize ruthlessly rather than listing everything possible - At least one action per week must directly address a Weakness or a Threat — do not let the plan become 100% opportunity-chasing - Do not invent SWOT items that weren't provided — only work with what's given - If the stated team capacity is clearly insufficient for a meaningful 30-day plan, say so explicitly instead of producing an unrealistic schedule OUTPUT FORMAT: For each of the 4 weeks, produce a table with these columns: Action | SWOT Source | Owner (use role titles like "[MARKETING LEAD]" if no names given) | Success Metric | Priority (High/Medium/Low). After the 4 weekly tables, add a short "Week 5 Check-In" section listing 3 questions the team should ask itself to evaluate whether the plan is working, so there's a built-in review point at the end of the 30 days.
Result
Week 1
| Action | SWOT Source | Owner | Success Metric | Priority |
|---|---|---|---|---|
| Interview 5 churned customers from the last 60 days to identify the top 2 reasons they left | Weakness #2 (high churn, unclear cause) | [HEAD OF CUSTOMER SUCCESS] | 5 completed interviews, findings summarized in one page | High |
| Draft a one-page competitive comparison highlighting our faster onboarding time (avg. 2 days vs. competitor's 9) | Strength #1 (fast onboarding) | [PRODUCT MARKETING] | Comparison doc reviewed and approved by founder | Medium |
| Audit current AWS spend against usage to identify the source of last quarter's 40% cost overrun | Threat #1 (rising infra costs eating margin) | [ENGINEERING LEAD] | Cost breakdown by service delivered, 3 reduction options identified | High |
Week 2
| Action | SWOT Source | Owner | Success Metric | Priority |
|---|---|---|---|---|
| Based on Week 1 churn interviews, ship a fix or workaround for the top-cited complaint | Weakness #2 | [PRODUCT LEAD] | Fix shipped or workaround documented and communicated to affected customers | High |
| Reach out to 10 prospects in the enterprise segment identified as underserved by competitors | Opportunity #1 (competitor left enterprise tier weak) | [SALES LEAD] | 10 outbound contacts made, 2+ discovery calls booked | Medium |
| Implement the top AWS cost reduction identified in Week 1's audit | Threat #1 | [ENGINEERING LEAD] | Measurable reduction in weekly infra spend, tracked in dashboard | High |
Week 3
| Action | SWOT Source | Owner | Success Metric | Priority |
|---|---|---|---|---|
| Publish the onboarding-speed comparison as a landing page targeting competitor-comparison search terms | Strength #1 | [PRODUCT MARKETING] | Page live, tracked for organic traffic starting this week | Medium |
| Formalize a churn early-warning check-in at day 14 and day 45 of the customer lifecycle | Weakness #2 | [HEAD OF CUSTOMER SUCCESS] | Process documented, first check-ins scheduled for existing at-risk accounts | High |
| Follow up with Week 2's enterprise discovery calls and send tailored proposals | Opportunity #1 | [SALES LEAD] | At least 1 proposal sent | Medium |
Week 4
| Action | SWOT Source | Owner | Success Metric | Priority |
|---|---|---|---|---|
| Measure churn rate for the 30-day period against the prior 30 days to see if Week 1-2 fixes moved the number | Weakness #2 | [HEAD OF CUSTOMER SUCCESS] | Before/after churn comparison delivered | High |
| Review infra cost trend since the Week 2 change and decide whether to pursue the second reduction option | Threat #1 | [ENGINEERING LEAD] | Go/no-go decision documented with updated cost projection | Medium |
| Compile results from the enterprise outbound push and decide whether to formalize it as an ongoing motion | Opportunity #1 | [SALES LEAD] | Pipeline value from the 30-day push reported | Medium |
Week 5 Check-In
- Did churn actually move, or did we only address the most visible complaint while the underlying cause persists?
- Is the enterprise outbound push generating real pipeline, or was 30 days too short to judge — and should we extend it another cycle?
- Which of these four weeks' actions took meaningfully longer than the team's stated capacity allowed, and does the next 30-day plan need to be less ambitious?
La mayoría de los análisis SWOT mueren en el momento en que se borra la pizarra. El ejercicio en sí es sencillo: enumera fortalezas, debilidades, oportunidades, amenazas, discute a qué cuadrante pertenece un hecho, toma una foto de la pizarra. Lo que casi nunca ocurre es el paso más difícil: convertir cuatro listas de observaciones en una secuencia de acciones específicas, asignadas a personas concretas, con un plazo y una forma de saber si funcionó.
Por qué este prompt está estructurado así
La sección de Rol presenta al modelo como un consultor de operaciones y no como un estratega, deliberadamente. Los consultores estratégicos son buenos produciendo más análisis; los consultores de operaciones están entrenados para preguntar "quién hace qué y para cuándo". Ese enfoque ya cambia la forma del resultado: obtienes un cronograma, no otro framework.
El bloque de Contexto obliga al usuario a pegar su contenido SWOT real más dos restricciones que la mayoría de los prompts de planificación omiten: el tamaño del equipo y las horas disponibles por semana. Un plan de 30 días para un equipo de 3 personas y una división de 300 personas no puede usar la misma densidad de acciones, y un prompt que ignora la capacidad produce planes que nadie puede ejecutar.
La instrucción de Tarea exige que cada acción cite de qué cuadrante SWOT proviene. Este requisito de trazabilidad es más importante de lo que parece: evita que el modelo genere relleno genérico de consejos para startups ("mejorar la comunicación", "enfocarse en el crecimiento") que en realidad no se deriva del análisis que el usuario hizo. Si una acción no se puede rastrear hasta una línea específica del SWOT, no debería estar en el plan.
La sección de Restricciones limita cada semana a un número fijo de acciones y exige que al menos una acción por semana aborde directamente una debilidad o amenaza, no solo que persiga una oportunidad. Los equipos que salen de sesiones de estrategia tienden a gravitar hacia acciones emocionantes del lado de las oportunidades e ignoran silenciosamente las debilidades y amenazas que son menos divertidas de trabajar. La restricción fuerza el equilibrio.
Donde esto demuestra su valor
El formato del plan —una tabla semana a semana con una acción, su fuente SWOT, un responsable y una métrica de éxito— está deliberadamente diseñado para que puedas pegarlo directamente en una herramienta de gestión de proyectos o en una agenda de standup del lunes sin necesidad de reformatear. Esa es la diferencia entre un prompt que produce un documento interesante y uno que produce algo que un equipo realmente usa.
Úsalo justo después de cualquier sesión de estrategia, mientras el SWOT aún está fresco, no semanas después cuando nadie recuerda el razonamiento detrás de cada elemento.