Some events divide time

My sister Chelsey’s accident is one of the experiences that divided my life into a before and an after.

There are events that do not simply create a problem to solve. They alter the assumptions around which a family, a body, a schedule, a future, and a sense of what is possible have been organized.

In those moments, ‘getting back to normal’ can be the wrong objective because the previous normal may no longer exist.

Resilience is reorganization

I used to hear resilience described as bouncing back. I think that metaphor is too elastic and not alive enough.

Living systems often survive by reorganizing. Roles change. Resources move. Homes, routines, relationships, expectations, and identities adapt around new conditions. The system does not return unchanged. It becomes capable of holding something it was not originally designed to hold.

A crisis makes architecture visible quickly. Who can step in? What information exists only in one person’s head? Which responsibilities have no backup? How much financial or emotional margin exists? What requires physical presence? Which systems assume everyone is functioning normally?

Those questions apply to families and organizations alike.

Designing for disruption is not pessimism

We sometimes resist redundancy, contingency, insurance, succession, or spare capacity because planning for disruption feels like expecting failure.

I see it differently. Preparing a system to encounter reality is an act of commitment to the system. The goal is not to predict every bad day. It is to avoid requiring a perfect day in order for everything to keep working.

Resilience is not proof that nothing can change you. It is the capacity to change without losing everything you were trying to protect.

When I write about my sister's accident, I resist turning it into a neat lesson. There were too many contingencies, too many people, too much luck, too much terror, too many systems working and failing at once.

What I know is that I stepped into building structures that could preserve a life worth living. The structures were not the life. They were ramps, schedules, advocacy, information, equipment, care, money, people, and repeated decisions about what had to change next.

Those things changed our lives. They did not end them. That is closer to what I mean by resilience than bouncing back.

Bad days are ordinary system requirements

The phrase ‘bad day’ can make disruption sound exceptional. Often it is not. Someone gets sick. A child needs to be picked up. A vendor fails. Weather changes the plan. A customer needs more than expected. A person who usually carries something cannot carry it today.

A system that only works when everyone is at full capacity is already operating with a hidden dependency on perfect conditions.

What matters is what can move

I am less interested now in whether a system can resist change than whether it can redistribute load without destroying the people or relationships inside it. Can someone step in? Can a commitment be renegotiated? Can information move? Can the plan become different without the entire structure being treated as a failure?