The invisible mental load of running kids' schedules

Here's a job description nobody applied for:

Know that Thursday is swim kit day. Know that the birthday RSVP closes tomorrow. Know that the dentist needs rebooking, that the camp form wants a copy of the insurance card, that your daughter's best friend just went gluten-free and the party bag needs adjusting. Know it all, permanently, with no reminders, while also doing your actual job.

That's not "helping with the schedule." That's carrying the mental load, and in most families one person carries almost all of it.

The work is the remembering

The French cartoonist Emma has a well-known comic about this called "You Should've Asked." Her point, roughly: when one partner says "you should've asked me to do it," they're revealing the real division of labor. One person executes tasks. The other person carries the entire catalog of what needs doing, when, and how - and dispatches from it.

Kids' schedules are the purest form of this. The individual tasks are trivial. Signing a slip takes ten seconds. Packing a swim bag takes two minutes. What's heavy is the always-on background process:

• Tracking dozens of small facts with expiry dates
• Monitoring four or five channels where new facts arrive (email, school app, WhatsApp, the backpack, the school gate)
• Projecting ahead: what does Wednesday need that has to happen Tuesday night?
• Broadcasting the relevant slices to the other parent, the grandparents, the babysitter

None of this shows up anywhere. Which is exactly the problem.

Invisible until it fails

The mental load has a cruel property: when it works, nobody sees it. The week runs smoothly, and it looks like the week just... ran. The carrying parent gets no credit for the two hundred small remembrances that made it smooth, because remembering leaves no trace.

It only becomes visible when something drops. The forgotten kit. The missed RSVP. And at that moment it doesn't look like a system failure - it looks like the carrying parent's personal failure. The reward for doing an invisible job well is that its one visible moment is the mistake.

If that dynamic feels familiar, here's the reframe that matters: you don't have a memory problem. You have an architecture problem. All of your family's operational data is stored in one human brain, with no backup, no shared access, and no alerts. No company would run this way. Most families do.

What actually reduces it (and what doesn't)

Some honest notes from trying to fix this in my own family:

"Just remind me" doesn't reduce it. When the other parent says "just tell me what to do," the catalog still lives in one head. Dispatching is part of the load. Delegating execution while keeping the tracking changes very little.

Trying harder doesn't reduce it. More sticky notes, more willpower, more guilt. The load isn't caused by insufficient effort. It's caused by where the information lives.

Externalizing reduces it. Every fact that moves from your head into a system you trust is a fact you're allowed to forget. This is the whole game. The system can be paper, a shared calendar, or an app - what matters is that it's outside your skull and that you trust it enough to actually stop rehearsing the fact.

Shared capture reduces it most. If information lands directly in the shared system - instead of landing in your head and being transcribed later - you were never the courier at all. The email gets forwarded the moment it arrives. The slip gets photographed at the backpack. Nobody carries anything.

Where Kikko fits

I built Kikko as that external system, because every general-purpose tool I tried still left the transcription work - the reading, extracting and typing - inside one parent's head.

With Kikko, the forward or the photo is the whole capture. The AI reads the school email or the crumpled flyer, builds the event card with the date, the packing list and the deadline, shares it with both parents, and reminds you before things are due. When you want to know what tomorrow needs, you ask it - instead of asking the parent who used to be the database.

It won't make the birthday parties plan themselves. But it moves the catalog out of your head, and the catalog was the heavy part.

Kikko is live at app.kikko.ai, free for 14 days, no card required.

And if you do one thing after reading this, do it tonight: pick the fact you're currently rehearsing - the form, the RSVP, the kit day - and put it in a system. Any system. That's one less thing your brain is quietly holding for everyone.