--- title: Family Is a Venture description: The single most common failure mode for people who run many things is that family time becomes the residual — and the structural fix is to model family, health, home, and relationships as ventures with equal standing in the same brief. track: playbooks url: https://www.chiefofstaff.io/guides/family-is-a-venture published: 2026-09-01 author: chiefofstaff.io editorial system outcome: model each personal area as a venture with a hub note, surface family and personal blocks in every brief with the same weight as work, and run a relationship cadence through a dedicated, highest-confidentiality curator. prerequisites: the-vault, the-daily-brief source: chiefofstaff.io --- # Family Is a Venture The single most common failure mode for people who run many things is that family time becomes the residual — and the structural fix is to model family, health, home, and relationships as ventures with equal standing in the same brief. ## The Failure Mode From the anti-patterns file: *family commitments not scheduled in the same calendar as work get compressed to nothing within six months.* The tell is "I'll be home for dinner" stated, not calendared; a child's event skipped because work came up. Nobody decides this. It happens because work sends reminders and family does not, and a system that only knows your job will optimise your job. ## The Fix Is Structural, Not Motivational **Personal life is a first-class venture.** Family, health, home, money, relationships, learning, the parents — each gets `Atlas/ventures//VENTURE.md` exactly like a company does: a hub note, a decisions file, a someday list, projects. They carry the same labels in the task graph, appear in the same weekly portfolio-state section, and get the same "untouched for seven days" flag when they go quiet. And the daily brief has a fixed section — **today's family and personal blocks** — with the same billing as decisions and meetings. The brief's calendar section explicitly groups any time overlap between a work event and a personal one, whether or not you planned to attend both, so the collision is visible before it happens. ## What This Looks Like in Practice - A school pickup is a calendar block that surfaces in the brief and that a proposed deep-work block cannot be booked over. (The system nearly did exactly that once, having mislabelled a family member's invitation as "unrecognised sender" — the [enrichment discipline](/guides/the-one-way-valve) exists because of it.) - "Book the dentist" is a task in the `health` venture with a cognitive mode and a priority, reviewed on Sunday like everything else. - A long-horizon family decision has a project note with a decision log, so the reasoning does not have to be reconstructed each time it comes up. - Parents, siblings, and the household have people notes, and their birthdays and recurring obligations are dated tasks — not things you hope to remember. ## The Relationship Cadence The most sensitive area got its own curator: a **relationship curator**, read-only, highest-confidentiality tier, that reads the couple's calendar, the relevant mail, the vault, and voice-note transcripts, and produces a short daily pulse on the relationship venture. By decision record it became the venture's *cadence engine*, with three responsibilities: - **Track the rhythm.** Whatever the couple's rhythm is — a solo sprint week per month, dates concentrated in a particular window — the curator checks in on a schedule instead of assuming a fixed calendar. - **Plan and verify.** Date blocks proposed ahead of time, then verified after — did it happen, was it good, what to change. - **Recurring gestures.** Flowers weekly, gifts lead-timed to occasions, the twice-yearly "big map" conversation, the monthly check-in, the phone-free dinner norm — each a dated task the brief cannot lose. The curator is read-only; the chief of staff does every write. Its tier means the *shape* of things surfaces ("cycle check-in due; date window opens Thursday") and the details stay in the vault behind the tier. And when it gets the shape wrong — it once resolved a contradictory signal the wrong way — that is a feedback-log entry like any other, with the root cause written down. ## Why This Is the Load-Bearing Guide Everything else on this site makes you more effective at work. This is the guide that makes the system worth having. A chief of staff that only knows your job is half a chief of staff — and the half it is missing is the half you would regret. ## Getting Started In the interview on day one, when your Claude asks about ventures, list the personal ones *first*. Give each a hub note with the same care as a company. Put the standing family blocks on the calendar the brief reads. Then watch the first week of briefs: if the family section is empty, the calendar is lying, not the system. ## See it The [demo vault](/demo/vault/atlas/ventures/maya/venture) has a venture that is a person, and the rule that it never gets a process name. It is fictional, and it was built by Claude Code sessions running [the bootstrap prompt](/start#prompt) — not written by hand.