Most family calendars fail in a quiet, specific way: one person maintains them.

Every appointment, deadline and plan passes through a single pair of hands, which makes that person the household's memory, its booking office and its reminder service at the same time. The calendar itself may be perfectly kept. The system around it is fragile, because an event that never reaches the maintainer never reaches the calendar, and a change mentioned in a car or a corridor exists nowhere at all.

Building TaskFamily — a shared home for household tasks, dates and lists — that failure mode kept showing up in the same shape as a familiar engineering problem: a single point of failure that looks like diligence until it breaks.

What worked

Treating entry rights as the feature, not a permission setting. When every adult in a household can add an event the moment it is agreed — at the school gate, on a call, in the room where a plan is made — the calendar stops depending on reports. Entries arrive with the details still fresh: the time, the place, what needs bringing, who is collecting whom. The design question stopped being "how do we display a week neatly?" and became "how do we make adding to it take ten seconds, from anywhere?"

Applying the same rule to tasks as to events. A shared household board works the same way. The chore, the form and the errand are visible where they are assigned, not reconstructed later from memory and mild grievance. One shared list, writable by everyone it affects, removed a whole category of "I thought you were handling that" — not by reminding harder, but by removing the handoff where the information used to get lost.

Giving children a smaller version of the same right. A child who can see the week laid out — and add a kit day, a party or a project deadline to it — is learning the actual skill the calendar teaches: that plans are made of commitments written down early enough for other people to arrange themselves around. Surprises shrink accordingly. The double-booking discovered on the morning itself usually turns out to be two perfectly reasonable plans that simply never met.

TaskFamily is built for that shared entry and shared sight: household tasks, dates and lists in one place, visible to the whole family rather than held by its most organised member.

What broke

The polished read-only view. Early effort went into making the week look calm and complete. It tested well and changed nothing, because a beautiful calendar that only one person can update is still a bottleneck with good typography. The households that struggled were not missing a nicer display; they were missing a second and third way in.

Reminders as a substitute for entry. More notifications made the maintainer busier, not the calendar fuller. Pinging someone to remember to tell the maintainer is still routing everything through one person — it just adds noise to the detour. The fix was upstream: capture at the moment of agreement, by the person who was there.

Assuming the maintainer wants the job. Product copy that praised the organised parent sounded warm and landed badly. Nobody had volunteered to be the household's memory; the role had simply accumulated. Designing to distribute that role — respectfully, without a lecture about fairness — mattered more than any single view or widget.

Lessons worth keeping

A calendar everyone can add to is not a neater diary. It is a household that no longer has a single point of failure. The same principle travels well beyond family software: if a shared record depends on one person hearing about changes and transcribing them, the record will be incomplete in exactly the places nobody can see. Writable by everyone it serves, captured at the moment it happens, beats curated later — in a kitchen, and in most other systems too.

Where have you seen a shared record fail because only one person could update it — and what finally opened it up?