{
  "slug": "mttr-impact-calculator",
  "title": "MTTR Impact Calculator",
  "heading": "MTTR Reduction Impact Calculator",
  "category": "other",
  "url": "https://www.revenuelab.fyi/toolbox/mttr-impact-calculator",
  "summary": "Quantify what cutting your mean time to recovery is actually worth.",
  "description": "Mean time to recovery (MTTR) is the average time from an incident starting to service being fully restored, and it's one of the four DORA metrics correlated with high-performing engineering teams. This calculator takes your current MTTR and incident frequency, applies your incident cost per minute, and computes both current annual incident cost and the savings from a target MTTR reduction, so investment in observability, runbooks, or automated rollback tooling can be justified with a real number instead of a vague 'faster is better' argument. It splits MTTR conceptually into detection time (how long until you know something's wrong) and repair time (how long to actually fix it once known) because they respond to different investments — better monitoring and alerting cuts detection time, while better runbooks, feature flags, and automated rollback cut repair time, and most teams have far more slack in detection time than they realize.",
  "formula": "Annual incident cost = incidents/year × MTTR (minutes) × cost per minute; savings = incidents/year × (current MTTR − target MTTR) × cost per minute.",
  "dateModified": "2026-09-30",
  "run_url": "https://www.revenuelab.fyi/api/public/calc?tool=mttr-impact-calculator",
  "inputs": [
    {
      "id": "incidentsPerYear",
      "label": "Incidents per year",
      "kind": "number",
      "hint": null,
      "default": 24,
      "unit": null,
      "min": 0,
      "max": null
    },
    {
      "id": "currentMttr",
      "label": "Current MTTR",
      "kind": "number",
      "hint": null,
      "default": 55,
      "unit": "minutes",
      "min": 1,
      "max": null
    },
    {
      "id": "targetMttr",
      "label": "Target MTTR",
      "kind": "number",
      "hint": null,
      "default": 20,
      "unit": "minutes",
      "min": 1,
      "max": null
    },
    {
      "id": "costPerMinute",
      "label": "Cost per minute of downtime",
      "kind": "number",
      "hint": null,
      "default": 1800,
      "unit": "$",
      "min": 0,
      "max": null
    }
  ],
  "outputs": [
    {
      "id": "savings",
      "label": "Annual savings from MTTR reduction",
      "format": "currency",
      "hint": null,
      "primary": true
    },
    {
      "id": "reductionPct",
      "label": "MTTR reduction",
      "format": "percent",
      "hint": null,
      "primary": false
    },
    {
      "id": "currentAnnualCost",
      "label": "Current annual incident cost",
      "format": "currency",
      "hint": null,
      "primary": false
    },
    {
      "id": "targetAnnualCost",
      "label": "Projected annual incident cost",
      "format": "currency",
      "hint": null,
      "primary": false
    }
  ],
  "worked_example": {
    "inputs": [
      "Incidents per year: 24",
      "Current MTTR: 55 minutes",
      "Target MTTR: 20 minutes",
      "Cost per minute of downtime: 1800 $"
    ],
    "outputs": [
      "Annual savings from MTTR reduction: $1,512,000",
      "MTTR reduction: 63.6%",
      "Current annual incident cost: $2,376,000",
      "Projected annual incident cost: $864,000"
    ]
  },
  "how_to": {
    "title": "How to use this",
    "steps": [
      "Enter incidents per year.",
      "Enter current mttr (minutes).",
      "Enter target mttr (minutes).",
      "Enter cost per minute of downtime ($).",
      "Read your annual savings from mttr reduction on the right — it updates as you type.",
      "Hit Share to keep the scenario or send it to someone."
    ]
  },
  "scenarios": [
    {
      "name": "Conservative",
      "description": "Lower-end numbers — what if things land soft?",
      "values": {
        "incidentsPerYear": 14,
        "currentMttr": 33,
        "targetMttr": 12,
        "costPerMinute": 1100
      }
    },
    {
      "name": "Typical",
      "description": "Defaults — the most common real-world setup.",
      "values": {
        "incidentsPerYear": 24,
        "currentMttr": 55,
        "targetMttr": 20,
        "costPerMinute": 1800
      }
    },
    {
      "name": "Ambitious",
      "description": "Higher-end numbers — what if things really pop?",
      "values": {
        "incidentsPerYear": 38,
        "currentMttr": 88,
        "targetMttr": 32,
        "costPerMinute": 2900
      }
    }
  ],
  "limitations": [
    "Estimates assume standard, average conditions — local rules, pricing, and materials vary.",
    "Results are rounded for readability; add a buffer before ordering, booking, or committing.",
    "Double-check anything with a real cost attached against a local quote."
  ],
  "faq": [
    {
      "q": "What counts as good MTTR for the industry?",
      "a": "DORA's State of DevOps research bands elite performers at under 1 hour MTTR, high performers under 1 day, medium performers under 1 week, and low performers over 1 week or even 1 month. The bands matter more than the exact minute count — moving from 'medium' to 'high' typically has a bigger business impact than shaving a few minutes off an already-fast MTTR."
    },
    {
      "q": "Where should I invest first: detection or repair time?",
      "a": "Time your last 10-15 incidents from actual failure onset to first alert versus first alert to resolution — most teams find detection eats 30-50% of MTTR and is cheaper to fix (better alerting thresholds, synthetic monitoring) than repair time, which often requires structural changes like feature flags or one-click rollback pipelines. Fix whichever phase is the larger share first."
    },
    {
      "q": "Does incident count go down as MTTR goes down?",
      "a": "Not directly — MTTR and incident frequency are different metrics driven by different causes (MTTR by response tooling and process, frequency by code quality and change failure rate). But teams that invest in fast, safe rollback mechanisms to cut MTTR often see frequency drop too, because the same tooling that speeds recovery also makes it cheaper to catch and revert bad changes before they escalate."
    }
  ],
  "related": [
    "https://www.revenuelab.fyi/toolbox/incident-cost-per-minute",
    "https://www.revenuelab.fyi/toolbox/error-budget-burn-rate",
    "https://www.revenuelab.fyi/toolbox/oncall-load-calculator"
  ],
  "license": "CC-BY-4.0",
  "citation": "RevenueLab — MTTR Impact Calculator (https://www.revenuelab.fyi/toolbox/mttr-impact-calculator)"
}