Project Failure Pre-Mortem Analyst

The problem

Projects often appear healthy until hidden dependencies, overloaded people, unrealistic timelines, weak assumptions, or delayed bad news finally become visible. By then, correction is expensive.

What it does

• Assumes the project has failed and works backward to identify the most plausible failure paths.
• Surfaces fragile assumptions, single points of failure, hidden dependencies, and coordination risks.
• Traces where project stability depends on one person carrying excessive work or responsibility.
• Checks timelines, budgets, capacity, external dependencies, and misleading success metrics.
• Identifies early warning signals before the final failure becomes visible.
• Defines correction actions, escalation thresholds, and conditions where the project should be reduced, redesigned, paused, or stopped.

Why use this skill

Generic risk analysis can easily become a long list of everything that could possibly go wrong. This skill focuses instead on the few failure modes that are plausible, consequential, difficult to detect early, and poorly handled by the current plan.

Use cases

• Pressure-testing a product launch before committing major resources.
• Auditing a campaign, implementation, event, software project, or operational change.
• Finding hidden workload and single points of failure inside a team.
• Identifying warning signals and escalation thresholds before a deadline is missed.
• Deciding what conditions should trigger scope reduction, delay, redesign, or cancellation.

Known limitations

A pre-mortem cannot predict every failure. Its quality depends on the project information provided. Technical, legal, safety, financial, or regulated risks may require specialist review in addition to this analysis.