El sprint de preparación de reuniones: convierte nombres de asistentes y una agenda en un resumen de cinco minutos
Por qué importa este prompt
Senior professionals routinely spend 20-plus hours a week in meetings. Walking into one without knowing who has influence in the room, what they're likely to push back on, or which question actually needs answering turns a scheduled 30 minutes into a wasted slot — and often a second meeting just to get the decision the first one was supposed to produce.
Para qué lo usamos
You have a 30-minute call in two hours with a VP of Engineering at a potential client and two of their staff engineers, and all you have is their names, titles, and a two-line agenda emailed by an assistant. You've never spoken with any of them before.
Prompt
Role: Act as an executive briefing analyst preparing me for an upcoming meeting. Context: - Meeting purpose: [ONE-SENTENCE MEETING GOAL] - Attendees: [LIST NAMES, TITLES, COMPANIES] - What I know about them already: [PASTE ANY NOTES, LINKEDIN SUMMARIES, PAST EMAIL THREADS] - Meeting agenda (if any): [PASTE AGENDA OR BULLET POINTS] - My goal for this meeting: [WHAT YOU WANT TO WALK AWAY WITH] Task: Produce a single-page briefing that prepares me to walk into this meeting confident and informed. For each attendee, infer likely priorities and potential objections based on their role and any notes provided. Identify the 3 most important talking points I should raise, in priority order. Draft 5 sharp questions I should ask that will surface information I don't already have. Flag any risk of this meeting going off the rails (e.g., an attendee who might dominate, a topic likely to cause disagreement) and suggest how to redirect if it happens. Constraints: - Do not invent facts about attendees you have no basis for — say "unknown, worth asking" instead of guessing. - Keep the talking points and questions specific to this meeting, not generic best practices. - Total output must be readable in under 5 minutes. - Flag if the stated meeting goal and the agenda don't actually match — this is one of the most common causes of wasted meetings. Output Format: ## Meeting Briefing: [Meeting name] **Attendee snapshot** (one line per person: role, likely priority, one thing to watch for) **Top 3 talking points** (numbered, priority order, one sentence each on why it matters) **5 questions to ask** (numbered, each paired with what answer would tell you) **Risk flags** (if any — otherwise state "no major risks identified") **Goal-agenda mismatch check** (state clearly: aligned / misaligned, and why)
Resultado
Meeting Briefing: Northwind Logistics API Integration Call
Attendee snapshot
Sarah Chen, VP of Engineering — likely priority: minimizing integration risk to their Q4 roadmap; watch for: moves fast, dislikes long technical tangents.
Marcus Webb, Staff Engineer — likely priority: implementation details, rate limits, error handling; watch for: may ask pointed questions about SLA history.
Priya Raman, Staff Engineer — unknown priority, no notes provided — worth asking directly what she's evaluating for.
Top 3 talking points
1. Lead with integration timeline and rollback plan — Sarah's Q4 roadmap concern means she'll judge this meeting on risk, not features.
2. Have rate-limit and uptime numbers ready before Marcus asks — arriving with these unprompted signals you've done the engineering homework, not just the sales pitch.
3. Confirm Northwind's actual technical blocker, since the agenda just says "explore integration" — that phrasing usually means someone upstream already has a specific concern nobody wrote down.
5 questions to ask
1. "What's the one thing that would make this a no for you?" — surfaces the real objection instead of six surface-level ones.
2. "Who else needs to sign off after this call?" — tells you if Sarah is the actual decision-maker or a gatekeeper.
3. "What's your current fallback if you don't integrate with us?" — reveals your real competitive alternative.
4. "What does your Q4 roadmap actually require from an API partner, technically?" — turns a vague "minimize risk" priority into a checklist you can address directly.
5. "Is there a past integration that went badly for your team?" — Marcus's SLA-history question suggests a possible bad prior experience; asking directly surfaces it instead of you guessing.
Risk flags
Marcus may dominate with technical minutiae; if the conversation stalls on rate-limit edge cases for more than 5 minutes, redirect with: "Let's get Priya's take on the higher-level fit, and I'll follow up on the technical spec in writing." Priya's priorities are unknown — if she stays quiet, directly ask her what she's evaluating for before the call ends.
Goal-agenda mismatch check
Misaligned. Your stated goal is "get a verbal commitment to a pilot," but the agenda only says "explore integration" — a much lower bar. Recommend opening the call by explicitly naming your goal ("I'd love for us to leave today with a decision on a 30-day pilot") so it isn't assumed to be a pure discovery call by the other side.
La mayoría de la gente se prepara para una reunión desconocida echando un vistazo de dos minutos a un perfil de LinkedIn justo antes — si es que se prepara. Este prompt convierte lo que tengas a mano (nombres, cargos, una agenda breve, quizás un hilo de correo antiguo) en un resumen estructurado que puedes leer en menos de cinco minutos, diseñado específicamente en torno a lo que realmente descarrila las reuniones: no saber quién tiene influencia en la sala, y no conocer la objeción real hasta que es demasiado tarde para abordarla.
Por qué funciona esta estructura
El prompt se construye en torno a cinco secciones, cada una resolviendo un modo de fallo específico en la preparación de reuniones. El resumen de asistentes te obliga a separar lo que realmente sabes de lo que estás asumiendo — la instrucción de marcar "desconocido, vale la pena preguntar" en lugar de adivinar es deliberada, porque una suposición equivocada con confianza sobre las prioridades de alguien es peor que admitir que no lo sabes.
Los puntos de conversación están limitados a tres y ordenados por prioridad, porque un resumen con doce puntos con el mismo peso no es un resumen, es una transcripción. Las cinco preguntas van acompañadas de qué respuesta deberían revelar — una pregunta que haces sin saber qué estás buscando es solo relleno.
La sección de señales de riesgo existe porque la mayoría de las reuniones que salen mal no fallan por falta de preparación sobre el contenido — fallan porque un asistente domina, o un desacuerdo predecible descarrila la agenda, y nadie planeó cómo redirigir de antemano.
La verificación final — alineación entre objetivo y agenda — detecta uno de los fallos más comunes y más evitables: entrar a una reunión donde tu objetivo ("conseguir un compromiso") y la agenda declarada ("explorar opciones") nunca fueron realmente lo mismo, y nadie lo notó hasta que la reunión terminó sin una decisión.
Caso de uso
Tienes una llamada de 30 minutos dentro de dos horas con un VP de Ingeniería de un cliente potencial y dos de sus ingenieros senior, y todo lo que tienes son sus nombres, cargos y una agenda de dos líneas que envió su asistente por correo. Nunca has hablado con ninguno de ellos.
Por qué importa
Los profesionales senior suelen pasar más de 20 horas semanales en reuniones. Entrar a una sin saber quién tiene influencia en la sala, qué es probable que rechacen, o qué pregunta realmente necesita respuesta convierte 30 minutos programados en tiempo perdido — y a menudo una segunda reunión solo para obtener la decisión que la primera debía producir.