Reference eligibility: eligible — Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.
leadership/strategy / comm-20
Atlassian project premortem
Participants anticipate project threats and enabling conditions, then convert selected concerns into commitments.
documented-procedure · conventional-workflow · Source account, not a validated implementation
What goes in
- Project context
- Participant concerns
- Past lessons
What comes out
- Prioritized risks
- Mitigation actions
Documented sequence
Order described in the source account; not a sequence between pattern families.
- Prepare project-specific prompts
- Silently generate possible failures and successes
- Group similar contributions
- Vote on threats
- Vote on success factors
- Discuss leading topics and mitigations
- Assign owners and dates
- Save and recap commitments
Checks described
- Quantify time or cost where available
- Every commitment gets an owner and deadline
What changes with context
- Small-group workshop before or during a project
- Prompts can be customized
- Remote and in-person variants
Shared patterns · provisional interpretation
-
Anticipate risks and plan mitigations
Proposed activity, dependencies, or disclosed risk → identified hazards and specific mitigation plans
-
Coordinate commitments to closure
An objective involving people or teams → accountable next actions, handoffs, tracking, and agreed closure
Fit: mapped. Exploratory analyst coding of collected source summaries; not independently tested
Could this transfer?
Hypothetical: a publishing team could anticipate why an issue might miss its release date and assign early safeguards.
Limit: Voting reflects the group's knowledge, not calibrated risk probability; rare severe risks can be outvoted.
Evidence limits and unknowns
Summary through context_constraints paraphrase source-backed mechanics. structural_motifs, candidate_midlevel_pattern, transfer_example_explicitly_hypothetical and transfer_limit are analyst interpretations, not tested findings.
- Mitigation follow-through
- Measured predictive accuracy
Source eligibility and effectiveness
Allowed use: process reference with explicit limits . Source eligibility is not proof of effectiveness, safety or transferability.
Review attribution: AI-assisted source review · 2026-10-18T03:26:44.526806+00:00.
- Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.
- No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.
- Mitigation follow-through
- Measured predictive accuracy
- Voting reflects the group's knowledge, not calibrated risk probability; rare severe risks can be outvoted.
Source and dates
Pre-mortem project management strategy ↗ · Official facilitation procedure with illustrated team examples
- Published
- Unknown
- Updated
- Unknown
- Checked (UTC)
- 2026-10-18T03:01:00Z
Original premortem play reopened. No publication/update label established; timing estimates refer to the workshop, not publication.
not stated in retrieved page · Date evidence ↗
Try a bounded adaptation
This generated starter is untested. It is not the source author’s prompt or a reviewed Commons skill.