Kostenlos registrieren

Run a project pre-mortem

Autor: AILesson7 Min. EinrichtungszeitGetestet mit:ChatGPTGeprüft am: 2026-08-28

Schnelle Antwort

Imagine a failed outcome to surface plausible causes, weak signals, tests, and preventive actions. Angeben: Project and failure date, Evidence and assumptions, Participants and action authority. Erwartetes Ergebnis: A prioritized failure scenario map with evidence, indicators, owners, and immediate experiments.

1

Kontext hinzufügen

Dein Text bleibt in diesem Browser. AILesson Prompts sendet ihn nicht an ein Modell oder einen Server.

2

Dein Prompt

Nicht ausgefüllte Felder bleiben als Platzhalter sichtbar, sodass du den Prompt weiterhin kopieren und bearbeiten kannst.

Run a project pre-mortem using the supplied context.

Project, users, plan, target, and concrete failure definition:
[project]

Constraints, dependencies, incidents, estimates, dissent, and unknowns:
[assumptions]

Participant perspectives, authority, mitigation capacity, and review timing:
[participants]

Assume the project has failed at the stated future point, then generate distinct and plausible explanations across user value, scope, delivery, quality, operations, people, vendor, governance, security, accessibility, data, and external context only where relevant. Separate evidence-backed concerns from hypotheses. Avoid generic catastrophes, blame, and hindsight certainty. Cluster causes into causal chains, identify earliest observable indicators, and rank by plausibility and damage with stated rationale—not invented precision. For the top scenarios provide a cheap test, prevention, contingency trigger, response, explicit owner or Unassigned, and decision deadline. Include contrarian scenarios and strengths that reduce risk.
Im Playground ausprobieren
Standardmäßig privatDer Prompt wird lokal in deinem Browser zusammengestellt. Gib keine vertraulichen Informationen in einen KI-Dienst ein, es sei denn, deine Organisation erlaubt dies.

Von der Eingabe zum Ergebnis

Ein ausgearbeitetes Beispiel

Sieh dir an, wie konkreter Kontext dieses Rezept in ein nutzbares Ergebnis verwandelt.

Tatsächliche Eingabe

Project and failure date
In March, a regional charity launches an online volunteer scheduling portal for 600 volunteers and 40 coordinators. Failure at 30 June means coordinators still maintain parallel spreadsheets, more than 10% of scheduled shifts are disputed, or fewer than 50% of active volunteers use the portal monthly. Pilot begins with two teams in February.
Evidence and assumptions
Many volunteers use phones; 18% of current records lack a unique email. Coordinators use different shift naming. The vendor says CSV import is supported but has not tested our file. Training budget covers two live sessions. One coordinator worries volunteers will not see cancellation notices. Authentication uses email links. No accessibility test, support rota, or spreadsheet retirement rule exists yet.
Participants and action authority
Workshop includes volunteer coordinator, volunteer representative, operations manager with launch authority, data officer, communications lead, and vendor specialist. Two staff-weeks remain for mitigation. Decisions reviewed next Tuesday.

Beispielausgabe

Failure story A—fragmented identity and import: 18% without unique email plus untested CSV import causes duplicate/missing accounts; volunteers cannot authenticate; coordinators retain spreadsheets; disputes rise. Evidence-backed. Earliest indicators: import exception rate, duplicate accounts, failed sign-ins. Cheap test: import a de-identified representative file and attempt phone sign-in with records missing/duplicating email. Prevention: define identity remediation and reconcile counts before pilot. Owner: Data officer for test; identity-policy owner Unassigned. Decision by next Tuesday.

B—inconsistent shift definitions: different names map incorrectly, creating disputed schedules and parallel records. Evidence-backed. Test a shared taxonomy against two pilot teams and reconcile every imported shift. C—cancellations fail operationally: email-link users may miss notices; no support rota or acknowledged-notice rule. Concern is explicit, outcome mechanism partly hypothetical. Test delivery/opening plus five volunteer task walkthroughs; define urgent fallback and owner. D—adoption appears acceptable while coordinators maintain shadow sheets; contrarian governance failure. Indicator: edits continue after cutover. Define retirement gate and exception log before launch.

Other hypotheses: mobile accessibility prevents task completion; two sessions miss shift workers; vendor defects outlast two staff-weeks. Strengths: staged two-team pilot, named launch authority, volunteer perspective, and measurable failure thresholds. Prioritize A/B before pilot because they share a data foundation but require separate acceptance checks.

Warum das funktioniert

  1. 1

    Prospective hindsight makes teams name failure causes that optimistic planning often suppresses.

  2. 2

    Indicators and cheap tests convert imagined failure into evidence that can change the plan.

Ergebnis prüfen

  • Are scenarios specific to this project and linked to supplied evidence or labeled hypotheses?

  • Do top scenarios have early indicators, cheap tests, triggers, and actionable responses?

  • Does the output avoid blame, false probability, and duplicate wording of the same causal chain?

Sicher nutzen

Häufig gestellte Fragen

Praktische Antworten dazu, wann du dieses Rezept verwenden solltest, was du bereitstellen solltest und wo menschliche Prüfung weiterhin wichtig ist.

What should I prepare before using “Run a project pre-mortem”?

For “Run a project pre-mortem,” prepare Project and failure date, Evidence and assumptions, and Participants and action authority. 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 “Run a project pre-mortem” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A prioritized failure scenario map with evidence, indicators, owners, and immediate 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 “Run a project pre-mortem”?

The published test record for “Run a project pre-mortem” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Weitere Möglichkeiten zum Entdecken

Wo dieses Rezept hineinpasst

Text-PromptsProjektmanagementFür Führungskräfte

Bring die Arbeit voran

AILesson · Empfohlene Kurse

Dein nächster Schritt: KI einsetzen

Vom Verstehen von KI zum Erledigen von Aufgaben. Übe Prompting, das Überprüfen und das Verbessern von Ergebnissen in interaktiven Lektionen für Arbeit und Alltag.

Alle Kurse entdecken
Titelbild von KI für Einsteiger

15 interaktive Lektionen

KI für Einsteiger

Beginne ein nützliches KI-Gespräch, verbessere die Antwort, prüfe das Wesentliche und erkenne, wann du selbst als Nächstes handeln musst.

Diesen Kurs entdecken
Titelbild von Grundlagen von ChatGPT

10 interaktive Lektionen

Grundlagen von ChatGPT

Lerne ChatGPT anhand von drei praktischen Abläufen kennen: Schließe einen ersten Chat ab, arbeite mit einer Datei und übernimm danach mit Projects einen geprüften Plan in einen neuen Chat.

Diesen Kurs entdecken
Titelbild von Wie generative KI funktioniert

7 interaktive Lektionen

Wie generative KI funktioniert

Verstehe, wie gängige KI-Chats Sprachmuster lernen, Nachrichten aus dem aktuellen Gespräch nutzen, Antworten erzeugen und Quellen sowie Werkzeuge einbinden.

Diesen Kurs entdecken