Resilience is a central concept in system theory that deals with the adaptability and robustness of systems against external influences. Organizations that promote resilience are better prepared to cope with challenges and achieve their goals successfully.
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 you need to understand to reason about a domain.
Resilience is a system’s ability to absorb disruption, preserve essential function, and adapt or recover afterward.
The approach emerged at the intersection of ecology, psychology, and engineering. Operations and systems practice extended it to organizations and digital services to address uncertainty and disruption over time.
A resilient system has several responses to disruption: it limits damage, keeps core service running, and learns from the event. Redundancy is only one possible means.
Wie gut ein System einen Stoß verkraftet, ohne seine Kernfunktion zu verlieren.
Die Rückkehr zu einem tragfähigen Betriebszustand nach einer Störung.
Eine dauerhafte Veränderung als Reaktion auf neue Bedingungen.
Resilience guides architecture, continuity planning, and exercises toward the consequences of real disruptions. It does not replace reliability or security analysis and must not normalize avoidable failures.
Where this building block is located in the topic model.
No structure path available.
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.