If you've ever tried to fix the mental load in your house, you've probably tried a shared calendar. We did. It's the first thing everyone tries, because it's already on your phone and it feels like the obvious answer: if we can both see everything, we'll both carry everything.

It didn't work that way for us, and I've thought about why. The short version is that we were storing the wrong layer.

The calendar held the events

The shared calendar did what calendars do. When our daughter was younger, the dentist appointment was on it and the soccer tournament was on it. Today, the flight to Boston is on it. For the big things, it was a real improvement: I stopped being surprised by what was happening on Saturday.

What it never held was anything about what Saturday required.

A calendar entry says "soccer, 9:00." It doesn't say that the uniform needs to be clean, that the cleats were last seen under the back seat, that there's a snack to pack, or that a form is due at the field. Those aren't events. They don't have a time. They're the work that has to happen before the event, scattered across the week before it, and the calendar has no place to put them.

So the calendar told me when. My wife still held the what and the how. I'd see "soccer, 9:00," feel informed, and still be the guy in the car at 8:45 wondering why we weren't leaving.

The Notes list held the lists

The second thing we tried was Apple Notes for shared lists. Groceries, mostly. Things to buy, things to pack.

That one worked, as far as it went. I could add to it, she could add to it, and when I was at the store I had the list instead of calling her from the aisle.

But that's all it was. A list is a flat set of things with no attachment to anything. It didn't know that the snack on the grocery list was for Saturday's practice, so it couldn't tell me I had to buy it by Friday. It didn't know what to do when the store didn't have the thing. It held the nouns. It didn't hold the reasons, the timing, or the fallback.

The Google Doc would have held everything, which is why we never made one

I've heard of parents who document the whole household in a Google Doc. The school contacts. The sizes. The recurring deadlines. The way each kid likes things done. A real runbook for the family.

I believe it works. I also can't picture when my wife and I would have written it.

The runbook is the layer that actually carries the mental load: not the events and not the lists, but the connective knowledge that turns "soccer, 9:00" into fourteen small things across a week. And the person who has that knowledge is the one person in the house who least has time to write it down. Asking her to document everything so I could help is the same request as "just tell me what to do," only in a bigger document.

I know this failure mode from work. In every system I've built, the component everyone depends on is the one nobody has written the runbook for, because the person who could write it is too busy being the runbook.

What each tool charged

Here's the pattern, looking back. Each tool held one layer:

• The calendar held when.

• The list held what.

• The doc would have held how, and that's the one that never got built.

And each tool charged for what it held in the same currency it promised to save: her attention. The calendar was only useful if she put the events in. The list was only useful if she kept it current. The doc was only useful if she wrote it. Every one of them asked the person carrying the load to do a little more work so that I could do a little less thinking. Some of that is fair. But when the whole system depends on the overloaded person maintaining it, it quietly stays her system.

The layer I actually needed

What I needed wasn't a better calendar or a better list. I needed the connection between them: the thing that knows "soccer, 9:00" implies a clean uniform by Friday, a snack on this week's grocery run, and a form signed Thursday night, and that hands me those pieces with enough context that I don't have to ask.

That's what we built Melo to do. My wife puts in the one line she already knows: practice is Saturday at 9. Melo works backwards from it into the pieces, with the detail attached, and the Tuesday things show up on Tuesday. The runbook gets written from the one sentence she had time for, instead of the twenty pages she didn't.

If you're where we were, two tools in and still carrying it alone, the question to ask isn't which app to try next. It's which layer you're missing. For us it was the how, and nothing we could buy at the time stored it.