Skip to content
How to ThinkIn the Age of AI

Resilient behaviors survive disruption

~11 min read

Core Primitive

Design your habits to be robust enough to withstand common disruptions.

The same disruption, two different outcomes

Two people build nearly identical morning routines over the course of a year. Both wake at six, both journal for twenty minutes, both exercise for forty-five, both review their priorities before the workday begins. Then a disruption arrives — the kind that All behavioral systems face disruption established as inevitable. A parent falls ill. Both fly across the country on short notice to help with care. They will be away from home for two weeks, sleeping in a spare bedroom, operating on someone else's schedule, emotionally depleted, stripped of every environmental cue that normally sustains their routines.

Person A does not journal, exercise, or review priorities for the entire two weeks. She tells herself she will resume when she gets home. When she returns, the restart feels impossibly heavy. Three weeks later she is still "getting back on track," and the routines that took a year to build have evaporated in five weeks. Person B journals for five minutes on her phone in a hospital waiting room. She does a ten-minute bodyweight circuit in the spare bedroom before anyone else is awake. She reviews her priorities in her head during the drive to the hospital. None of these are her normal routines. All of them are recognizably continuous with her normal routines. When she returns home, she slides back into the full versions within two days, because she never fully stopped.

The difference between these two people is not willpower, not discipline, not motivation, not character. It is design. Person A built routines that worked beautifully under ideal conditions and shattered under real ones. Person B built routines that could degrade gracefully — that had built-in fallback modes allowing the behavior to continue in diminished but unbroken form when the normal context disappeared. This lesson is about the design principles that separate the first architecture from the second.

Resilience is a design property

The most consequential shift this lesson asks you to make is from thinking about resilience as a personal quality to thinking about it as a structural property of the behavioral systems you build. When Person A's routines collapsed during the family crisis, the natural interpretation is that she lacked the discipline to maintain them. That interpretation is wrong. She had demonstrated twelve months of discipline. What she lacked was a system designed to operate outside its original parameters.

This distinction matters because it changes where you direct your effort. If resilience is a character trait, the solution is to become tougher, more disciplined, more committed — to white-knuckle through disruptions by sheer force of will. If resilience is a design property, the solution is to engineer your habits differently from the start so that they require less force of will to maintain when conditions deteriorate. The first approach fails reliably, because willpower is precisely the resource that disruptions deplete. The second approach succeeds reliably, because it reduces the willpower requirement at exactly the moment when willpower is least available.

This is not a new idea in other domains. Engineers do not build bridges that require ideal weather to remain standing. They build bridges that withstand storms, earthquakes, heavy loads, and material fatigue — not by making the bridge infinitely strong, but by designing structural properties like redundancy, flexibility, and graceful degradation into the system from the beginning. The bridge does not need to be brave. It needs to be well-designed. Your behavioral systems are no different.

The fragility spectrum

Nassim Nicholas Taleb's framework from Antifragile (2012) provides the most useful vocabulary for thinking about where your habits sit on the resilience spectrum. Taleb identified three categories: fragile, robust, and antifragile. A fragile system breaks under stress. A robust system resists stress and remains unchanged. An antifragile system actually improves under stress — it uses the disruption as information or stimulus for growth.

Most people's habits are fragile without knowing it. They function under normal conditions and collapse under abnormal ones. The collapse is not dramatic — it is not a single catastrophic failure. It is a quiet cessation. The person simply stops doing the behavior when the context changes, intending to resume later, and "later" becomes "eventually" becomes "never." The fragility was invisible during normal operations because the system was never tested. It only became apparent when the disruption arrived.

Robust habits, by contrast, are designed to absorb disruption without breaking. They have fewer contextual dependencies, lower activation energy, and built-in fallback modes. A robust exercise habit does not depend on a specific gym, a specific time, or specific equipment. It can execute in a hotel room, in a park, in a hospital waiting room — anywhere a human body exists. The behavior looks different in different contexts, but its identity and continuity are preserved.

Antifragile habits go further: they use disruptions as opportunities to strengthen the system. A person whose meditation practice deepens during a crisis because the emotional intensity provides richer material has an antifragile habit. Antifragility is the ultimate goal, but it is not where you start. You start by eliminating fragility. You move through robustness. Antifragility emerges from a system that has survived enough disruptions to learn from them.

