The decision question
The relevant question is: which prioritised business service must return by when, at what minimum capability—and which decisions are required to get there?
This shifts the focus from individual backup jobs to the complete chain of people, identities, data, platforms, networks, suppliers and operational decisions.
The recovery chain
Recovery is only as dependable as its weakest critical dependency. A technically restored system may remain unusable if identities are unavailable, data states are unclear or an external service is down.
- Critical service and accepted minimum capability
- Sequence, data consistency and technical dependencies
- Decision and communication paths
- Suppliers, access and alternative operating procedures
The common wrong decision
Recovery objectives are derived from technical habit rather than tolerable business impact. The numbers may be precise but not decision-relevant. A dependable mandate starts with a shared definition of service, minimum capability, time and accepted data loss.
Executive checklist
A useful recovery model answers:
- Which services take priority, and why?
- What minimum capability is acceptable?
- Which dependency can block recovery?
- Who decides trade-offs and deviations?
- Which exercise demonstrates the next maturity step?