Resilience Engineering is a systems-focused discipline that helps organizations design, operate and evolve systems capable of sustaining acceptable levels of service under varying conditions. It emphasizes anticipating variability, monitoring indicators, enabling adaptive responses through organizational practices, redundancy and institutionalizing post-inci…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Resilience engineering designs systems and organizations to keep functioning, adapt, and improve under disruption.
The approach grew from human-factors and safety research, including work by Erik Hollnagel, David Woods, and colleagues. It applies the view of safety as adaptive capacity to complex sociotechnical systems.
Look beyond isolated errors to everyday operation under changing conditions. Detect signals, anticipate risks, respond while limiting harm, and learn from normal and exceptional work. Redundancy, graceful degradation, recovery, practice, and blameless learning are means within this loop.
Potential stresses and changes are identified and prepared for before they occur.
People and systems remain capable of action during unknown or changing disruptions.
Evidence from operations, exercises, and incidents improves the system and organization.
Resilience engineering is useful for services where outage, misuse, or overload has significant consequences. It complements reliability measures with organization, working conditions, and adaptation; one redundancy or runbook does not make a system resilient.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.