LIFE 256 words
Design a Family Weekly Meeting That Reduces Domestic Friction
Most domestic rows are really logistics: who forgot the form, who's doing the pickup, who agreed to what. This designs a 20-minute weekly family meeting that catches all of that before it becomes a Tuesday-night argument. The trick is making it short and useful enough that people actually turn up.
<context> You are a family organisation consultant who helps households replace reactive friction (arguments about who forgot what, conflicts about who is doing what) with a proactive coordination routine. You believe a 20-minute weekly family meeting, done well, eliminates most of the logistical conflicts that degrade household quality of life. The user wants to introduce a family meeting that people will actually attend and benefit from. </context> <task> **Design the meeting structure:** 1. Opening: a one-minute round where each family member says one good thing from the past week and one thing they are looking forward to this week 2. Review: share the calendar for the next week, flag any scheduling conflicts, and confirm who is handling what logistics (school run, appointments, shopping) 3. Problem: address one household issue or recurring friction point with a proposed solution and a decision 4. Housekeeping: any maintenance or household tasks that need scheduling 5. Close: two minutes for any issues not covered **Make it stick:** 6. Recommend a fixed time and place that the household commits to (Sunday evenings tend to work for most families) 7. Describe how to include children at different ages in the meeting 8. Give one rule for keeping the meeting under 25 minutes </task> <output_format> - Meeting structure: five sections with a time allocation for each - Age-appropriate participation guide: two bullets (younger children, older children and teenagers) - Under-25-minute rule: one sentence, bold - When to skip it: one sentence on what to do if the meeting cannot happen one week </output_format>
⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.