Anticipating
Noticing needs before they become emergencies: cleats will be too small by spring, the passport expires before the trip, the science fair is in three weeks.
Self-driving cars exist.
Who's driving the calendar?
Soccer schedules, the school email, the permission form, the pickup change, the thing buried in a group chat. One person usually tracks all of it — a real workload that never appears on a resume. This is the mental load, and you can model it.
—
Load index
Drag to rotate
Split with a partner
14
Loops on carrier
0
Loops on partner
0
Loops in a system
5.8h
Est. weekly hours
Each cube is an open loop — something that must be remembered, checked, or chased. Orbit speed and color intensity track how overloaded the central carrier is. Hours estimate: ~25 min/loop/week of anticipating, checking, and coordinating.
The load is not the chores. It's the tracking of the chores.
Sociologist Allison Daminger's research on cognitive household labor breaks the invisible job into four distinct activities. Doing the dishes is visible. These four are not — and studies consistently find they fall disproportionately on one partner, most often mothers.
Identifying options
Researching the choices: which camp, which dentist, which form, which gift. Hours of comparison work that produces no visible artifact.
Deciding
Making the call — often the most shared step, and the one partners point to when they say "we decide together." The steps around it are the imbalance.
Monitoring
Checking that the thing actually happened: was the form returned, did the payment go through, did anyone reply to the coach. The loop only closes here.
Every open loop consumes working memory even when you're not acting on it — psychologists call the residue of unfinished tasks the Zeigarnik effect. Twenty open loops is a background process that never sleeps. Why "just relax" doesn't work for the default parent.
Worked example — one ordinary week
| Open loop | Anticipate + research | Coordinate | Monitor |
|---|---|---|---|
| Soccer: schedule change + carpool | 15 min | 25 min | 10 min |
| School email: spirit week + supplies | 10 min | 15 min | 10 min |
| Field trip form + payment | 5 min | 10 min | 15 min |
| Pickup change (dentist Thursday) | 10 min | 20 min | 10 min |
| Birthday party buried in WhatsApp | 20 min | 15 min | 10 min |
| Camp registration opens Friday 9am | 45 min | 15 min | 15 min |
| Total | 1h 45m | 1h 40m | 1h 10m |
≈ 4.6 hours of pure coordination in one week — before any actual driving, shopping, or cooking. At six loops. The simulator above defaults to fourteen, which is closer to what school-age families report. That's why the "AI assistant for family logistics" category exists: the job it targets is real, measurable, and historically uncounted.
What actually reduces the load?
Play with the model above and the pattern is clear. Offloading to a system (shared calendar, auto-reminders, an AI that reads the school email and extracts the dates) removes loops entirely. Splitting with a partner halves the count only if ownership transfers — if one person still monitors whether the other did it, the loop never left their head. The failure mode of delegation is monitoring; the fix is transferring the whole loop: anticipate, research, decide, and verify.