Skip to main content

Postmortem Action Prioritizer

Prioritize incident postmortem action items using impact vs effort analysis. Enter values for instant results with step-by-step formulas.

Share this calculator

Worked Examples

Example 1: Database Outage

Problem: 2-hour database failure. 8,000 customers affected, $50,000 revenue lost. 6 action items identified.

Solution: Quick wins: Add query monitoring (impact 7, effort 3). Major: Implement automated failover (impact 10, effort 13). Prioritize monitoring first for fast win.

Result: 6 actions prioritized | 2 quick wins | 1 major project | 45 dev-days total

Example 2: API Rate Limit Incident

Problem: 30-min API unavailability due to rate limit. 500 users affected, $2,000 impact. 4 actions.

Solution: Top priority: Rate limit monitoring (impact 9, effort 2, 3 days). Also: Better error messages (impact 6, effort 3). Skip expensive API redesign (impact 5, effort 20).

Result: 4 actions | Focus on monitoring | Skip low-ROI redesign | 15 dev-days

Example 3: Deployment Gone Wrong

Problem: Bad deploy took down site for 45 min. 12,000 users affected. 8 proposed actions.

Solution: Too many actions (8). Consolidate to: Enhanced deployment gates (impact 9, effort 5), Rollback automation (impact 10, effort 8), Canary deployment (impact 8, effort 13).

Result: 8 → 3 focused actions | Top 3 address root causes | 26 dev-days

Frequently Asked Questions

What is a postmortem?

A postmortem (or post-incident review) is a blameless analysis conducted after an outage or incident. It documents what happened, why, and what actions will prevent recurrence. Blameless culture enables honest learning.

How do I prioritize postmortem action items?

Use impact (how much does this reduce future risk?) vs. effort (how hard to implement?). High impact, low effort are quick wins. High impact, high effort need planning. Low impact items may not be worth doing.

What's a reasonable number of action items?

3-7 actionable items per postmortem. More than 10 suggests too little prioritization—most won't get done. Focus on high-impact items that actually get implemented.

Should every postmortem have action items?

Not necessarily. If existing defenses worked or the incident was truly unforeseeable, acknowledge it. Manufacturing action items creates busy work. Sometimes the lesson is 'our systems worked as designed.'

How do I track postmortem action completion?

Assign owners, set due dates, track in project management tools (Jira, Linear, etc.). Review quarterly—incomplete actions from old postmortems indicate follow-through problems.

What makes a good postmortem action item?

Specific (not vague), measurable (can verify completion), achievable (realistic scope), relevant (actually prevents recurrence), and time-bound (has deadline). Avoid 'improve monitoring'—specify what metrics.

Background & Theory

The Outage Postmortem Action Item Prioritizer applies the following established principles and formulas. Break-even analysis identifies the sales volume at which total revenue equals total costs, producing neither profit nor loss. The formula divides total fixed costs by the contribution margin per unit, where contribution margin equals selling price minus variable cost per unit. If a software product has $50,000 in monthly fixed costs and each licence generates $20 above its variable cost, break-even requires 2,500 unit sales per month. Above that threshold, each additional unit contributes directly to profit. Gross margin expresses the percentage of revenue remaining after direct cost of goods sold: gross margin equals revenue minus COGS, divided by revenue. A SaaS company with 80 percent gross margins retains $0.80 of every revenue dollar to cover operating expenses, while a manufacturer with 30 percent gross margins faces much tighter operating leverage. Customer acquisition cost (CAC) divides total sales and marketing expenditure in a period by the number of new customers acquired in that same period. Customer lifetime value (LTV) estimates the total profit attributable to a customer relationship. The standard formula multiplies average revenue per user (ARPU) by gross margin and divides by the monthly churn rate. A business with $50 ARPU, 75 percent gross margin, and 2 percent monthly churn has an LTV of $1,875. The LTV:CAC ratio benchmarks unit economics health; a ratio above 3:1 is generally considered sustainable, while ratios below 1:1 indicate the business is acquiring customers at a loss. Burn rate measures monthly cash expenditure net of revenue. Cash runway equals current cash reserves divided by net monthly burn. A company with $1.2 million in the bank burning $100,000 per month has twelve months of runway. The Rule of 40 is a benchmark for SaaS health: the sum of annual revenue growth rate (as a percentage) and profit margin (as a percentage) should equal or exceed 40. High-growth companies burning cash can still pass this rule if their growth rate compensates.

History

The history behind the Outage Postmortem Action Item Prioritizer traces back through the following developments. Early economic thought centred on mercantilism, the 16th and 17th century doctrine that national wealth derived from accumulating precious metals through export surpluses and colonial extraction. Adam Smith's "Wealth of Nations" in 1776 dismantled this framework, arguing that genuine prosperity arose from specialisation, division of labour, and freely operating markets. David Ricardo extended Smith's work with the theory of comparative advantage in 1817, demonstrating mathematically that mutually beneficial trade was possible even when one country was less productive in every industry. Alfred Marshall's "Principles of Economics" published in 1890 provided the modern framework of supply and demand curves, consumer surplus, price elasticity, and marginal analysis, establishing neoclassical economics as the dominant academic paradigm for decades. The Great Depression exposed the limits of laissez-faire assumptions, and John Maynard Keynes's "General Theory of Employment, Interest and Money" in 1936 argued that private-sector aggregate demand failures required countercyclical government fiscal intervention to restore full employment, shifting the policy consensus toward active macroeconomic management. The post-World War II decades constructed mixed-economy models combining market allocation with expanded welfare states and Keynesian demand management. Milton Friedman and the Chicago School challenged this consensus from the 1960s onward, championing monetarism and arguing that stable money supply growth was superior to discretionary fiscal policy. Their influence shaped the deregulatory and privatisation policies of the Reagan and Thatcher eras in the 1980s. Behavioural economics emerged through the work of Daniel Kahneman and Amos Tversky in the 1970s and Richard Thaler in the 1980s, using psychology to demonstrate that real human decision-making deviates systematically from rational-actor models through heuristics and biases. The rise of the internet and mobile platforms in the 2000s and 2010s created a new category of platform economics, where network effects, near-zero marginal cost of digital goods, and two-sided market dynamics generated winner-take-most competitive outcomes requiring new analytical frameworks for business valuation.

References