Capacity-Variable Accountability: A Framework for Chronic Illness

The resistance band hangs on the closet doorknob exactly where she left it Sunday night, three mornings out of five. She can see it from the bed — a loop of red rubber, the physical therapist’s homework, ten minutes before breakfast. On those three mornings, the twelve feet between the bed and the doorknob might as well be a mile; her joints have already told her, before she’s fully awake, what today’s ration looks like. On the other two mornings she’s up and looping the band around her ankle before she’s properly thought about it, texting a friend a photo mid-stretch, feeling like someone whose life holds together in a neat row. Something changed between those two kinds of morning — inflammation markers, sleep architecture, the previous day’s exertion, a hormonal tide nobody can see from outside her — and none of it shows up on a calendar or a habit tracker. She learned, the hard way, that any plan which doesn’t already account for this will fail her by Thursday.

That’s the scene that most accountability advice is quietly unequipped to handle. Set a fixed time. Commit publicly. Never miss a day. Treat a skip as evidence you didn’t want it enough. This is coherent advice for a body that shows up roughly the same every morning — a little tired, a little unmotivated, but fundamentally the same machine as yesterday. It is close to useless, and sometimes actively harmful, for a body whose capacity resets every night to an unpredictable number. Put plainly: accountability systems for chronic illness and variable-energy conditions need to distinguish, in their actual design, between showing up on a high-capacity day and showing up on a low-capacity day, because a system that can’t tell the difference will eventually punish someone for their biology and call it a discipline problem. Everything else in this piece is an attempt to make that distinction operational rather than aspirational.

Why standard accountability logic assumes a body it doesn’t have

Nearly every popular accountability method — habit trackers, streak apps, accountability partners who check “did you do the thing, yes or no” — is built on an implicit premise: today’s capacity is approximately equal to yesterday’s capacity. Under that premise, a missed day is diagnostic. It tells you something about motivation, prioritization, or character, because the thing that would have made today possible (a working body, an available nervous system, enough spoons, to borrow Christine Miserandino’s now-famous term) is assumed to have already been present. The system doesn’t need to ask whether you had the capacity, because the model says everyone basically does, every day, if they arrange their life correctly.

Miserandino’s 2003 essay “The Spoon Theory” gave this problem its most durable metaphor. Trying to explain to a friend what living with lupus actually felt like, she grabbed a handful of spoons from a diner table and handed them over one at a time as she narrated a normal day — showering costs a spoon, getting dressed costs a spoon, driving to work costs a spoon — until the spoons ran out well before the day did. The insight that made the metaphor spread far beyond lupus communities wasn’t really about counting utensils. It was that healthy people plan their day by asking what they want to do, while people with chronic conditions plan by asking what they can afford, and the affordable number changes without warning. An accountability system that never asks “how many spoons do you actually have today” is a system designed for the first kind of planning, deployed on the second kind of life.

This is where it goes wrong specifically, not abstractly: a person manages three low-capacity days by adapting — smaller portions of the task, rescheduled where possible, gentler versions of the commitment. Then the tracker resets to zero, the streak breaks, the accountability partner’s easy “you’re slipping” lands like an accusation about character. The system was never wrong about the missed day. It was wrong about what the missed day meant, because it had no category for “showed up as much as was available” versus “didn’t try.”

Capacity-fixed and capacity-variable systems

The distinction worth naming clearly is this: a capacity-fixed system treats every day as having the same baseline of available energy, attention, or physical function, and measures success or failure against that flat expectation — miss the fixed target and the system logs a failure regardless of what your body had to offer that day. A capacity-variable system instead builds an explicit, pre-negotiated range of acceptable outcomes into its design from the start, so that a smaller version of the commitment on a low-capacity day and the full version on a high-capacity day are both legible as success, rather than one being success and the other being an asterisked failure. The first kind of system asks “did you do the thing.” The second kind asks “did you do the thing that matched today,” and it only works if that second question was answered truthfully before the day started, not negotiated in the moment when the moment is already hard.

Most accountability tools on the market — most habit apps, most “text your friend if you skip the gym” arrangements, most 75-day-no-exceptions challenges — are capacity-fixed by default, not by malice. Nobody built them to be cruel to disabled and chronically ill users. They were built for the far more common design target: someone whose main obstacle is inconsistency of will, not inconsistency of body. The trouble is that a capacity-fixed system, applied to a capacity-variable person, doesn’t fail neutrally. It fails in a specific direction — it interprets biology as character, over and over, until the person either abandons the system or starts lying to it, both of which defeat the point of having accountability at all.

The Flex-Floor Framework

What a capacity-variable body actually needs isn’t less accountability. It’s accountability that has been told, in advance, what the range of true effort looks like. I’ll call this the Flex-Floor Framework, and it has three parts, each doing a distinct job.

The floor

Before any bad day arrives, name the smallest version of the commitment that still counts as showing up — not the smallest version that would be nice, the smallest version that is still, unmistakably, the thing. If the commitment is “move my body,” the floor might be two minutes of stretching from bed, not a walk, not a workout, two minutes of stretching, decided on a good day when you can think clearly about what a bad day will need. The floor has to be embarrassingly small. If it doesn’t feel almost too easy to name out loud, it’s still a fixed-capacity target wearing a variable-capacity costume, and it will fail the same way the original commitment did.

The declared tier

