Last Tuesday, Marcus looked up from his phone and asked me what time Lily's soccer thing was on Saturday. We have a shared Google Calendar. It has been shared for three years. The soccer thing was on the calendar. Had been for two weeks. Title, location, time, everything.
I told him. He said thanks. We moved on.
That's the family calendar app mental load problem in one small moment that probably doesn't even sound like a problem. He got the information. I gave it to him. It took four seconds. But something in me sank a little, the same way it does every time, because I already knew the answer without checking. He didn't know to check. And neither of those things had anything to do with whether the calendar was shared.
The calendar being shared is not the issue. The calendar being shared never was.
I spent a long time thinking visibility was the fix. If he can see what I see, he'll understand what I understand. So I shared everything. Google Calendar, synced across both our phones. Color-coded by kid. Reminders set. Recurring events labeled. I built a system that would embarrass most small nonprofits.
He uses it sometimes. He adds things occasionally. But here's what I noticed: I still hold the map.
I know that Thursday is the early release day, which means pickup is at 1:45, which means my 2pm call has to move, which means I need to reschedule before Wednesday because the other person is in a different time zone and that's just a whole thing. Marcus knows Thursday is an early release day, in the same way you know a fact. He doesn't know what it costs.
That's the gap. Not information. Context.
A calendar shows you what's happening. It doesn't show you what that thing requires, or what it bumps, or what needs to happen before it. It's a list of outputs, not a picture of the inputs.
I don't think this is Marcus's fault. I think it's how calendars work. They are tools for recording commitments, not for distributing the work of managing them. When I add "Evan dentist 3:30" to the calendar, I've already figured out who's picking him up, whether he'll be back for dinner, whether we need to cancel the playdate, and what we're doing about the two-hour window after school before I get home. None of that is on the calendar. It just lives in my head.
The shared calendar made me feel like I was sharing the load. I wasn't. I was sharing the output of the load.
Here's what it does get right: it helps with the immediate logistics. If Marcus needs to know what time the dentist is, he can check. If I need to know when his work trip lands, I can check. We don't have to ask each other as much for bare facts, and that's genuinely useful. It cuts down on the "did you remember that thing" conversations, at least sometimes.
But it doesn't change who's tracking. It doesn't change who noticed that Lily's recital and Evan's friend's birthday party are on the same afternoon in two weeks and that's going to require actual decision-making about how to split up. It doesn't change who's holding the three-week lookahead in their head at all times, scanning for conflicts before they become emergencies.
The mental load isn't the information. It's the continuous act of managing it.
I'm not sure there's a clean fix. I've tried different things. We've had the conversation, more than once. It helps for a while and then fades. What I've started to understand is that visibility is a necessary first step, not a solution. He has to see it. But then something has to prompt him to act on what he sees, without me prompting the prompt.
That's the part no calendar app has really figured out. They're good at storing and displaying. They're not good at creating shared ownership. Ownership requires both people to feel like something belongs to them, which means both people have to have been in on the thinking, not just handed the result.
Some of that is just a relational thing. You have to actually talk about how you're managing the house, not just share a tool and hope it transmits equally.
But the tool matters too. A calendar that just shows events isn't the same as something that shows the weight behind them, the tasks that feed in, the things that need to happen before the day arrives. The closer a tool gets to that, the more useful it actually is.
A calendar that just shows events was never the problem I needed solved. What I needed was something that showed the tasks and prep behind the events, and kept both of us looking at the same live picture.
What that looks like in practice: if Lily's recital is on the calendar and there are three things that need to happen before it, those things are tasks attached to the household, assigned to whoever is handling them, visible to both of us. Not in a separate app. Not in a follow-up text thread. In the same place the event lives. Marcus doesn't need me to narrate the prep. He can see what's outstanding at the same time I can.
When something gets done, it updates on both our screens right away. He doesn't have to report back. I don't have to check in.
That's what Orbyt does that a shared calendar doesn't. The calendar is part of the picture, not the whole thing. Still in beta at orbythq.com.