SIPS Month 2: The Long Tail of Recovery

Hi, it's me, back with another month of physiological shenanigans.

The Institute was busy in August! I partially recovered from a rough flareup, started a beta test program, turned a year older, and took my first-ever solo trip relying entirely on myself as a disabled person.

Alongside all that was the continued process of applying for disability support and rebuilding my business after a rough first half of the year. So the questions about capacity, recovery, and accessible support were playing out in real life while I was trying to understand them!

Month 1 of SIPS established a baseline and gave me questions worth following, like the difference between apparent and recoverable capacity. Being able to do something didn't mean I had enough capacity to absorb the cost afterward.

So Month 2 started with a simple question: Would that distinction keep showing up?

It did...but it also got stranger. Month 2 suggested that even after usable function returned, other parts of recovery could keep lagging behind.

In other words: Being functional again did not necessarily mean I was recovered.

Previously, at SIPS…

Month 1 showed that I could work, go somewhere, socialise, handle an appointment, or otherwise look reasonably functional—and discover afterward that doing so had cost much more than it appeared to in the moment.

That distinction between capacity and recoverability was worth following.

At first, I thought Month 2 would mostly tell us more about delayed cost. Instead, it shifted the question. Function, mood, physical energy, sleepiness, and appetite did not always seem to recover together.

So the investigation moved from "Can I do this, and can I recover from doing it?" to "Which part of me has actually recovered?"

What happened when we followed that thread?

The strongest Month 2 development was what I'm starting to think of as a long-tail recovery. The "worst" part of an episode would pass and I'd be out of crisis, but not really doing much better.

If I can write, answer messages, leave the house, and make decisions, it's kinda tempting to assume I'm recovered. Instead, my observations suggest there's a mismatch between functional rebound and other aspects of recovery.

They don't yet tell me why that mismatch occurs and whether it follows a predictable sequence or not, but those are Month 3 questions.

Finding 1: Functional rebound is not full recovery

During Month 2, usable function sometimes returned first after a crisis. I could work again, think more clearly, and make decisions, while physical energy, mood, sleepiness, appetite, or interest still lagged behind.

The exact mix varied. The important part was that “functional” and “recovered” did not consistently arrive together.

Month 1 established that capacity and the ability to recover were not the same. Month 2 agreed. Even the return of capacity may not reliably prove that I'm fully recovered.

That introduces the possibility of asynchronous recovery: different parts recovering at different rates. I just don't know whether spending my newly recovered capacity will affect my recovery afterwards. Yet.

Finding 2: Smaller crises may still carry a long recovery cost

Several Month 2 episodes appeared less severe, shorter at their peak, or both, compared with earlier crises. At the same time, the crisis and my total recovery burden didn't necessarily shrink together.

This challenges the assumption that a smaller crisis should mean a proportionally smaller total recovery cost.

Month 2 does not consistently support that. A shorter or less severe episode may still be followed by several days of reduced physical energy, mood disruption, sleepiness, or other effects.

This is still a candidate pattern. One month is not enough to know whether the crises themselves are genuinely changing. For now, the narrower finding is:

Acute severity and total recovery cost may not move together.

Finding 3: Sleep can look better on paper than recovery feels

Month 2 included days when my wearable was telling me I was in recovery, but I'd still be exhausted, nauseous, and depressed.

The numbers and the experience did not always agree. That mismatch is useful.

A wearable can provide information about sleep duration, timing, heart rate, estimated recovery, and related proxies. It cannot directly tell me whether I woke up feeling restored. At this stage, the strongest conclusion is simple:

“Good sleep” and “restored” cannot automatically be treated as synonyms.

What comes next is figuring out which kinds of sleep or recovery data actually predict what I can do—and how I feel afterward.

Finding 4: Reducing the effort of care may matter in its own right

During lower-capacity periods, the self-management strategies that proved most usable were often the ones that required less effort.

Pre-prepared meals. Shorter observations. Using accessibility supports. Fewer steps between identifying a need and meeting it.

Until now, much of SIPS has asked whether a particular behaviour, intervention, environment, or decision affects symptoms or recovery. Month 2 suggests another variable deserves more attention:

What does it cost to do the helpful thing?

An intervention can be beneficial and still be functionally inaccessible if using it requires more capacity than I have. That moves accessibility and burden from background context toward something worth observing directly.

Explorer field notes

One of the stranger parts of Month 2 was realizing how persuasive functionality can be.

The return of function feels like evidence. I can work, answer messages, and leave the house. Therefore, some part of my brain immediately wants to declare the problem solved.

But the data is making that harder to do. “Back to normal” is starting to feel like a pretty useless category if I can be back in one area and nowhere close in another.

The log also has its limits. It can tell me that function returned, but has a harder time capturing the negotiation afterward:

How much do I trust that capacity? How much do I spend? Am I resting because I still need it, or because I'm anticipating another stressor?

The data has made some things clearer. It has also given me better questions, which may be more useful anyway.

What we're following next

Month 3 gets three main questions:

How large is the recovery gap?

If functional rebound can precede fuller recovery, how long is the distance between them? What tends to return first? Which ones lag? Does the pattern change depending on the type of strain?

Are mini-crises actually changing?

Month 2 suggested a possible pattern of shorter or less severe episodes paired with longer recovery tails. Now we need to see whether that keeps happening or whether Month 2 was simply an unusual cluster.

What changes when burden becomes part of the observation?

Accessibility and burden have been present throughout SIPS, but mostly in the background. Month 3 will begin a small test of tracking a few specific real-world stressors more deliberately.

Just enough to ask whether the cost of navigating something helps explain patterns that symptoms alone do not.

Out and about

SIPS also did a few things outside the observation log during Month 2.

Field Kit #1 continued circulating as a lightweight way for other people to start making their own observations.

I also started a beta test program, a first step toward seeing how this work translates beyond my own observation log.

Want to help shape what comes next? Join the SIPS Explorer Panel to help test these tools and tell me what works—and what asks too much of you.

Work also continued on minimum viable reporting, ways to return after missed or low-capacity observation days, and early infrastructure for eventually testing SIPS methods with other Explorers.

If you're curious about observing your own days, Field Kit #1 is a place to start. No perfect record required.

What I'm carrying into Month 3

Month 1 taught me not to confuse capacity with sustainability. Month 2 taught me to separate function and recovery. Month 3 gets to investigate the space between them.

If recovery is multi-factor, I want to know what comes back first, what stays behind, how long the gap lasts, and what makes that gap larger or smaller.

And if accessibility changes how much capacity ordinary life requires, then burden may turn out not to be background noise at all. It may be an important part of the story.