What is mental load? Definition and examples

The problem families face

The term 'mental load' is widely used but rarely precisely defined. Harvard researcher Allison Daminger's 2019 study identified four distinct phases in what she calls the cognitive labour of running a household: anticipating needs, identifying options, making decisions, and monitoring execution. It is the first three phases — invisible and cognitively demanding — that create the asymmetry. Loading the dishwasher is visible. Noticing that washing-up liquid is nearly out, remembering the brand you use, and adding it to the Tesco order while you're in a work meeting — that is mental load.

Without a name for this phenomenon, it cannot be discussed without sliding into personal accusation. 'You never help' lands badly because the partner often does do tasks — just not the cognitive groundwork that preceded them. Without a shared vocabulary to distinguish between physical care work, housework, and the cognitive management of the household, couples cannot talk about distribution as something structural. It stays personal, becomes an argument, and nothing changes.

• You read the school newsletter from Class Dojo and plan the week around it — your partner knows there is a newsletter but rarely opens it
• You know the children's shoe sizes and when the next pair will be needed — without it being written anywhere
• You track the next dentist appointment, know which vaccinations are due, and monitor whether a child has been ill long enough to need picking up

Common ways families try to solve this today

The most common approach is asking the partner to help more — and hoping it sticks. This works for some families in short bursts, especially when concrete tasks are named. But 'help' is not the same as ownership: the person asking retains the project manager role, including the cognitive responsibility for noticing what needs doing and delegating it. The asymmetry in cognitive management remains unchanged even when task distribution improves.

Another common move is a shared calendar or shopping list — Google Calendar, a whiteboard, a family WhatsApp thread. This makes some information visible, but doesn't touch the decision-making and monitoring phases. Who decides what goes on the weekly menu? Who checks whether the child actually took their packed lunch? These phases remain invisibly asymmetrical even when the calendar is shared.

• Asking for more help — creates task sharing but not ownership transfer
• Shared calendar — surfaces timing data but not the decision responsibility behind it
• To-do lists — work for visible tasks but don't capture the 'anticipate and identify' phases

A better system for family planning

Daminger's framework suggests making all four phases visible, not just the final task. That means writing down not just 'buy food' but 'decide the week's meals, write the shopping list, do the shop, check everything is there'. Once these phases are explicitly named, it becomes possible to see who is actually performing them — and to redistribute deliberately rather than letting structure decide. Eve Rodsky's Fair Play framework calls this 'holding the card fully': whoever holds a domain owns all its phases, not just the visible execution.

In practice, this means selecting some domains and transferring them completely. Not 'help with the children's activities' but 'you own planning, registration, kit, transport and follow-up for all the children's clubs and after-school activities'. It is cognitively heavy in the first month — because all the background knowledge must be transferred — but after the handover period, those domains disappear from the original owner's mental map.

• Name all four phases: anticipate, identify, decide, monitor — not just the last one
• Transfer domains fully, not individual tasks
• Allow a handover period: whoever takes over a domain needs time to build the background knowledge

Example of a weekly system

A concrete starting point: spend half an hour on Sunday evening naming all active domains in family life — food, school, health, activities, finances, travel, social commitments, home maintenance. For each domain: who performs the final phase (doing), and who performs the first three (anticipating, identifying, deciding)? This exercise surfaces the asymmetry as data rather than feelings — and creates the foundation for a distribution conversation.

When the week goes off-script — a sick child, a work crisis, a forgotten commitment — the minimum action is to name which domain broke down. Not 'everything is chaos' but specifically: was it meal planning, school logistics, health tracking? That makes the next distribution conversation far more precise, and prevents the default drift back to whoever was carrying it before.

• Sunday evening: name all family domains and who owns which phases
• Pick one domain to transfer completely — all four phases, not just the doing
• Allow 4-6 weeks before assessing whether the transfer is actually holding
• When something breaks down: name the domain, not just the feeling

How Zenframe helps

Zenframe Tasks is built around ownership per task rather than undifferentiated shared lists. You can create recurring tasks within a domain — say, everything related to the children's kit and activities — and assign them to one person. That makes 'who owns what' visible across the week, reducing the chance that ownership silently drifts back to whoever noticed it first.

The Planner module gives both parents visibility over the week — who has what on — without one person needing to hold it all mentally. Zenframe Assistant can import school week plans and add activities to the calendar, removing one of the typical 'anticipate and identify' steps that otherwise sit as invisible cognitive load with the default parent.

• Tasks: named ownership per recurring domain — not a floating shared checklist
• Planner: both parents see the week, reducing the need for one person to hold everything
• Zenframe Assistant: import school week plans directly — removes one cognitive step from the default parent's load

Practical tips families can start with today

• Write down every domain your family actively manages — just naming them makes the asymmetry visible as data.
• 'Help' is not ownership. Don't ask for help — transfer the entire domain, including planning and monitoring.
• Use Daminger's four phases as a checklist: anticipate, identify, decide, monitor. Ask who does the first three, not just the last.
• A shared calendar solves visibility for timing — but not who decides what goes into it.
• One domain list as a conversation starter turns the discussion into data rather than accusations.

FAQ