The critical question Taleb forces you to ask is not "How strong is this habit?" but "What happens to this habit when something unexpected occurs?" A glass is strong enough to hold water every day for decades. It is still fragile. Your habit that has run without interruption for six months may be equally fragile — you simply have not dropped it yet.

Resilience engineering applied to behavior

Erik Hollnagel's work on resilience engineering, originally developed for safety-critical systems like aviation and healthcare, translates directly to behavioral design. Traditional safety thinking focuses on preventing failures — identifying what can go wrong and building barriers against it. Resilience engineering takes a fundamentally different approach: it assumes that disruptions are inevitable and asks how the system can continue to function acceptably when they occur (Hollnagel, 2011).

Hollnagel identified four core capacities of a resilient system that map cleanly onto behavioral design. Anticipation means designing your habits with disruption scenarios in mind before any disruption occurs — building fallback modes now, while conditions are calm. Monitoring means paying attention to the early signals that a disruption is approaching and activating contingency plans before the full disruption hits. Response means having a practiced protocol for switching from normal-mode habits to disrupted-mode habits smoothly, without decision-making overhead under stress. Learning means debriefing after each disruption to identify which elements held up, which broke, and how to redesign the broken elements for next time.

The insight most people miss is that resilience is not about the acute response to disruption. It is about the steady-state design that makes the acute response possible. A well-designed system responds well because it was built to. A poorly designed system responds poorly because it was never built for anything other than normal operations.

Four design principles for resilient behaviors

The research from Taleb, Hollnagel, BJ Fogg, and Wendy Wood converges on four architectural principles that make the difference between habits that survive disruption and habits that do not.

The first principle is context-independence. Wendy Wood's research on habit and automaticity demonstrated that habits are deeply bound to their contexts — the specific locations, times, preceding behaviors, and environmental cues that trigger them (Wood & Neal, 2007). This binding is what makes habits automatic: the context does the triggering, so you do not need to deliberate. But context-dependence is also the primary source of habit fragility. When the context disappears — when you travel, when your schedule changes, when you move to a new home — the trigger disappears with it, and the habit goes dormant. The design solution is to build habits that have a context-dependent primary mode and a context-independent fallback mode. Your primary exercise habit might be triggered by arriving at the gym at 6 a.m. — that is fine, and the automaticity is valuable. But the fallback mode should be triggerable by any context: waking up anywhere, at any time, in any physical space. You practice the fallback occasionally, so that when the primary context vanishes, you do not experience a trigger void.

The second principle is low activation energy. BJ Fogg's Tiny Habits framework (2019) demonstrated that the most reliable predictor of habit survival is not motivation or importance — it is how easy the behavior is to initiate. A habit with high activation energy — one that requires significant preparation, equipment, or psychological ramp-up — is fragile by definition, because disruptions increase the cost of initiation at exactly the moment when your resources for overcoming that cost are depleted. The design solution is to ensure that every important habit has a version with activation energy so low that it is harder to skip than to do. Two minutes of journaling. Five pushups. One paragraph of reading. These are continuity devices — their purpose is to keep the behavioral chain unbroken so that restart cost never accumulates. Fogg's research showed that once the tiny version is initiated, people naturally expand to a larger version most of the time. The tiny habit is a door, not a room.

The third principle is identity-anchoring rather than environment-anchoring. This lesson connects directly to the work you did in Identity-Behavior Alignment on identity-behavior alignment. A habit that is anchored to an environment — "I exercise at Gold's Gym" — fails when the environment is removed. A habit that is anchored to an identity — "I am someone who moves their body daily" — survives environmental change because the identity travels with you. The person who exercises in hotel rooms during business trips is not maintaining an environment-anchored habit under difficult conditions. She is expressing an identity-anchored habit in a new environment. The behavior looks different, but the identity function is identical. Designing for identity-anchoring means that when you build a habit, you explicitly connect it to a self-concept rather than a location. "I write daily" rather than "I write at my desk from 6 to 7 a.m." The desk and the hour are useful defaults, but they are not the load-bearing structure. The identity is.

The fourth principle is modularity rather than monolithicity. A monolithic routine is a single block: if any component fails, the entire routine collapses. A morning routine that must proceed in exact sequence — wake, meditate, journal, exercise, shower, review — is monolithic. If the meditation gets interrupted, the entire downstream chain derails. A modular routine treats each component as an independent unit that can execute in any order, at any time, and in any combination. If meditation is impossible this morning, you skip it and exercise. If exercise is impossible, you journal and review. The routine degrades gracefully because no single failure cascades through the system — the failure of any individual component does not produce a total system failure.

