Stop Mapping Workflows. Start Defining What Must Stay Up.

July 24, 2025

Let’s cut to it: Workflow dependency mapping looks useful — until you realize no one uses it when it matters.

You can chart every input, every output, and every branch of every process. But when something breaks, people don’t follow the map.

They ask:

• “What’s down?”
• “How long can we live without it?”
• “What has to stay running no matter what?”

That’s why smart resilience programs are ditching spaghetti maps and asking a better question: “What’s the minimum acceptable availability for this service over the course of a year?”

What Is Percentage Availability?

It’s not a gut check. It’s not a vague SLA. It’s a clear, numeric threshold:

• “This service must be available 99% of the time annually.”
• “This process can only be down for ~88 hours a year (1%).”
• “This function only needs 80% availability to be considered successful.”

This gives you a tangible, outcome-based requirement for continuity — not just a list of dependencies that might or might not matter in a disruption.

Why Workflow Dependency Mapping Misses the Mark

It’s Static: Processes and systems change constantly. Maps don’t.

It’s Not Prioritized: Everything looks connected, but it doesn’t tell you what’s vital vs. what’s just annoying to lose.

It Doesn’t Translate to Exec Decisions: No executive makes decisions off a diagram. They need to know: “What are we failing to deliver, and how long can we fail before it matters?”

It’s a Maintenance Burden: Who’s updating all those dependencies quarterly? No one. Let’s be real.

Why Percentage Availability Works Better

Aligns With Business Objectives: You’re not asking “What does this connect to?” You’re asking: “How much uptime does this service need to meet customer expectations, compliance, and revenue targets?”

Drives Response Planning: If something has to be up 99.9% of the year, you don’t just plan a recovery — you build failovers, redundancy, rapid response. It tells you where to spend your money.

Simplifies Communication: “This service needs 99% availability” is clearer than “This service depends on 14 other systems, 3 vendors, and 2 manual workarounds.”

It’s Measurable: You can track it. You can report on it. You can prove whether you’re meeting the requirement or not.

How to Implement Percentage Availability

1. Define Service Tiers

Not everything needs 99.9% uptime. Classify services based on business impact:

• Tier 1: Mission-critical (99.9%+)
• Tier 2: Important but not critical (99%)
• Tier 3: Nice-to-have (95% or less)

2. Set Annual Availability Targets

Based on those tiers, set numeric targets. Example: “Customer portal must be available 99.5% of the year (max 43.8 hours downtime).”

3. Build Response Around the Target

If a Tier 1 service goes down, you activate crisis response immediately. If a Tier 3 service goes down, you log it and fix it when you can.

4. Track and Report

Measure actual availability against the target. Report deviations. Adjust strategies if you’re consistently missing thresholds.

Final Thought

Workflow maps look impressive in a presentation. But when something breaks, no one’s pulling up a flowchart.

They’re asking: “What’s down, and how long can we survive without it?”

Percentage availability answers that question. It’s simple. It’s measurable. And it drives the decisions that actually matter when things go wrong.

Stop mapping dependencies. Start defining what must stay up.