El Auditor de Reuniones Recurrentes: Convierte tu Calendario en una Recomendación Keep-Cut-Shorten
Por qué importa este prompt
The average knowledge worker now spends over 11 hours a week in meetings, and managers specifically average close to a quarter of their entire work week in them — costing roughly $29,000 per employee per year in direct salary time alone, before counting prep, follow-up, and the recovery time needed after context-switching out of back-to-back calls. Most of that time isn't reclaimed not because people don't notice the waste, but because nobody wants to be the person who unilaterally declares a meeting unnecessary without a structured case for why.
Para qué lo usamos
You're a mid-level manager who just did a rough tally and realized you're in 14 recurring meetings a week, several of which you inherited from a predecessor or joined "just in case" a year ago, and you have a strong suspicion at least a third of them could be cut or shortened — but you don't have a systematic way to make that case to the organizers without it sounding like you're just complaining about meetings.
Prompt
Act as an operations consultant who specializes in auditing recurring meetings for time-cost efficiency. Context: - My recurring meetings: [PASTE A LIST — for each meeting include: name, frequency, duration, number of attendees, and a one-line description of its stated purpose] - My team's approximate hourly cost: [AVERAGE FULLY-LOADED HOURLY RATE ACROSS ATTENDEES, OR JUST SKIP IF UNKNOWN] - My role in each meeting: [ORGANIZER, REQUIRED ATTENDEE, OR OPTIONAL ATTENDEE — note this per meeting if it varies] - What I'm optimizing for: [E.G. RECLAIM FOCUS TIME, CUT COSTS, REDUCE MY OWN MEETING LOAD SPECIFICALLY] Task: 1. For each meeting, calculate its approximate annual time cost: duration × frequency per year × number of attendees, and convert to a dollar figure if I gave you an hourly rate. 2. Score each meeting on two dimensions: (a) how clearly its stated purpose could be achieved through async means instead (status updates, decisions that don't need real-time debate), and (b) how essential my specific attendance is to that purpose. 3. Recommend one action per meeting: KEEP AS-IS, SHORTEN (and suggest a new duration), REDUCE FREQUENCY (and suggest a new cadence), CONVERT TO ASYNC, or CUT ENTIRELY. 4. For every recommendation that isn't KEEP AS-IS, draft a short, non-defensive message I could send to the meeting organizer or team proposing the change, framed around the meeting's own stated purpose rather than as a complaint about meetings in general. 5. Total up the annual hours and cost I'd reclaim if every non-KEEP recommendation were adopted. Constraints: - Do not recommend cutting a meeting just because it's long-running or has many attendees — base every recommendation strictly on the gap between its stated purpose and what a real-time synchronous meeting actually requires. - If a meeting's purpose is decision-making with genuine debate or relationship-building, that is a valid reason to KEEP it even if it's expensive — say so explicitly rather than defaulting to cutting everything. - Never suggest converting a meeting to async if its stated purpose involves reading a room, resolving conflict, or building trust across a new team — flag those as KEEP or SHORTEN only. - Keep each proposed change-message under 60 words. Output format: - A table: Meeting Name | Annual Hours | Annual Cost | Recommendation | Reasoning (one line) - Below the table, one drafted change-message per non-KEEP recommendation, labeled by meeting name - A closing summary: total hours and cost reclaimed if all recommendations are adopted, plus which single change would have the biggest impact if I could only make one
Resultado
| Meeting | Annual Hours | Annual Cost | Recommendation | Reasoning |
|---|---|---|---|---|
| Weekly Cross-Team Sync (30 min, 8 attendees) | 26 hrs | $2,340 | CONVERT TO ASYNC | Purpose is status sharing with no real decisions made in the room — a shared doc update covers this. |
| Monthly Roadmap Review (60 min, 12 attendees) | 12 hrs | $1,620 | SHORTEN to 30 min | Real decisions happen here, but the first 20 minutes is consistently a recap that could be pre-read. |
| Daily Standup (15 min, 6 attendees) | 65 hrs | $3,510 | REDUCE FREQUENCY to 3x/week | Team is not blocked often enough day-to-day to justify daily; async blockers channel covers the gap days. |
| Quarterly Team Offsite Planning (2 hrs, 10 attendees) | 8 hrs | $1,080 | KEEP AS-IS | Genuine relationship-building and open debate purpose — this is exactly what synchronous time is for. |
| 1:1 with Skip-Level Manager (30 min, 2 attendees) | 26 hrs | $1,404 | KEEP AS-IS | Relationship and trust-building purpose; cutting this would cost more in political capital than it saves. |
Drafted Change Messages
Weekly Cross-Team Sync: "Since this is mostly status updates without live decisions, could we try a shared async doc for two weeks instead? Happy to keep the live version if anyone feels we lose something important."
Monthly Roadmap Review: "Would it help if I sent the recap portion as a pre-read 24 hours before, so we can use the full 30 minutes for the actual roadmap decisions?"
Daily Standup: "We haven't had a same-day blocker in the last three standups — want to try Mon/Wed/Fri live with an async blockers-only channel the other two days?"
Summary
Adopting all three non-KEEP recommendations reclaims approximately 103 hours and $7,470 per year across the team. The single highest-impact change is reducing Daily Standup frequency — it accounts for more than half the reclaimed time and cost of any individual recommendation, because the per-occurrence cost of a 6-person meeting compounds fast at daily frequency even at just 15 minutes.
La mayoría de los consejos para reducir reuniones se reducen a "solo di que no", lo que ignora la fricción real: nadie quiere ser la persona que unilateralmente elimina una reunión recurrente sin una razón defendible, especialmente si no fue quien la creó. Este prompt está construido alrededor de tres decisiones de diseño que convierten una vaga sensación de "demasiadas reuniones" en un caso específico y proponible.
Por qué el Prompt Evalúa contra el Propósito Declarado, no contra las Reuniones en General
La instrucción prohíbe explícitamente eliminar una reunión por ser larga o tener muchos asistentes. En cambio, cada recomendación debe remontarse a una desalineación genuina entre lo que la reunión dice ser y lo que el tiempo síncrono realmente requiere para ese propósito. Una reunión cuyo propósito es un debate real o generar confianza se protege incluso si es costosa; el prompt está diseñado para encontrar desperdicio, no para ser un instrumento contundente que corte indiscriminadamente.
Por qué Redacta el Mensaje Real, no Solo una Recomendación
Una recomendación de "acortar esta reunión" es inútil si aún tienes que escribir el incómodo mensaje proponiéndolo. El prompt fuerza un mensaje redactado y no defensivo para cada cambio, enmarcado en el propósito de la reunión misma y no como una queja. Ese es el paso que realmente se usa; la mayoría abandona las auditorías de reuniones en la fase de análisis porque convertir un hallazgo de hoja de cálculo en una conversación real con el organizador se siente como una tarea separada y más difícil.
Por qué Protege Ciertos Tipos de Reuniones por Diseño
Las restricciones protegen explícitamente las reuniones cuyo propósito implica leer el ambiente, resolver conflictos o generar confianza en un equipo nuevo; estas solo se marcan como KEEP o SHORTEN, nunca CONVERT TO ASYNC o CUT. Esto importa porque una auditoría ingenua de costo-tiempo marcaría cada reunión como desperdicio puramente por las matemáticas, pasando por alto que parte del tiempo síncrono existe por razones que una hoja de cálculo no puede capturar. El prompt está diseñado para argumentar a favor de la eficiencia sin convertirse en un argumento contra toda interacción humana en el trabajo.
Pega aquí tus reuniones recurrentes reales con duraciones y cantidades de asistentes reales, y sé honesto sobre el propósito real de cada una; el output solo es tan útil como lo preciso que seas al describir lo que cada reunión realmente debería lograr.