Week 2 · Day 1111 / 28

Weekly Meeting 2.0

Installing: The Full Operating System

Test — Where Are You Today

Review the domains you divided this week. What worked? What slipped? Where are the pressure points in the coming week?

Why It Matters

The Week 1 meeting established connection. This week it becomes a functioning operating system: appreciations, domain review, next-week planning, and calendar sync -- in that order.

Solution — Today's Practice

Run the full meeting: five appreciations each, domain check-in, next-week planning, and calendar sync.

Today's Challenge

Last week's meeting built connection. This week it becomes real infrastructure -- a repeatable operating system covering appreciations, what's working (and not) in your divided domains, next week's commitments, and a synced calendar. Add the domain check-in to the agenda tonight so it's part of the system going forward, not a one-time add-on.

Explained
The Weekly Meeting Structure: Appreciation (5 minutes, 20-25%) -- start with what's working, name specific observations. Logistics (15 minutes, 40-45%) -- coordinate the week ahead, calendar review, pressure points, who owns what. One Problem (10 minutes, 50-55%) -- address the biggest friction point, feelings first not blame. Result: logistics contained, random fights eliminated, peace created. The 30-Minute Weekly Meeting: the structure creates containment so conflict doesn't bleed into every day.

Tap to view full size

The base meeting you built in Week 1: appreciation, logistics, one problem.

This is the structure Day 6 installed -- what's new this week slots in around it: a domain check-in after appreciation, and next-week planning alongside the logistics sync. If any of these four parts quietly disappears from your meeting, that's the thing to name and re-add tonight, not let slide.

Solo

Review Your Domains

Review the domains you divided this week. What worked? What slipped? Where are the pressure points in the coming week?

Your response here isn't saved yet -- that lands with activity persistence, a later step.

Couple

Run the Full Meeting

Run the full meeting: (1) Five appreciations each. (2) Domain check-in -- what worked, what failed, and what needs adjustment? (3) Next-week planning -- who has what commitments, where are the conflicts? (4) Update the shared calendar so both people know where they are responsible.

Your response here isn't saved yet -- that lands with activity persistence, a later step.

Reflect
Add the domain check-in to your recurring weekly meeting agenda before you end tonight.
Your Coach

Reflect with your coach

Did this week's meeting actually cover all four parts -- appreciations, domain check-in, next-week planning, calendar sync -- or did one quietly get skipped?

Program progress

Day 11 of 28

← PreviousNext →