Mapping your fragility portfolio

Understanding the principles is the first step. Applying them requires an honest assessment of your current behavioral architecture. Every habit you maintain sits somewhere on the fragility spectrum, and most people have never evaluated where.

The assessment is straightforward but uncomfortable. For each habit you consider important, identify its contextual dependencies — the specific conditions that must be true for the habit to execute. A habit that requires a specific location, a specific piece of equipment, a specific time window, a specific preceding event, a specific energy level, and a specific emotional state has six dependencies. Even if each individual condition has a ninety percent chance of being available on any given day, the probability of all six being simultaneously available is only fifty-three percent. Your "reliable" habit is actually a coin flip under anything other than perfectly normal conditions.

Categorize each habit accordingly. Five or more dependencies: fragile, will break under moderate disruption. Two to four: moderately robust, survives mild disruption but fails under significant change. Zero to one: highly robust, survives almost anything short of total incapacitation. And if the habit actually benefits from disruption — if stress makes your meditation more valuable, if novelty makes your creative practice more generative — it is approaching antifragility.

Most people discover that their most important habits are also their most fragile, because the habits they care about most are the ones they have optimized for ideal conditions. The optimization is real. The fragility it creates is also real. And the fragility only becomes visible when the optimization conditions disappear.

The Third Brain

Your externalized thinking systems and AI tools can serve as a fragility auditor for your behavioral portfolio — surfacing the structural vulnerabilities you cannot see from inside the system.

Start by listing your top ten habits with all of their contextual dependencies. Feed this inventory to your AI and ask it to identify the habits with the highest dependency counts, the dependencies most likely to be disrupted simultaneously (travel disrupts location, schedule, equipment, and social cues all at once), and the habits whose failure would cascade into other habits. The AI can perform the combinatorial analysis that your intuition cannot: given a specific disruption scenario, which habits survive and which collapse? Where are the single points of failure?

Then ask the AI to help you redesign. For each fragile habit, generate a context-independent fallback version, a low-activation-energy minimum version, and an identity-anchored framing that survives environmental change. The AI does not know your life well enough to design your habits for you. But it knows enough to pressure-test your designs and propose fallback structures you have not considered.

You can also use the AI to build a disruption playbook — a pre-written set of protocols for common disruption scenarios. "When traveling: these habits switch to these fallback versions. When sick: these habits pause, these continue in minimum form. When in crisis: only these three habits remain active, in these specific forms." Writing the playbook now, while conditions are calm, means you do not need to make these decisions under the cognitive load of an actual disruption. The playbook is a form of Hollnagel's anticipation capacity — you are designing the response before you need it.

From principles to minimum viable routines

You now understand that resilience is not a character trait you either possess or lack. It is a design property you can engineer into your behavioral systems through specific architectural choices: reducing contextual dependencies, lowering activation energy, anchoring to identity rather than environment, and building modular structures that degrade gracefully rather than failing catastrophically. You understand the fragility spectrum and can assess where your current habits sit on it. You have a framework for redesigning fragile habits into robust ones.

But there is a practical tool that operationalizes all four of these principles simultaneously — a single design pattern that, more than any other, separates people whose habits survive disruption from people whose habits do not. That tool is the minimum viable routine: a stripped-down version of every important practice that preserves behavioral continuity and identity expression under any conditions, no matter how degraded. The minimum viable routine takes up this concept in detail, giving you a concrete protocol for building the smallest possible version of each habit that still counts — still maintains the chain, still expresses the identity, still keeps the system alive until normal conditions return.


Sources:

  1. Taleb, N. N. (2012). Antifragile: Things That Gain from Disorder. Random House.
  2. Hollnagel, E. (2011). "Prologue: The Scope of Resilience Engineering." In E. Hollnagel, J. Paries, D. D. Woods, & J. Wreathall (Eds.), Resilience Engineering in Practice: A Guidebook (pp. xxix-xxxix). Ashgate.
  3. Fogg, B. J. (2019). Tiny Habits: The Small Changes That Change Everything. Houghton Mifflin Harcourt.
  4. Wood, W., & Neal, D. T. (2007). "A New Look at Habits and the Habit-Goal Interface." Psychological Review, 114(4), 843-863.
  5. Clear, J. (2018). Atomic Habits: An Easy and Proven Way to Build Good Habits and Break Bad Ones. Avery.

Put it into practice

