O Auditor de Reuniões Recorrentes: Transforme seu Calendário em uma Recomendação de Keep-Cut-Shorten
Porque é que este prompt importa
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 que o 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.
A maioria dos conselhos sobre cortar reuniões se resume a "simplesmente diga não", o que ignora o atrito real: ninguém quer ser a pessoa que mata unilateralmente uma reunião recorrente sem uma razão defensável, especialmente quando não foi ela quem a criou. Este prompt foi construído em torno de três escolhas de design que transformam uma sensação vaga de "reuniões demais" em um caso específico e passível de ser proposto.
Por que o Prompt Avalia Contra o Propósito Declarado, Não Contra Reuniões em Geral
A instrução proíbe explicitamente cortar uma reunião por ser longa ou ter muitos participantes. Em vez disso, toda recomendação precisa remontar a um descompasso genuíno entre o que a reunião diz que é para e o que o tempo síncrono realmente exige para aquele propósito. Uma reunião cujo propósito é debate real ou construção de confiança é protegida mesmo que seja cara — o prompt foi projetado para encontrar desperdício, não para ser um instrumento bruto que corta indiscriminadamente.
Por que Ele Redige a Mensagem Real, Não Apenas uma Recomendação
Uma recomendação de "encurte esta reunião" é inútil se você ainda precisa escrever a mensagem awkward propondo isso. O prompt força uma mensagem redigida e não defensiva para cada mudança, enquadrada em torno do próprio propósito da reunião, não como uma reclamação. Esse é o passo que realmente é usado — a maioria das pessoas abandona auditorias de reunião na fase de análise porque transformar uma descoberta de planilha em uma conversa real com o organizador parece uma tarefa separada e mais difícil.
Por que Ele Protege Certos Tipos de Reunião por Design
As restrições excluem explicitamente reuniões cujo propósito envolve ler o ambiente, resolver conflitos ou construir confiança em uma equipe nova — essas são marcadas como KEEP ou SHORTEN apenas, nunca CONVERT TO ASYNC ou CUT. Isso importa porque uma auditoria ingênua de tempo-custo marcaria toda reunião como desperdício puramente pela matemática, ignorando que algum tempo síncrono existe por razões que uma planilha não consegue capturar. O prompt foi projetado para fazer um caso pela eficiência sem se tornar um argumento contra toda interação humana no trabalho.
Cole suas reuniões recorrentes reais com durações reais e contagens de participantes, e seja honesto sobre o propósito real de cada uma — a saída só é tão útil quanto o quão precisamente você descreve o que cada reunião realmente deveria realizar.