BlogOrbyt
household management one person

The day I was sick in bed and still the only one who knew how the house ran

I had a fever of 101 and I was in bed by ten in the morning. Marcus had the kids. He had work calls. He was doing everything, genuinely, and I was not needed.

O
Orbyt·March 28, 2026

I had a fever of 101 and I was in bed by ten in the morning. Marcus had the kids. He had work calls. He was doing everything, genuinely, and I was not needed.

Except he texted me six times in 36 hours.

Not because anything was going wrong. He had it handled. The kids got to school, dinner happened, nothing fell apart. But the texts kept coming anyway: where do we keep Sofia's extra inhaler. Is there anything happening this week I should know about. Did I already pay the aftercare bill or is that still sitting there. What size is Eli in shoes right now, his grandmother's asking.

I answered all of them from bed, half asleep, phone screen too bright, because even sick I was still the only place the household's operating knowledge existed.

That was the thing that stuck with me after I recovered. Not that he needed to ask. Not that I was annoyed, because I wasn't really. But just the plain fact of it: I could not actually go offline. I could lie in bed and try to rest, but the household couldn't go to anyone else for the information it needed. There was no one else. There was just me.

That's the part I keep thinking about when people talk about household load.

It doesn't start as a decision. Nobody sits down and says, you will be the one who holds all of this. It accretes slowly. One person pays attention, gets asked a question, answers it. Gets asked again. Answers that too. Over time the pattern hardens and that person becomes the place where everything is stored, and everyone else becomes a person who asks them things.

The tasks are part of it. But the tasks aren't the whole thing. The deeper weight is the tracking -- the awareness that something is coming up, the background thread that's always running, the sense that you are the only thing standing between your household and forgetting something important. That's not a to-do list. That's a system with one node. And when the node goes offline, even partially, the system can't function.

There's nothing wrong with Marcus for not knowing where the inhaler was. I don't say that to be generous. I mean it literally. He didn't know because I had never put it anywhere he could find it. The information existed in my head and nowhere else. So when I was sick and he needed it, his only option was to come to me. Of course he texted. What else was he going to do.

That's a design problem, not a character problem.

I've thought about why it ends up this way so often. Part of it is attention, which way attention flowed early on. Part of it is who got asked things first and therefore became the person who knew. Part of it is that once the pattern sets it becomes self-reinforcing: you know, so you get asked, so you know more, so you get asked more. It tends to run along gendered lines for a lot of families, though not always. The dynamic looks the same whether it's a mother or a father or whoever ended up being the one who pays attention. The problem is structurally identical.

And the problem is this: one person is running a second job that has no hours and no off switch. The job is called knowing what's going on with the house.

When I'm sick it's visible because I'm physically unavailable and the questions still find me. But it's also there when I travel for a few days, or when I have a week where I'm stretched thin, or when I just want to sit down without doing a mental scan of everything that's in motion. The household doesn't pause when I step back. It just routes the requests to me anyway.

What I wanted was for the information to exist somewhere other than inside my head. Not a shared notes app that I'd be the only one updating. Not a calendar my husband technically has access to but never checks. An actual external system where the recurring structure of our household could live, where anyone could find what they needed, where things happened without requiring me to remember to trigger them.

The cognitive overhead isn't about doing a lot. It's about maintaining constant awareness. Knowing which things are in flight, which things are coming up, which things need to happen before someone asks about them. Externalizing the information doesn't make the household simpler. It makes the load something two people can actually share, because the knowledge isn't trapped in one of them anymore.

The first time Marcus found something on his own without texting me, I felt it in a way that's hard to explain. Not relief exactly. More like the pressure dropping by a few degrees. The thing he needed existed outside of me. The system had somewhere else to go.

When I'm sick now, I can actually rest. The household still runs. And the texts are fewer.

When I'm sick now, I can actually rest. The household still runs. And the texts are fewer. That's the whole thing, really. The information exists somewhere other than my head, and that means I'm not the only one who can answer when someone has a question. Orbyt is what I used to build that.

Ready to stop carrying it all?

Orbyt moves your household out of your head — into somewhere both of you can see and act on.

Join the waitlist — free beta access
All posts

Related Posts

  1. cognitive labor relationships

    I found the term for what I'd been trying to explain for three years

    2026-03-31
  2. why household tasks fall to one person

    I noticed I was the one. Then I figured out why.

    2026-03-31
  3. mental load

    The thing I carry that I didn't even know I was carrying

    2026-03-28