We automated meeting notes before school emails
An entire household is often run by one tired person refreshing six different group chats. The unpaid job of keeping a family alive has zero infrastructure — so let's design some. Below: a live model of household information flow. Watch the chaos, then apply the three fixes.
The message storm simulator
Apply infrastructure
Why one person ends up holding it
Defaults, not decisions. Nobody chose the six-chat system. The school picked email, the team picked WhatsApp, the carpool picked SMS, and whoever answered first became the permanent router. Sociologists call this "gatekeeping by accident" — the first responder becomes the single point of failure.
The math is brutal. Six channels × ~12 messages/day × a context-switch cost of 2–3 minutes each (task-switching research, APA) ≈ 3+ hours of attention fragments daily — before doing any of the actual tasks the messages describe.
Interfaces hide the work. Meeting notes got automated because office work is measured and billed. Household coordination is unmeasured, so no one builds for it — and the person doing it can't even show a log of what they did.
The 2-week rollout
Week 1 · Consolidate
Create one shared family calendar and one family channel. Every incoming item gets forwarded there within the day — no information lives only in a side chat. Expect to forward ~40 items the first week.
Week 1 · Split intake
Divide the six sources by channel, not by task: one adult owns school email + team chat, the other owns carpool + activities. Owning a channel means reading, deciding, AND doing — not summarizing it for the other person.
Week 2 · Batch + sync
Set two 15-minute check windows (e.g., 7:30 and 17:30) and one Sunday 15-minute sync. Measured pilots of "batched communication" show interruption counts dropping by 60–80% with no increase in missed deadlines.