Melo becomes a paid app on November 15. Create your account before then and you're a founding member, free through November 14, 2027. Details.

Last week I wrote about the layer our shared calendar never held: not the events, not the lists, but the knowing that connects them. The runbook nobody writes.

This week is about why nobody writes it. I used to think it was a time problem. It's not. It's a capture problem, and it's about three seconds long.

Where the thought arrives

Here's where the mental load actually shows up. Not at a desk. Not with an app open.

It shows up at 10:40 at night, brushing teeth, when my wife remembers the form is due Friday. It shows up in the car, at a red light, when she realizes the snack for Saturday isn't in the house. It shows up mid-meeting, mid-shower, mid-sentence with someone else. The thought arrives, fully formed, in the least convenient place possible, and it's hers to hold until she can do something with it.

My favorite example isn't even a task. It's the poster on the school notice board, or the flyer at the community center: a Saturday science fair, a free swim clinic, a family hike. We'd stand in front of it and one of us would say "we should do that." And we meant it. And by the parking lot it was gone, and we'd see the same poster three weeks later, after the event, and say it again. Nobody counts that as mental load. But it's the same three seconds, and the same loss, and over a childhood it adds up to a lot of things we meant to do.

And then there's the three seconds. The thought is there; something has to happen to it, or it gets overwritten by the next thing. In those three seconds she can do one of two things: hold it in her head, or get it out.

Every tool we ever tried required more than three seconds.

Why every tool fails at the same moment

Open the calendar. Pick a date. Pick a time, which the thought doesn't have. Type a title. Decide whether it's an all-day event. Save. That's fifteen seconds and four decisions for a thought that was "snack, Saturday."

Open the list app. Which list? The grocery list or the to-do list? Is this a grocery item or a task? Type it. Decide if it needs a reminder. Save.

Open the doc. Find the section. Type it where it belongs, in enough detail that someone else could act on it. Which, at 10:40 at night, is never.

Each tool asks the thought to arrive already sorted: this is an event, this is an item, this is a note, here is its date, here is its list. But the thought doesn't arrive sorted. It arrives as "snack, Saturday, don't forget," and the sorting is work, and the work is exactly the thing she doesn't have three seconds for.

So the thought stays in her head. Not because she chose to carry it. Because getting it out cost more than carrying it.

This is the same reason the runbook never gets written. The knowing doesn't arrive as a document. It arrives one line at a time, at red lights, and there's never a moment to transcribe it into the form the tool wants.

What I got wrong about helping

For years my version of helping was asking "what can I do?" The problem with that question, I've written before, is that it hands the thinking back. But there's a second problem I only saw later: it arrives at the wrong time. I'd ask on Saturday morning. The thought she needed me to act on had arrived on Tuesday night and been carried, by her, for four days, because there was nowhere to put it that I would see.

Capture isn't a feature. It's the difference between a load that gets shared and one that gets carried.

The three-second rule

If I had to reduce everything we've learned building Melo to one rule, it's this: the tool has to accept the thought in the form it arrives, in the time it takes to say it, or it isn't a tool for the mental load. It's a tool for people who've already done the mental load.

That's what the brain dump is for. My wife says what's in her head, in whatever order it's in, "form Friday, snack Saturday, call the dentist, the thing with the gutters," and stops. That's the whole capture. Melo does the sorting: which are tasks, which have dates, which go on a list, which need one of us to do something before Saturday. The school newsletter gets forwarded to it instead of read and re-typed. The poster on the notice board gets photographed, and the date and the place come out of it instead of staying on the wall. A screenshot, a PDF from the school, a note someone sent her: Share, Melo, done, on either phone. And in the car, where most of these thoughts arrive and where typing is the wrong answer, she doesn't open anything: "[Hey Siri, tell Melo] snack for Saturday," hands on the wheel, done. (That one's iPhone for now; Android is coming.) The thought leaves her head in three seconds, and the sorting, the part that used to cost more than carrying, happens after she's put the phone down.

I'm not going to claim it catches everything. But the question I ask of every feature now is whether it makes those three seconds shorter or longer. Most of what we've shipped that mattered made them shorter. Most of what we've killed made them longer.

What to do if you don't have a tool

You don't need Melo to use the rule. If your partner carries the load, the thing you can do is give the thought somewhere to go that is faster than her own memory: a text to you, unsorted, that you promise to act on without asking what it meant. "Snack Saturday" is enough. You figure out the rest. The sorting is yours now.

And the poster on the notice board: take the photo. Don't decide what to do with it. Just take it, and send it to the person who'll act on it without asking what it was for.

That's the whole game. Not the list. Not the calendar. The three seconds where the thought either gets out or gets carried.

Melo becomes a paid app on November 15. Create your account before then and you're a founding member, free through November 14, 2027. Details.