System 08
Shared work · Household responsibilities
The Family Responsibility Map
Ownership, not tasks. Standards, not nagging.
- Who it's for
- Families with children aged 5 and up
- When it runs
- Created once, reviewed monthly, adjusted seasonally
The invisible load
The parent who is the only one who notices the bin, the washing, the empty loo roll, the pet's water bowl.
The child who is asked to 'help' but never quite knows what 'help' means today.
The endless reminders that turn every small task into a power struggle.
The household where everyone lives together but only one person feels responsible for how it runs.
Why we resist this
It is faster to do it ourselves
Teaching a child to own a domain takes longer than doing it the first ten times. Most parents give up before the child reaches competence, which teaches the child that they were never really expected to do it.
We confuse ownership with punishment
Responsibilities are often assigned as consequences for behaviour, which makes them feel like punishment. A responsibility map assigns ownership as a sign of belonging, not a penalty.
We do not trust the standard
If the standard is 'the way I would do it,' a child will never meet it. Ownership includes the right to meet the standard in their own way, within agreed limits.
Remove before you add
Before assigning more jobs, check how much of the work needs doing at all.
- Which household task exists because it has always existed?
- What could be done less often to the same effect?
- Where is a higher standard being maintained than anyone actually needs?
- Which job could be removed by changing where something lives?
Set this up first
- List every recurring household task and the domains they belong to: kitchen, laundry, pets, bins, entryway, bathrooms, shared spaces, recycling.
- Separate daily tasks from weekly tasks from seasonal tasks. A child can own a domain more easily than a scattered set of jobs.
- Define the standard for each domain in one sentence: 'The kitchen is tidy when the counters are clear and the dishwasher is loaded.'
- Create a visual map that shows who owns what. Put it where everyone can see it.
The system
The domains
Grouped areas of responsibility rather than individual tasks. A child might own the entryway, not just 'put your shoes away.'
The owners
One primary owner per domain, with a backup person who can cover illness or absence. Shared domains are fine, but they need a named lead.
The standard
A simple, observable description of what 'done' looks like. Not a parent's secret standard; a written one that everyone can see.
The review rhythm
A monthly check-in that is not a scolding. What worked? What got hard? Does anyone want to swap or take on something new?
Running it
Map the domains
Write the household domains on a large sheet or board. Let everyone see the whole picture before anything is assigned.
Assign ownership by choice first
Ask who is interested in which domain. Interest is not required for everything, but starting with choice increases buy-in. Fill the gaps by negotiation.
Define the standard together
For each domain, write one sentence describing what 'done' looks like. The child should help write it. If they cannot describe it, they do not own it yet.
Teach the domain
Spend a week doing the domain together, then a week watching while the child does it, then a week letting them do it alone. Real ownership requires teaching.
Review monthly, not daily
Daily nagging destroys ownership. The monthly review is where adjustments happen. If the domain is failing, the system is failing, not the child.
When this stops working
The standard keeps creeping upward.
If the child does the domain and the parent re-does it, the child does not own it. The standard must be agreed in writing and honoured even when it is not your way.
Ownership becomes rigid and unfair.
The monthly review exists to allow swaps. If a child is stuck with a domain they hate for months, the system feels like punishment, not belonging.
The adults are not on the map.
Children must see adults owning domains too. If the map is only for children, it sends the message that responsibilities are something adults impose on children, not something the household shares.
Who owns what
System owner
One adult keeps the map current as children grow. Revisit termly, not weekly.
System users
Everyone in the household.
Child's role
Contribution appropriate to age: belongings, their own space, one shared task. Not adult logistics, not the care of younger siblings as a standing duty.
Shared role
Noticing when something has quietly landed on one person again.
Make it easier
- Attach a task to a moment that already happens rather than a time of day.
- Keep the number of assigned jobs small enough to remember without a chart.
- Give whole tasks, including the ending, so nobody has to supervise.
- Store what a job needs where the job happens.
Make it yours
For a young child
Start with a single, concrete domain: the bathroom sink, the pet's water bowl, the shoes by the door. One domain, well taught, builds more competence than three tasks half-learned.
For a teenager
Give them domains that matter to their life: laundry, their own room, their sports gear, a meal a week. They need to see the connection between ownership and autonomy.
For neurodivergent children
Use visual checklists, colour coding, and timers for each domain. The standard should be visible and broken into small steps. Executive function support is part of ownership.
For a single parent
The map still matters, even if the adult owns most of the domains. A child who owns one real thing is learning competence, not just 'helping.'
The minimum viable system
One task each, attached to something that already happens.
- 01Name one job per person.
- 02Attach it to an existing moment: after dinner, before the bus.
- 03Say what finished looks like.
- 04Leave it there for a fortnight before adding anything.
Keep this line
A child who owns something becomes someone who notices. A child who only helps learns to wait to be told.
A note from Sian
Responsibility is one of the ways children develop a sense of themselves as capable people. When they only 'help' with tasks assigned by an adult, they learn compliance. When they own a domain, they learn stewardship.
The resistance parents feel is often not about laziness; it is about control. Letting a child own a domain means accepting that it will be done differently, more slowly, and sometimes less well. That is the price of competence.
Thrive Family Systems are psychoeducational family wellbeing guidance. They are not therapy, diagnosis or medical advice, and they are not a substitute for support from a professional who knows your child.