IntermédiaireProductivity

Prompt Meeting Minutes Détaillées

Rédigez un compte-rendu de réunion structuré : participants, objectifs, discussions par point d'ordre du jour, décisions et prochaines étapes. Format professionnel pour archiver et diffuser aux absents avec traçabilité complète.

Variables à personnaliser

{{TRANSCRIPTION_OU_NOTES}}Transcription ou notes

Aperçu en direct

📄 Prompt Minutes de Réunion

Rédige des minutes de réunion détaillées à partir de : {{TRANSCRIPTION_OU_NOTES}}

Inclus :
📋 Participants : Liste tous les participants avec leurs rôles et départements.
🗣️ Points de discussion : Résume les sujets abordés, incluant les débats ou points de vue alternatifs.
✅ Décisions prises : Note les décisions prises, qui les a prises, et leur justification.
📌 Actions à faire : Précise les tâches assignées, les responsables et les deadlines.
📊 Données et insights : Mets en avant les données présentées ou insights partagés qui ont influencé la réunion.
🔄 Suivi : Note les réunions de suivi ou checkpoints convenus.

Code API

from openai import OpenAI

client = OpenAI()

response = client.chat.completions.create(
    model="gpt-4o",
    messages=[
        {"role": "user", "content": "📄 Prompt Minutes de Réunion\n\nRédige des minutes de réunion détaillées à partir de : {{TRANSCRIPTION_OU_NOTES}}\n\nInclus :\n📋 Participants : Liste tous les participants avec leurs rôles et départements.\n🗣️ Points de discussion : Résume les sujets abordés, incluant les débats ou points de vue alternatifs.\n✅ Décisions prises : Note les décisions prises, qui les a prises, et leur justification.\n📌 Actions à faire : Précise les tâches assignées, les responsables et les deadlines.\n📊 Données et insights : Mets en avant les données présentées ou insights partagés qui ont influencé la réunion.\n🔄 Suivi : Note les réunions de suivi ou checkpoints convenus."}
    ],
    temperature=0.5,
    max_tokens=2048,
)

print(response.choices[0].message.content)

Conseils d'utilisation

Utilisez ce format détaillé pour les réunions cross-départements où l'accountability est critique (executive meetings, project kickoffs)
Copiez-collez directement les Action Items dans votre outil de gestion de projet (Asana, Monday, Notion) pour éviter que les décisions restent lettre morte
Archivez ces minutes dans un dossier partagé daté (ex: "2025-12-05_Product-Roadmap-Review.pdf") pour référence future et onboarding

Exemple de résultat

**MEETING MINUTES - Product Roadmap Review Q1 2026**

**Meeting Information**
Date: December 8, 2025, 2:00 PM - 4:00 PM
Location: Conference Room B / Zoom Hybrid

📋 **ATTENDEES**
- Sarah Chen, VP Product (Meeting Lead)
- Marc Dubois, CTO
- Julie Martin, Head of Engineering
- Thomas Roux, Head of Design
- Claire Petit, Product Marketing Manager
- Kevin Blanc, Customer Success Lead

🗣️ **DISCUSSION POINTS**

**1. Q1 Feature Priorities**
Sarah presented the proposed roadmap with 12 features ranked by customer demand (NPS survey data, 450 responses). Debate centered on whether to prioritize "Advanced Reporting Dashboard" (requested by 67% of enterprise clients) vs "Mobile App Redesign" (38% of all users but higher churn impact).

Marc raised technical debt concerns: current codebase requires 3 weeks refactoring before advanced reporting is feasible. Julie supported mobile redesign as "lower effort, higher immediate impact."

Thomas presented user research showing mobile UX is primary complaint in 1-star App Store reviews (42% mention), correlating with 23% higher churn rate for mobile-only users.

**2. Resource Allocation**
Engineering capacity: 2 senior devs, 3 mid-level devs available Q1 (one senior on parental leave). Design has bandwidth for max 2 major features. Decision to limit scope to 3-4 features max vs original 8.

**3. Customer Beta Program**
Claire proposed inviting 20 enterprise customers to beta test features pre-launch. Kevin supported, offering Customer Success team to manage communications. Concern raised about beta churn risk if features are buggy.

✅ **DECISIONS MADE**

**Decision 1: Mobile App Redesign is Q1 Priority #1**
- Decision Maker: Sarah Chen (VP Product), with unanimous team support
- Rationale: Higher ROI (lower dev effort + direct churn reduction), backed by user research data showing 23% churn increase for mobile users. Advanced Reporting deferred to Q2 after technical debt resolved

**Decision 2: Limit Q1 Scope to 3 Features**
- Decision Maker: Sarah Chen, Marc Dubois
- Rationale: Engineering capacity constraints and need for quality over quantity. Focus on Mobile Redesign + 2 quick wins (push notifications, bulk actions)

**Decision 3: Launch Closed Beta Program with 15 Enterprise Customers**
- Decision Maker: Sarah Chen, Claire Petit
- Rationale: Reduced from 20 to 15 to minimize risk. Only invite customers with &lt;6 months contract remaining (incentivize renewal). Customer Success to handle outreach

📌 **ACTION ITEMS**

| Task | Owner | Deadline | Status |
|------|-------|----------|--------|
| Finalize mobile app wireframes (20 screens) | Thomas Roux | Dec 15 | In Progress |
| Technical spec doc for mobile redesign | Julie Martin | Dec 18 | Not Started |
| Refactor codebase for Q2 reporting feature | Marc Dubois (delegated to Dev Team) | Jan 31 | Not Started |
| Create beta program invite email + landing page | Claire Petit | Dec 20 | Not Started |
| Identify 15 beta candidates from enterprise accounts | Kevin Blanc | Dec 16 | Not Started |
| Update public roadmap on website | Claire Petit | Dec 22 | Not Started |
| Schedule Q1 sprint planning with Eng team | Julie Martin | Dec 12 | Not Started |

📊 **DATA &amp; INSIGHTS**

• NPS Survey Results: 450 respondents, 67% of enterprise customers requested advanced reporting (vs 38% requesting mobile improvements across all segments)

• Churn Analysis: Mobile-only users show 23% higher churn rate (18% vs 14% for desktop users). Primary reason cited: &quot;Difficult to use on phone&quot; (42% of 1-star reviews)

• Engineering Velocity: Q4 average = 32 story points/sprint. Q1 estimated capacity = 28 points/sprint due to team member absence

• Beta Program Precedent: Q3 2025 beta had 85% participation rate, surfaced 12 critical bugs pre-launch, reduced post-launch support tickets by 34%

🔄 **FOLLOW-UP**

• **Next Meeting**: Sprint Planning Session - December 12, 10:00 AM (Julie to send calendar invite)
• **Checkpoint**: Beta Program Kickoff Review - January 5, 2:00 PM (Claire to present beta performance metrics)
• **Monthly Cadence**: Product Roadmap Review every 1st Monday of month, 2-4 PM

**Meeting Adjourned**: 4:05 PM
**Minutes Prepared By**: Sarah Chen
**Distributed**: December 8, 2025, 5:30 PM