Why I treat family ops like product ops

Stand-ups, retros, even a small roadmap. We run a version of all of them inside our household.

The first time I floated this with my wife she laughed. A few months in, she was the one running the retros. The same operating rhythm that ships software ships a calmer household. The difference is the stakes — these stand-ups are the most important fifteen minutes in my week.

Treating the family as a system is not coldness; it is respect. It says the people in the room deserve the same intentionality I bring to a customer or a team.

If I would not run an engineering org without a weekly cadence, why would I run a family without one?

Sunday evening: a fifteen-minute review of the week. What worked, what did not, one thing to change.

Daily check-in over coffee. Two minutes. Three things each: today's anchor, today's friction, today's small joy.

One quarterly afternoon to look further out — money, travel, kids, our own learning.

Less surprise. Fewer 'I thought you knew' moments. A shared sense of what the week is for.

And — surprisingly often — laughter. The cadence itself becomes a small ritual that everyone starts to look forward to.

Whatever discipline I bring to the work goes home with me. If I can run a tight retro at the office and then refuse to run one at the kitchen table, the lesson is that I do not actually believe in the practice — I just like the meeting.

Family ops keeps the work honest.