Exercise

Select three habits you currently maintain that matter to you. For each one, list every contextual dependency it relies on: specific location, specific equipment, specific time of day, specific preceding event, specific energy level, specific emotional state, other people. Count the dependencies. A habit with six contextual dependencies is structurally fragile — it requires six things to go right simultaneously. Now, for each habit, design a version that reduces the dependency count by at least half. If your meditation habit requires your meditation cushion, a quiet room, and thirty uninterrupted minutes, design a version that requires only a chair and five minutes. Write the reduced-dependency version down explicitly. You are not replacing your ideal routine. You are building a fallback version that survives the conditions your ideal version cannot.

More on putting it into practice

See it in action

Two friends both maintain morning exercise routines. When a week-long business trip disrupts their schedules, one person stops exercising entirely — her routine depends on a specific gym, a specific time slot, and a specific playlist. Without those elements, the behavior feels wrong, and she decides to "get back on track when she returns home." The other person exercises in her hotel room for twelve minutes using bodyweight movements she learned years ago. Her routine is not location-dependent, not equipment-dependent, and not time-dependent. It is anchored to her identity as someone who moves her body daily, not to the specific context in which that movement usually occurs. She does not experience the trip as a disruption to her exercise habit because the habit was designed to survive exactly this kind of displacement. By the time her friend returns home and spends another week "getting back into it," the second person has not missed a single day. The gap between them is not discipline or motivation. It is architecture.

Watch for the failure mode

Confusing resilience with lowering your standards. Designing habits that survive disruption does not mean permanently reducing your practice to its minimum viable form. The person who does twelve-minute hotel-room workouts during travel should still do full gym sessions when she has access to a gym. The failure is when someone discovers a stripped-down version and decides that is sufficient forever — that because the minimum works during crises, there is no reason to do more during normal conditions. Resilient design means having multiple operating modes: a full version for optimal conditions, a reduced version for moderate disruption, and a minimum viable version for severe disruption. If you collapse all three into the minimum, you have not built resilience — you have rationalized stagnation. The resilient behavior portfolio is a spectrum of intensity, not a single low bar.

Make it stick

Take the reduced-dependency versions of your three habits from the exercise above. For each one, create an explicit "disruption protocol" — a written plan that specifies exactly what you will do when the normal version of the habit becomes impossible. The protocol should name the trigger ("When I cannot access my usual gym"), the replacement behavior ("I will do a fifteen-minute bodyweight circuit"), and the identity anchor that justifies the substitution ("because I am someone who moves daily, not someone who goes to the gym"). Test one of these protocols this week by deliberately simulating a disruption: skip the gym and do the bodyweight circuit instead, meditate in a noisy room instead of a quiet one, journal on your phone instead of in your notebook. Observe what happens to the felt continuity of the habit. Carry these disruption protocols forward into The minimum viable routine, where you will formalize the concept of a minimum viable routine — the most stripped-down version of your practice that still preserves its identity function and behavioral continuity.

Practice

Build Fallback Habits with Reduced Dependencies in Notion

You'll analyze three current habits for contextual dependencies, then create if-then fallback plans with half the dependencies using Notion's database structure to track both ideal and resilient versions.

15 minutesIntermediate
  1. 1Create a new database in Notion titled 'Resilient Habits' with columns for Habit Name, Ideal Version, Dependency Count (number), Dependencies List (multi-select), Fallback Version, Fallback Dependencies (number), and If-Then Trigger (text).
  2. 2Add three habits you currently maintain as separate rows, then in the Dependencies List column for each habit, add tags for every contextual requirement (location, equipment, time, preceding event, energy level, emotional state, people) and count them in the Dependency Count column.
  3. 3For your first habit, identify which dependencies are most frequently disrupted, then write a Fallback Version that cuts the dependency count in half by removing the most fragile requirements — if meditation needs cushion + quiet room + 30 minutes + high energy, create a version needing only chair + 5 minutes.
  4. 4In the If-Then Trigger column, write specific conditional statements like 'IF my meditation room is occupied or I have less than 15 minutes, THEN I will do 5-minute chair meditation in any quiet corner' to activate your fallback version during disruption.
  5. 5Repeat steps 3-4 for your remaining two habits, ensuring each fallback version has at least 50% fewer dependencies than the ideal version, then add a toggle property called 'Fallback Used This Week' to track when disruptions forced you to use the resilient version.

Common questions about this lesson

More around this idea