L'extracteur de journal de décisions de réunion : transformer un relevé brouillon en une répartition claire des responsabilités
Why this prompt matters
Teams routinely walk out of the same meeting with three different understandings of what was decided, and only discover the mismatch when someone ships the wrong thing two sprints later. A vague 'we'll sort it out' that gets written into a recap as a firm decision is one of the most common sources of cross-functional rework — and it is far cheaper to catch the ambiguity in the first hour after the meeting than to unwind a sprint's worth of misdirected work.
What we use it for
A product manager just left a 45-minute cross-functional planning meeting between engineering, design, and marketing about a delayed Q3 feature launch, and needs to send a decision recap within the hour — before people's memories of who-agreed-to-what start to diverge — but manually re-listening to the recording or notes to reconstruct exactly what was agreed would take 20+ minutes and still risk missing a contradiction between two speakers.
Prompt
Act as an experienced chief-of-staff or operations lead who has run hundreds of cross-functional meetings and knows exactly how a vague "we'll figure it out" turns into three teams building three different things a week later. CONTEXT: - Meeting transcript or raw notes: [MEETING TRANSCRIPT OR NOTES] - Participants and their roles: [MEETING PARTICIPANTS AND ROLES] - Meeting purpose/agenda: [MEETING PURPOSE] TASK: Extract a clean decision log from the raw meeting content. Distinguish clearly between what was actually decided and what was merely discussed. CONSTRAINTS: - Only list something as a "Decision Made" if the transcript shows clear agreement — do not invent an owner or deadline if none was actually stated - If a decision sounded final but had no named owner or deadline, flag it under Ambiguity Flags instead of the Decisions table — do not guess - If two participants appeared to agree on different versions of the same decision, call out the contradiction explicitly - Do not pad the output with meeting-process commentary (no "the meeting opened with..." narration) — go straight to substance - Keep each decision to one line; put nuance and caveats in a separate notes column, not the decision text itself OUTPUT FORMAT: 1. Decisions Made (table: Decision | Owner | Deadline | Confidence — high/medium/low based on how explicit the transcript was) 2. Open Items Requiring Follow-up (things discussed but not resolved, with who needs to weigh in next) 3. Ambiguity Flags (things that sounded decided but had no clear owner/deadline, or where speakers seemed to disagree) 4. Suggested One-Line Recap (a single Slack-ready message summarizing the meeting's outcome for people who weren't there)
Result
1. Decisions Made
| Decision | Owner | Deadline | Confidence |
|---|---|---|---|
| Q3 launch date moves from Aug 15 to Sep 5 | Priya (PM) | Confirmed in meeting | High |
| Onboarding flow ships without the referral-code step for launch; referral code becomes a fast-follow | Dan (Eng Lead) | Fast-follow by Sep 19 | High |
| Marketing holds the press release until engineering confirms the new date is locked | Sam (Marketing) | Confirmation needed by Aug 29 | Medium — Sam agreed but didn't explicitly confirm the Aug 29 checkpoint date, inferred from context |
2. Open Items Requiring Follow-up
- Design has not confirmed whether the simplified onboarding flow needs new user-research validation before the Sep 5 date — Priya to follow up with Design lead (Wren) directly, not resolved in this meeting
- Budget for the delayed launch's paid marketing push was mentioned as "probably fine" by Sam but not confirmed against actual Q3 budget — needs Finance sign-off before marketing commits spend
3. Ambiguity Flags
- Dan said engineering "should be able to" hit Sep 5, which is weaker language than a firm commitment — this is recorded as a decision in the log above but the confidence is medium-high, not certain; recommend a written confirmation from Dan before treating Sep 5 as locked
- Priya and Sam appeared to agree the referral code delay was fine, but Sam's tone ("I guess that works") suggests lower conviction than Priya's framing implied — worth a direct check-in with Sam before external commitments reference the fast-follow date
4. Suggested One-Line Recap
"Q3 launch moves to Sep 5 without referral codes (fast-follow by Sep 19); marketing holds the press release until engineering reconfirms the date by Aug 29 — still need Design's read on onboarding research and Finance sign-off on the delayed launch's ad budget."
Chaque équipe a vécu cela : une réunion de planification de 45 minutes se termine, tout le monde hoche la tête, et deux semaines plus tard, on découvre que trois personnes sont reparties avec trois compréhensions différentes de ce qui avait réellement été convenu. L'e-mail de récapitulation est rédigé de mémoire, la paraphrase confiante de quelqu'un disant « on va régler ça » devient un engagement ferme par écrit, et au moment où quelqu'un remarque le décalage, l'équivalent d'un sprint de travail est déjà orienté dans la mauvaise direction.
Ce prompt est conçu pour combler cet écart dans la première heure, et non après coup. Il prend un transcript brut de réunion ou des notes et produit un journal des décisions qui trace une ligne claire entre ce qui a été réellement décidé et ce qui a simplement semblé l'être.
Pourquoi le signalement des ambiguïtés est plus important que la liste des décisions
La plupart des outils de synthèse de réunions produisent volontiers une liste propre de « décisions » — mais une liste d'apparence propre est précisément le problème lorsque la moitié de son contenu n'a jamais été véritablement verrouillée. Ce prompt reçoit pour instruction explicite de ne pas inventer un responsable ou une échéance lorsque le transcript ne les mentionne pas, et de signaler le langage flou (« devrait pouvoir », « je suppose que ça marche ») comme étant de moindre confiance, même lorsqu'il s'agit techniquement d'un accord. Cette distinction constitue l'entière valeur du prompt : il est conçu pour faire remonter les deux ou trois décisions de chaque réunion qui semblent réglées dans la salle, mais qui s'effondreront dès que quelqu'un agira sans qu'un véritable responsable ne soit attaché.
Comment l'utiliser
Collez un transcript ou vos propres notes brutes, accompagnés des participants et de l'objet de la réunion. Exécutez-le immédiatement après la fin de la réunion, tant que le contexte est encore suffisamment frais pour vérifier le résultat par rapport à votre propre mémoire — les signaux d'ambiguïté sont surtout utiles comme déclencheur pour un message de suivi de deux minutes (« hé, peux-tu confirmer que tu es bien en charge de X d'ici Y »), et non comme un enregistrement définitif en soi.