Cadastre-se grátis

Run a project pre-mortem

Autor: AILesson7 min de configuraçãoTestado com:ChatGPTRevisado em: 2026-08-28

Resposta rápida

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

1

Adicione seu contexto

Seu texto permanece neste navegador. O AILesson Prompts não o envia para um modelo ou servidor.

2

Seu prompt

Campos não preenchidos permanecem visíveis como marcadores de posição, para que você ainda possa copiar e editar o prompt

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.
Experimente no Playground
Privado por padrãoA montagem do prompt acontece localmente no seu navegador. Evite colocar informações confidenciais em qualquer serviço de IA, a menos que sua organização permita.

Da entrada ao resultado

Um exemplo prático

Veja como um contexto concreto transforma esta receita em um resultado útil

Entrada real

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.

Exemplo de saída

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.

Por que isso funciona

  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.

Verifique o resultado

  • 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?

Use com confiança

Perguntas frequentes

Respostas práticas sobre quando usar esta receita, o que fornecer e onde a revisão humana ainda é importante

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.

Mais maneiras de explorar

Onde esta receita se encaixa

Prompts de textoGestão de projetosPara gestores

Mantenha o trabalho em andamento

AILesson · Cursos recomendados

Seu próximo passo: use a IA na prática

Passe de entender a IA para fazer as coisas acontecerem. Pratique como criar prompts, revisar e melhorar resultados por meio de lições interativas para o trabalho e o dia a dia.

Explore todos os cursos
Capa de IA para iniciantes

15 lições interativas

IA para iniciantes

Inicie uma conversa útil com IA, melhore a resposta, confira o que importa e saiba quando o próximo passo é seu.

Explore este curso
Capa de Fundamentos do ChatGPT

10 lições interativas

Fundamentos do ChatGPT

Aprenda a usar o ChatGPT por meio de três fluxos de trabalho práticos: conclua uma primeira conversa, trabalhe a partir de um arquivo e use Projects para levar um plano verificado a uma nova conversa.

Explore este curso
Capa de Como a IA generativa funciona

7 lições interativas

Como a IA generativa funciona

Entenda como chats comuns de IA aprendem padrões da linguagem, usam mensagens atuais, criam respostas e incorporam fontes e ferramentas.

Explore este curso