S'inscrire gratuitement

Create a project retrospective meeting agenda

Auteur: AILesson8 min de préparationRévisé: 2026-08-29

Réponse rapide

Review observable outcomes, process conditions, and improvement experiments without assigning blame. Fournir: Project baseline and outcomes, Participants and context, Retrospective scope. Résultat attendu: A psychologically safer retrospective agenda with evidence prompts and bounded experiments.

1

Ajouter votre contexte

Votre texte reste dans ce navigateur. AILesson Prompts ne l’envoie ni à un modèle ni à un serveur.

2

Votre prompt

Les champs non remplis restent visibles sous forme d’espaces réservés, afin que vous puissiez quand même copier et modifier le prompt.

Create a project retrospective meeting agenda grounded in observable evidence.

Objectives, plan, actual outcomes, timeline, incidents, changes, and evidence:
[baseline]

Participants, power differences, confidentiality, conflict, accessibility, and facilitator:
[team]

Duration, scope, data, authority, decision limits, and follow-up:
[scope]

Separate outcomes, observations, interpretations, and proposed causes. Review system conditions and decision points without inferring intent or turning the meeting into individual performance evaluation. Offer equal input routes and a way to raise sensitive issues outside the group. Prioritize no more improvement experiments than the supplied capacity supports; each needs hypothesis, owner only if confirmed, evidence, duration, and review trigger. Return pre-work, timed agenda, evidence questions, facilitation safeguards, experiment template, parking lot, and follow-up review.
Essayer dans le Playground
Privé par défautL’assemblage du prompt se fait localement dans votre navigateur. Évitez de placer des informations confidentielles dans un service d’IA, sauf si votre organisation l’autorise.

De l'entrée au résultat

Un exemple détaillé

Voyez comment un contexte concret transforme cette recette en résultat utilisable.

Entrée réelle

Project baseline and outcomes
Website migration planned 6 weeks, completed in 8. Forty pages moved; five had broken links at launch, fixed next day. Plan assumed content approval by week 2; 11 pages arrived in week 4. Two unplanned accessibility fixes added 3 days. No evidence identifying a single cause of the full delay.
Participants and context
Product, content, engineering and accessibility representatives; engineering manager attends with two engineers. Product Ops facilitates. Anonymous pre-input available. Individual performance is out of scope.
Retrospective scope
60 minutes. Data: plan, issue log, approval dates, launch checks. Team can approve at most two process experiments for next release. Sensitive staffing issues route to managers separately. Review experiments after four weeks.

Exemple de sortie

Pre-work: timeline with planned/actual dates; issue log; approval dates; launch-check evidence. Participants label each note Observation, Interpretation, or Proposal; anonymous route remains open.

Agenda (60 minutes) 0–6 access, confidentiality, no-blame and no-performance boundary. 6–14 restate objective and recorded outcomes: 40 pages, eight weeks, five launch link issues fixed next day. 14–26 timeline review: content approvals, accessibility additions, dependencies. Ask 'What changed, when, and according to which record?' Do not ask who caused the delay. 26–36 patterns that helped or hindered; separate evidence from hypotheses. 36–46 generate process experiments silently first, then round-robin; staffing concerns route outside. 46–54 select no more than two using supplied authority and capacity. 54–60 confirm experiment record and four-week review.

Experiment template: hypothesis; specific process change; scope; confirmed owner; start/end; observable evidence; risks; stop/review trigger. Candidate experiment, not pre-approved: require content approval-status check at the end of week 1 and escalate pages lacking an approver. Evidence needed: whether this would have exposed the 11 late pages earlier.

Pourquoi cela fonctionne

  1. 1

    Evidence-status separation prevents confident causal stories from replacing what the project actually recorded.

  2. 2

    Bounded experiments convert learning into testable change without overloading the team.

Vérifier le résultat

  • Are observations separated from interpretations and causal hypotheses?

  • Does the agenda avoid individual performance judgment and motive inference?

  • Are experiments limited, owned only when confirmed, and reviewable?

Utilisez-la en toute confiance

Questions fréquentes

Des réponses pratiques sur le bon moment pour utiliser cette recette, ce qu’il faut fournir et les cas où une vérification humaine reste nécessaire.

What should I prepare before using “Create a project retrospective meeting agenda”?

For “Create a project retrospective meeting agenda,” prepare Project baseline and outcomes, Participants and context, and Retrospective scope. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Create a project retrospective meeting agenda” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A psychologically safer retrospective agenda with evidence prompts and bounded experiments—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Create a project retrospective meeting agenda”?

No model run is recorded for “Create a project retrospective meeting agenda” as of 2026-08-29. Treat it as a model-portable template rather than a compatibility claim. Run the worked example first, keep every constraint visible, and compare the output with the result checks before using it on real material.

Plus de façons d'explorer

Où se situe cette recette

Prompts texteRéunions et collaborationOrdres du jour de réunionRetours et relectureGestion de projetPour les managers

Faites avancer votre travail

AILesson · Cours recommandés

Votre prochaine étape : mettez l’IA à contribution

Passez de la compréhension de l'IA à l'action. Entraînez-vous à formuler des requêtes, à évaluer et à améliorer les résultats grâce à des leçons interactives pour le travail et la vie quotidienne.

Découvrir tous les cours
Image de couverture de L’IA pour débutants

15 leçons interactives

L’IA pour débutants

Lancez une conversation utile avec une IA, améliorez sa réponse, vérifiez l’essentiel et sachez quand c’est à vous d’agir.

Découvrir ce cours
Image de couverture de Les bases de ChatGPT

10 leçons interactives

Les bases de ChatGPT

Découvrez ChatGPT à travers trois flux de travail pratiques : mener une première conversation, travailler à partir d’un fichier, puis utiliser Projects pour réutiliser un plan vérifié dans une nouvelle conversation.

Découvrir ce cours
Image de couverture de Comment fonctionne l’IA générative

7 leçons interactives

Comment fonctionne l’IA générative

Comprenez comment les systèmes courants de chat IA apprennent des structures linguistiques, utilisent les messages actuels, construisent leurs réponses et intègrent des sources et des outils.

Découvrir ce cours