Le Recurring Meeting Auditor : transformez votre calendrier en recommandations Keep-Cut-Shorten
Pourquoi ce prompt est important
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.
À quoi nous l'utilisons
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
Résultat
| 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 plupart des conseils pour réduire les réunions reviennent à « dis simplement non », ce qui ignore le vrai problème : personne n’a envie d’être celui qui supprime unilatéralement une réunion récurrente sans une raison solide, surtout s’il n’en est pas à l’origine. Ce prompt repose sur trois choix de conception qui transforment un vague sentiment de « trop de réunions » en un cas précis et proposable.
Pourquoi le prompt évalue par rapport à l’objectif déclaré, pas aux réunions en général
La consigne interdit explicitement de supprimer une réunion parce qu’elle est longue ou compte beaucoup de participants. Au lieu de cela, chaque recommandation doit remonter à un véritable décalage entre ce que la réunion dit être et ce que le temps synchrone exige réellement pour cet objectif. Une réunion dont le but est un vrai débat ou un renforcement de la confiance est protégée, même si elle coûte cher – le prompt est conçu pour trouver le gaspillage, pas pour être un outil brut qui coupe sans discernement.
Pourquoi il rédige le message concret, pas seulement une recommandation
Une recommandation du type « raccourcissez cette réunion » est inutile si vous devez encore écrire le message gênant qui la propose. Le prompt force une réponse rédigée et non défensive pour chaque changement, formulée autour de l’objectif de la réunion plutôt que comme une plainte. C’est l’étape qui est réellement utilisée – la plupart des gens abandonnent l’audit des réunions à l’étape d’analyse, car transformer un constat de tableau en une vraie conversation avec l’organisateur semble être une tâche distincte et plus difficile.
Pourquoi il protège certains types de réunions par conception
Les contraintes excluent explicitement les réunions dont le but est de « lire la salle », résoudre un conflit ou établir la confiance au sein d’une nouvelle équipe – celles-ci sont marquées uniquement KEEP ou SHORTEN, jamais CONVERT TO ASYNC ou CUT. C’est important car un audit naïf du coût en temps marquerait chaque réunion comme un gaspillage sur la seule base des chiffres, en oubliant que certains temps synchrones existent pour des raisons qu’un tableur ne peut pas capturer. Le prompt est conçu pour plaider en faveur de l’efficacité sans devenir un argument contre toute interaction humaine au travail.
Collez ici vos vraies réunions récurrentes avec leurs durées et nombres de participants réels, et soyez honnête sur l’objectif de chacune – la sortie n’est utile que si vous décrivez avec précision ce que chaque réunion est censée accomplir.