The weekly family meeting: 20 minutes that save hours of arguments
The whole family, in a single app.
The family organiser for iPhone, Android and the browser, end-to-end encrypted. Free for a family of two parents.
The phrase "family meeting" suggests something solemn, or worse, a telling-off session. Done well, it's the opposite: twenty minutes a week where everyone knows what's happening, problems get tackled before they turn into rows and children have a space where their voice counts.
Why it works
In families without a fixed time to talk, things get decided in the hallway, on the fly, when someone is already cross. The meeting moves those conversations to a calm, predictable moment. And it gives everyone a valuable piece of information: if there's a problem, there's also a place to bring it.
When and how long
- Once a week, always the same day: Sunday afternoon or evening works for almost everyone
- Twenty minutes, thirty at most. Nobody wants to repeat a long meeting the next week
- Everyone present, from four or five upwards, with phones away
Put it in the family calendar as a recurring appointment: if it's in the calendar it exists, if not it disappears the first busy week.
The four-point agenda
1. One good thing (3 minutes)
Everyone shares something that went well that week, or thanks someone else. It looks like a detail: it's what stops the meeting being associated only with problems.
2. The week ahead (7 minutes)
Look at the calendar together: commitments, who's driving whom, dinners out, appointments, tests. It's when clashes get spotted — the match and the party at the same time — while there's still time to fix them.
3. One problem to solve (7 minutes)
Only one a week. Anyone can raise it, children included: the bathroom left messy, fights over the tablet, pocket money. Gather ideas, choose a solution to try for a week, and check the following week whether it worked.
The golden rule: talk about the problem, not the person. "The bathroom is always busy in the morning", not "Julia always takes an hour".
4. Who does what (3 minutes)
Decisions become actions with a name: who books, who buys, who calls. Written as assigned to-dos, they don't get lost between meetings.
The minutes in a note
A shared note with one line per meeting — date, problem discussed, solution chosen — looks like bureaucracy. It's useful: after a few months you can see which problems keep coming back, which solutions worked, and you avoid having the same discussion twice.
What not to do
- Don't use it for telling-offs. If every meeting becomes a list of faults, the children will stop taking part.
- Don't let parents decide everything. On some things parents have the last word, and it's fine to say so. But if children never decide anything, they'll soon realise the meeting is fake.
- Don't let it run long. If a problem needs more time, parents discuss it separately, or it continues next week.
With children of different ages
With the youngest, the meeting can be even shorter and more concrete: what are we doing on Saturday, what are we eating on Sunday. With teenagers, letting them run the meeting now and then boosts participation a lot.
In short
Twenty minutes a week, always the same day, in the calendar. One good thing, the week ahead, a single problem, who does what. One-line minutes, no telling-offs and real decisions for the children too. It won't eliminate arguments. But it will move them to a moment when they can be solved.
The tools this article talks about
Read next
The evening routine that actually works for families
Between 6pm and 9pm you decide how tomorrow goes. A four-block routine, with what to prepare in the evening so you don't run in the morning.
Your partner won't use the family app? Why it happens and how to fix it
You installed it, loaded everything, and the other parent still asks "what time's the appointment?". The five reasons a family app doesn't take hold, and what to do.
The mental load of parents: what it is, why it falls on one person and how to unload it
It's not the housework: it's thinking about the housework. How to make the invisible load visible and move it from one person's head into a shared system.