A gentle note: this library is general education about how people tend to think, feel and get along. It is not diagnosis, therapy or treatment, and it can’t know your situation. Where the evidence is thin, mixed or debated, each entry says so.
A household is a small team running a lot of recurring projects: meals, money, laundry, appointments, care. Workplaces have spent decades learning how teams share work without dropping things or blaming each other, and much of that learning transfers. The program borrows several of these tools on purpose. These entries explain where they came from, and what the research says about why they work.
How to read this page: entries summarize published research and name their sources. Notes marked This site’s idea are our own way of putting it into practice, not established science.
This site’s idea
Systems and teams and the Five Pillars
Systems and teams is Pillar II, Fix the setup, not the person. In you, it means seeing your habits and routines as a setup you can redesign rather than a flaw. Between you, it means clear owners, handoffs, reviews and agreements instead of blame. Several entries also help with Pillar I, See the whole load, by getting work out of one person’s head and onto a shared page.
The Five Pillars are this site’s own way of grouping these ideas, not a research finding. Each one borrows its name from a field. Here is what the pillars on this page mean, in you and between you and others:
I. See the whole load (borrowed from ledger accounting). In you: notice everything you carry, including the invisible, mental and emotional load. Between you and others: put it on one shared, fair page so nobody has to argue about whose work “counts”.
II. Fix the setup, not the person (borrowed from systems thinking). In you: see your habits and routines as a setup you can redesign, not a character flaw. Between you and others: use clear owners, handoffs and agreements instead of blame.
IV. Tune how you send and receive (borrowed from signal theory). In you: know your own wiring, pace and how you hear things. Between you and others: translate across different wiring and tone; a mismatch is tuning, not a moral failing.
V. Notice the quiet incentives (borrowed from behavioral economics). In you: spot the defaults and shortcuts that steer your own choices. Between you and others: see how unclaimed jobs drift to one person, and how fairness and thanks keep things steady.
RACI and one owner per job
Also known as: RACI, responsibility assignment matrix, responsible accountable consulted informed, ownership, one owner.
In a nutshell
RACI is a project-management tool that lists every task and marks who is Responsible (does it), Accountable (owns the outcome), Consulted and Informed.
This site’s idea The program uses a simplified version: every regular job gets one named owner.
Going deeper
In workplaces, RACI charts help clarify roles on complex projects, where confusion about who does what can lead to duplicated effort or dropped tasks. The key rule is usually that each task has exactly one person accountable.
At home, the same problem appears: “I thought you were doing it.” Jobs that belong to “both of us” or “whoever notices” are the ones most likely to slip, or to fall to the person with the lowest mess threshold. A single owner removes ambiguity.
This site’s idea The program’s version keeps it simple: for each regular job, write down who owns it (noticing, planning and doing) and who helps. Ownership can be changed on purpose, but not by drift. Agreeing on it means the arrangement is clear, not that it is perfect.
What the research says, and its limits
Responsibility assignment matrices have been used in project management since at least the mid-twentieth century; their exact origin is not well documented. RACI and variants (RASCI, DACI) appear in project-management guides. There is little direct research on RACI itself, but research on role ambiguity and diffusion of responsibility supports the underlying principle that clear individual ownership reduces dropped tasks and stress.
Also known as: role ambiguity, role clarity, unclear roles, who is responsible, role conflict.
In a nutshell
Role ambiguity means not being clear about what you are expected to do. Research consistently links it to stress, lower satisfaction and conflict, at work and plausibly at home.
Going deeper
Robert Kahn and colleagues studied role stress in organizations in the 1960s. They distinguished role ambiguity (unclear expectations) from role conflict (incompatible expectations, like being asked to do two things at once).
Unclear roles create friction in two directions. One person does something they thought was theirs, and the other redoes it. Or both assume someone else is doing it, and it doesn’t get done. Each outcome can lead to blame.
Clarifying roles, by writing them down, agreeing them together and reviewing them, is one of the simplest ways to reduce conflict. It works especially well for recurring tasks that nobody has explicitly discussed.
What the research says, and its limits
Kahn, Donald Wolfe, Robert Quinn, J. Diedrick Snoek and Robert Rosenthal published Organizational Stress in 1964. John Rizzo, Robert House and Sidney Lirtzman developed widely used measures in 1970. Meta-analyses since then have linked role ambiguity with job stress and lower satisfaction. Research in households is less direct, but related findings on the division of labor are consistent.
Also known as: diffusion of responsibility, bystander effect, someone else will do it, shared jobs slip.
In a nutshell
When responsibility is shared among several people, each person feels less responsible. This helps explain why jobs owned by everyone often get done by no one.
Going deeper
John Darley and Bibb Latané found that people were less likely to help in an emergency when they believed others were also present. Each person assumed someone else would act. They called this diffusion of responsibility.
The same dynamic appears in everyday life. In a shared house, the trash can that “everyone” should empty is often left overflowing. In a family, the task “we” need to do slips until one person, often the same one each time, gives in and does it.
Naming a specific person as responsible counters this. It isn’t about blame; it is about making sure someone clearly feels the job is theirs.
What the research says, and its limits
Darley and Latané published their studies in 1968. The bystander effect has been widely replicated, though a 2011 meta-analysis by Peter Fischer and colleagues found it is weaker in dangerous emergencies. The diffusion of responsibility principle is well supported in group research.
Also known as: social loafing, Ringelmann effect, doing less in groups, group effort.
In a nutshell
People often put in less effort when working in a group than alone, especially when individual contributions aren’t visible. This is called social loafing.
Going deeper
In the late nineteenth century, Max Ringelmann found that individuals pulled less hard on a rope when pulling as part of a group. Later researchers found similar effects for clapping, shouting and brainstorming.
Social loafing is reduced when individual contributions are identifiable, when tasks are meaningful, when groups are small and cohesive, and when people feel their effort matters to the outcome.
This site’s idea This supports the program’s approach of making contributions visible. It isn’t about surveillance; it is about making sure everyone’s effort, and everyone’s share, can be seen.
What the research says, and its limits
Bibb Latané, Kipling Williams and Stephen Harkins named social loafing in 1979. Steven Karau and Williams’ 1993 meta-analysis found the effect was reliable across many tasks and reduced when contributions were identifiable. It is one of the best-established findings in group psychology.
Also known as: psychological safety, safe to speak up, team safety, Edmondson, admitting mistakes.
In a nutshell
Psychological safety is a shared belief within a team that it is safe to take interpersonal risks, like admitting mistakes, asking questions or raising concerns. Amy Edmondson found it is central to how teams learn.
Going deeper
Edmondson began studying hospital teams and found something surprising: better-led teams appeared to report more errors. On closer look, they weren’t making more mistakes; they were more willing to talk about them. Mistakes that are hidden can’t be fixed.
Psychological safety isn’t about being nice or avoiding disagreement. It means people can speak up without fear of humiliation or punishment. High-performing teams often have both high safety and high standards.
At home, a similar principle applies: if admitting a forgotten job leads to criticism, people learn to hide mistakes. If it leads to problem-solving, people speak up earlier, and problems are caught when they are small.
What the research says, and its limits
Edmondson published her key study in 1999. Google’s Project Aristotle, an internal study reported in 2015–16, found psychological safety was the most important factor distinguishing effective teams. Research across industries has linked psychological safety with learning and performance, though most studies are correlational.
Also known as: retrospective, retro, review meeting, lessons learned, what went well, look back.
In a nutshell
A retrospective is a regular meeting where a team looks back at a period of work and asks what went well, what didn’t, and what to try next.
This site’s idea The program’s weekly and monthly look-backs follow this model.
Going deeper
Retrospectives became common in software development, particularly with agile methods. Norm Kerth, who wrote a well-known book on project retrospectives, proposed a “prime directive”: assume that everyone did the best job they could, given what they knew, their skills, the resources available and the situation.
The prime directive changes the tone of a review. It turns the question from “who messed up?” to “what about the situation made this happen, and what could we change?”
A simple household version: once a week or month, ask what went well, what was hard, and one thing to try. Keep it short, focus on systems, and end on something positive.
What the research says, and its limits
Kerth published Project Retrospectives in 2001. Retrospectives are standard practice in agile teams. Research on team debriefs more generally, including a 2013 meta-analysis by Scott Tannenbaum and Christopher Cerasoli, found that well-structured debriefs improved team performance by a meaningful amount on average.
Also known as: blameless postmortem, just culture, no blame, learning from mistakes, blame culture.
In a nutshell
Blameless reviews, common in aviation, healthcare and software, investigate what went wrong without assigning personal blame, so people can speak honestly. Just culture adds that accountability still matters for reckless choices.
Going deeper
When mistakes lead to punishment, people hide them. When they lead to learning, people report them. Safety-critical industries learned this the hard way, and developed blameless review practices.
Sidney Dekker and James Reason described “just culture”: a balance where honest mistakes are treated as learning opportunities, while reckless disregard is still addressed. Most errors happen because of system factors (fatigue, unclear procedures, poor design), not bad character.
This site’s idea The program’s monthly look-back uses this spirit: it reviews the system, not the people. A recurring problem is assumed to have a system cause, such as unclear ownership, overload or a gap in planning, until proven otherwise.
What the research says, and its limits
James Reason’s Human Error (1990) and Managing the Risks of Organizational Accidents (1997) are foundational. Dekker’s Just Culture was published in 2007. Blameless postmortems are described in Google’s Site Reliability Engineering (2016). Evidence comes largely from case studies and safety outcomes in industries that adopted these practices.
Also known as: Swiss cheese model, how mistakes happen, layers of defense, James Reason.
In a nutshell
James Reason’s Swiss cheese model pictures safeguards as slices of cheese with holes. Accidents happen when the holes line up. Most failures have several causes, not one.
Going deeper
Each layer of defense, like a checklist, a reminder, a second person, has weaknesses. Usually, a hole in one layer is caught by another. When holes in several layers line up, something slips through.
At home, a missed appointment might involve a calendar nobody checked, a reminder that went to the wrong phone, and a busy morning. Blaming one person misses the others.
The model encourages looking for several small fixes rather than one culprit: a shared calendar, a clear owner, a routine morning check.
What the research says, and its limits
Reason published the model in 1990. It is widely used in healthcare, aviation and engineering. Some safety researchers argue it is too simple for complex systems, but it remains a helpful teaching model.
Also known as: checklist, checklists, lists, surgical checklist, Gawande, to do list.
In a nutshell
Checklists help people remember routine steps under pressure. A famous surgical checklist study found fewer complications after its introduction, though later studies found more mixed results.
Going deeper
Checklists work because memory is unreliable, especially when tired, rushed or interrupted. They take routine steps out of memory and put them somewhere visible.
Atul Gawande’s The Checklist Manifesto popularised the idea beyond aviation. He emphasized that good checklists are short, focused on critical steps, and written with the people who use them.
At home, checklists can help with recurring routines: getting out the door, weekly shopping, handovers between people. They also help when handing a job to a new owner, because they capture the hidden steps.
What the research says, and its limits
Alex Haynes, Gawande and colleagues published the WHO Surgical Safety Checklist study in the New England Journal of Medicine in 2009, finding reduced complications and deaths across eight hospitals. A 2014 study in Ontario by David Urbach and colleagues found no significant improvement after province-wide adoption, suggesting implementation and culture matter as much as the checklist itself.
Also known as: transactive memory, shared memory, who remembers what, couples memory, Wegner.
In a nutshell
Couples and teams develop a shared memory system where each person remembers different things and knows who knows what. It is efficient, but can become lopsided.
Going deeper
Daniel Wegner noticed that couples divide up memory: one remembers birthdays, the other remembers where the passports are. Each knows the other knows, so they don’t need to remember everything.
This works well when it is balanced and when both people know the map. It becomes a problem when one person holds most of the household’s memory. They become the default for everything, and when they are unavailable, things fall apart.
External systems, like a shared calendar, notes or lists, act as backups, and make the load easier to share.
What the research says, and its limits
Wegner proposed transactive memory in 1985 and 1987. Andrea Hollingshead (1998) found couples performed better on memory tasks when they could use their established system. Research on teams supports transactive memory as a contributor to performance.
Also known as: cognitive offloading, external memory, lists, calendars, reminders, writing it down.
In a nutshell
Cognitive offloading means using external tools, like lists, calendars and reminders, to reduce the load on memory. It frees mental space and reduces the stress of holding everything in mind.
Going deeper
Evan Risko and Sam Gilbert described cognitive offloading as a natural strategy: people write things down, set reminders and use their surroundings to hold information.
For people carrying the mental load, offloading can be a relief. Shared offloading, like a family calendar or a shared shopping list, spreads the memory work so it doesn’t sit in one person’s head.
There is a small trade-off: offloaded information may be remembered less well internally. But for everyday household planning, the benefits generally outweigh this.
What the research says, and its limits
Risko and Gilbert published their review in 2016. E. J. Masicampo and Roy Baumeister (2011) found that making a specific plan for an unfinished goal reduced intrusive thoughts about it, suggesting that writing a plan down can quiet mental reminders.
Also known as: Zeigarnik effect, unfinished tasks, open loops, nagging thoughts, incomplete tasks.
In a nutshell
The Zeigarnik effect is the idea that unfinished tasks stay on our minds more than finished ones. The original finding has mixed replication, but planning seems to quiet the mental nagging.
Going deeper
Bluma Zeigarnik, working in the 1920s, reported that people remembered interrupted tasks better than completed ones. The idea became popular as “open loops” that nag at us.
Replications have been mixed, and the memory effect may be weaker than originally claimed. But later research by Masicampo and Baumeister found that unfinished goals do tend to intrude on thought, and that making a specific plan reduces this.
For households, this suggests that a long list of unowned, unplanned tasks can create constant background worry. Assigning owners and times can quiet it.
What the research says, and its limits
Zeigarnik published in 1927. Later reviews have found inconsistent replication of the memory effect, so it should not be treated as a reliable law of memory. A related finding, that people tend to want to go back and finish interrupted tasks (sometimes called the Ovsiankina effect, after another researcher in the same group), is often discussed alongside it. Masicampo and Baumeister published their planning study in 2011.
Also known as: Goodhart's law, Campbell's law, gaming metrics, keeping score, measuring.
In a nutshell
Goodhart’s law, in its popular form, says: “When a measure becomes a target, it ceases to be a good measure.” Numbers are useful for seeing patterns, but chasing them can distort behavior.
Going deeper
Economist Charles Goodhart made the observation about monetary policy in 1975. Anthropologist Marilyn Strathern later gave it its familiar phrasing. Donald Campbell described a similar law for social indicators.
This site’s idea The lesson for households is important. The program uses numbers, like battery scores and fairness ratios, to see patterns, not to win. If people start optimizing for the number (doing lots of small visible tasks to boost a tally, for example), the number stops reflecting reality and the point is lost.
This site’s idea This is why the program stresses that its scores judge the setup, not the person, and are for conversation rather than competition.
What the research says, and its limits
Goodhart’s original statement was in a 1975 paper; Strathern’s phrasing appeared in 1997. Campbell’s law dates from 1979. The phenomenon is widely documented in education, healthcare and business, where targets have produced unintended behavior.
Also known as: PDSA, plan do study act, plan do check act, continuous improvement, trying things out, Deming.
In a nutshell
Plan–do–study–act is a cycle for improving things through small experiments: plan a change, try it, look at what happened, then adjust. It comes from quality improvement in manufacturing and healthcare.
Going deeper
Walter Shewhart and W. Edwards Deming developed the cycle in the twentieth century. Instead of big overhauls, teams try small changes, measure results and learn.
At home, this takes pressure off decisions. Instead of arguing about the perfect chore system, try one for two weeks, then review. If it doesn’t work, adjust. Nobody has to be right in advance.
Framing changes as experiments also makes them easier to agree to. “Let’s try it for two weeks” is less threatening than “this is how it will be.”
What the research says, and its limits
Deming popularised the cycle from the 1950s. PDSA is widely used in healthcare quality improvement. A 2014 systematic review by Michael Taylor and colleagues found that many healthcare projects claiming to use PDSA didn’t follow it fully, suggesting it is easy to name and harder to do well.
Also known as: five whys, root cause, root cause analysis, why does this keep happening.
In a nutshell
The five whys is a simple technique from Toyota: when something goes wrong, ask “why?” repeatedly to move from the surface problem to an underlying cause. It is useful but can oversimplify.
Going deeper
Suppose the trash weren’t taken out. Why? Nobody remembered. Why? It wasn’t on anyone’s list. Why? We never assigned it. Why? It used to be done by someone who moved out. The fix is now clear: assign an owner.
The technique helps move conversations from blame to systems. Most recurring problems have causes in how things are set up.
Critics point out that real problems often have several causes, and asking “why” in a single line can lead to one convenient answer. It works best combined with other views, like the Swiss cheese model.
What the research says, and its limits
The technique is associated with Sakichi Toyoda and Taiichi Ohno at Toyota. It is widely used in lean management and healthcare. Safety researchers have criticized it for encouraging a single root cause where there are several, so it is best used as a conversation starter rather than a full analysis.
Also known as: forming storming norming performing, Tuckman, team development, new household, moving in together.
In a nutshell
Bruce Tuckman described teams moving through stages: forming, storming, norming and performing. It is a simple model, and it suggests early friction in any new team, or household, is normal.
Going deeper
When a new team forms, people are polite and unsure. Then differences surface (storming): disagreements about how to do things. Gradually, shared norms develop, and eventually the team works smoothly.
New households, such as moving in together, new housemates or a new baby, often go through something similar. The storming stage can feel alarming, but it is part of working things out.
The model also suggests that norms don’t appear by themselves. Talking explicitly about how things will work speeds up norming and makes it fairer.
What the research says, and its limits
Tuckman proposed the model in 1965, adding a fifth stage (adjourning) with Mary Ann Jensen in 1977. It is widely taught, but research suggests many teams don’t follow a neat sequence. Connie Gersick’s punctuated equilibrium model (1988) is one alternative. It is best seen as a helpful description rather than a precise theory.