Each day, before acting, the person names — to themselves, to a partner, to whatever system is watching — which tier today is: floor, partial, or full. This step is the entire mechanism, and it’s the one capacity-fixed systems skip entirely. The declaration has to happen before the task, not as a post-hoc excuse after missing it, because a system that only classifies days retroactively just becomes a more elaborate way of grading effort after the fact. Naming the tier in advance turns “I did less today” from a confession into a data point, which is a different emotional register entirely and a different informational one for whoever’s watching.

The person who is told the difference

Whoever is providing the accountability — a partner, a friend, an app, a group chat — has to be told what floor-tier success looks like, so that seeing it doesn’t read as failure. This is the part that gets skipped even by well-meaning accountability partners: they agree to “check in on whether you did the thing” without ever being told that the thing has three sizes. Someone who only knows the full-size version of the commitment will, however gently, communicate disappointment at the floor-size version, and disappointment from a chosen observer is exactly the signal that makes a chronically ill person start hiding low-capacity days instead of reporting them.

There’s a useful analogy in how bridges are engineered for load, not for a single expected weight. A bridge rated only for its average daily traffic collapses the first time a heavier truck crosses it; a bridge engineered with a tolerance range absorbs the outlier without failing catastrophically, and the engineers who built it never call the heavy truck a discipline problem. A capacity-fixed accountability system is a bridge rated for average traffic. The Flex-Floor Framework is the tolerance range — built in before the load arrives, not improvised underneath it.

It’s worth acknowledging plainly that this framework, done badly, can become an escape hatch — a way to always declare “floor day” and never stretch toward the fuller version of a commitment on days that could support it. The safeguard isn’t more rigidity; it’s the same three components applied without flinching: the floor stays small enough that declaring it constantly would be its own kind of tell, and someone who’s paying attention will notice a pattern of only-floor over weeks, which is a conversation worth having, distinct from the daily question of whether today’s declaration was accurate.

Where a fixed-time, fixed-picture accountability app runs into this

This is where I want to be specific about a real product rather than staying comfortably theoretical, because the gap matters more than the theory. DontSnooze, the app this blog sits under, works on a capacity-fixed model by default: you set an alarm time, and if you don’t get up and record a photo or video within the window, your chosen friends see it — a picture of you still in bed, or a missed check-in, delivered to people whose opinion you actually care about. For the audience this piece is about, that default is close to unusable as-is, and it’s worth saying so plainly rather than glossing over it to get to a tidy recommendation.

The plain gap: the app currently has no built-in concept of a floor tier. It knows “did the check-in happen by the deadline,” full stop. There’s no native way to pre-declare “today is a floor day, the check-in is just me sitting up in bed for the camera, that’s the whole ask,” and have your friends see that context instead of a bare miss or a bare success. Someone using it as-is, on a bad flare day, either forces a full-effort check-in their body can’t actually support, or takes the miss and lets their friends see an undifferentiated failure that looks identical to the day they simply slept through an alarm out of ordinary tiredness. Both outcomes recreate the exact problem this piece is describing.

What would need to change, concretely, for it to work well: the setup conversation with the friends you’ve chosen would need to happen before the flare, not during one — naming the floor version of the check-in explicitly (“if I send the floor-tier photo, that’s a full success, don’t ask me about it, don’t compare it to yesterday”) so the people receiving the photo have the same three-tier vocabulary the framework requires. That’s a workaround, not a feature, and it depends entirely on picking people who will actually hold the distinction rather than defaulting to disappointment. A future version worth wanting would let the tier be declared inside the check-in itself, so the friend on the other end sees “floor day, and she showed up for it” rather than just a photo with no context, which is the single clearest feature gap between what the app does today and what this population needs.

And yet — even with that gap fully admitted — the underlying idea is one worth adapting rather than throwing out. The reason accountability partnerships work at all, for anyone, chronically ill or not, is that a chosen person changes the felt weight of a small action. A two-minute stretch declared to no one is easy to let slide; the same two minutes, declared in advance as today’s floor and then actually seen by someone who agreed in advance to count it as success, carries a different kind of realness. That effect — a person who sees you, on terms you set together beforehand — doesn’t stop being valuable just because the default setting of who counts as “showing up” was built for someone else’s body. It means the tool needs a conversation layered on top of it before it’s handed to this audience, not that the tool is the wrong idea.

What this looks like day to day

In practice, the Flex-Floor Framework is less a piece of software and more a habit of speech, repeated daily, ideally out loud or in a text to whoever’s watching: “Today’s a floor day, this is what floor looks like, this counts.” Some mornings that sentence is unnecessary — the full version is obviously available, and everyone can see it. Other mornings it’s the only thing standing between a person and either overexertion or shame, and saying it plainly, before acting, is the whole trick. It resembles a related problem covered elsewhere on this site — the way depression can make even a fixed, achievable wake-up time feel physically unreachable, or the specific bind of getting out of bed when the obstacle is depression rather than a broken alarm — except that with depression the target usually stays constant while motivation to reach it fluctuates, whereas with chronic illness the target itself has to move, because the thing that fluctuates is measurable, physical capacity, not the desire to act on it. It’s a different problem producing a similar-looking Tuesday morning, and worth reading alongside the ADHD-specific case for why standard alarm advice fails for reasons that have nothing to do with motivation, since both pieces make the same underlying argument this one does: the failure isn’t the person, it’s a system built for a body that isn’t theirs.

The band still hangs untouched some mornings. That’s not the metric. The metric is whether, on the untouched-band day, the system watching her already knew that today’s version of showing up looked like something smaller than a stretch — and whether the people who saw it understood that as the whole, sufficient thing.