Sakshi Khilari
Masters Thesis · Research

Making invisible work visible

A masters thesis on the planning behind household work, and what has to be true before two people can talk about it.

Two people stand in the same kitchen looking at the same chore, and see completely different amounts of work.

Neither of them is wrong. One of them is counting something the other has no word for.

01The problem

Couples who care about fairness at home try to divide the chores equally. The usual approach is to think of everything physical around the house, doing the dishes, taking out the trash, cleaning, and keep track of that. On paper it's an even split. In practice, one person ends up doing more than the physical chores.

More than physical chores means the planning, coordinating, remembering and anticipating that make the physical stuff happen. That work is called , and it's missing from our chore charts, our tools, and our conversations.

INVISIBLE

remembers to defrost the chicken

cooks dinner

notices supplies before they run out

shops for groceries

monitors bills and due dates

pays the bills

sets the standard for a clean enough home

vacuums the house

Four chores, and the work that made each one possible

Cognitive work produces no evidence and leaves no trace, which is what makes it invisible. And because it's invisible, couples have nothing to point at and nothing to discuss.

Across this imbalance only ever came up in two situations: as ammunition during a fight, or not at all.

Couples who wanted a fair split were failing, because half of the chores were invisible.

So the question became: how do you make cognitive work count as real work in a household?

02The first approach

If the work needs to be seen, make it visible through recognition. (Spoiler alert: it failed.)

Recognition is what works for physical tasks. Someone does the dishes, someone else notices, and the effort is on the record. So I sketched two rounds of that same logic applied to the invisible half, and tested them with couples.

Both fail on the same asymmetry, from opposite ends. Logging charges the person already carrying the load a second time, for work they are already doing. Recognition asks the partner to notice something they have never been able to see, which is the reason the work is invisible in the first place.

And in testing, both turned into scorekeeping. Once there's a record of who did what, couples stop discussing the work and start counting it. That was true of everything couples already reach for, too.

All three start after the naming is done. None of them help a couple do the naming itself, and when I sat with people trying to log their own work, that was exactly where they stopped. They wrote down the chore, paused, and had nothing to add.

You can't acknowledge something you have no words for. Neither can you log it, split it, or argue about it fairly.

So the problem wasn't a missing feature. It was a missing conversation, and you can't design a conversation. You can only design the conditions that make one possible.

03What I found

So I went to find out whether this was really a language problem.

I asked three questions, across 8 interviews and 6 diary studies.

Nobody could name this work. Everybody recognized it the moment it was put in front of them.

04The framework

Five things that have to be true before that conversation can happen.

They describe what has to be true for two people to build a shared picture of the work, whatever form the thing takes.

  1. 01

    Design for replayability

    From the interviews

    Cognitive labor shifts with seasons, moves and circumstances, and awareness of it never landed in one conversation. It has to be something a couple can return to.

  2. 02

    Ground the conversation in concrete examples

    From the sorting activity

    Asked to define cognitive work, nobody could. Shown a specific example, everybody knew what it was. So put the examples in front of people first.

  3. 03

    Leave room for couples to build their own language

    From the tools couples already use

    Prescribed vocabularies stay clinical, because the words are borrowed. Give enough structure to start, then leave space for a couple to name their own house in their own words.

  4. 04

    Protect individual reflection before shared discussion

    From the diary study

    The couples who had practiced naming this alone described their partner's day with far more specificity. Reflection on your own has to come first, or the conversation has nothing to work with.

  5. 05

    Create a neutral entry point that separates the conversation from blame

    From the interviews, and from

    Invisible work surfaced two ways only: as an accusation mid-argument, or not at all. The way in can't sound like "we need to talk."

The guidelines are the thesis. What follows is one way to build them.

05The proof of concept

To find out whether the five conditions could be built into something, I built one.

A card-based conversation game for two people.

One partner draws a scenario and both read it aloud. Each of you places it on a 1 to 5 scale on your own side, hidden by the divider. Once you've both committed, the divider comes down. You don't have to land on the same number. You have to explain the one you chose, and hear why your partner chose theirs.

Nothing on a card says who does that task in your house. You are rating the work, not each other, which takes the competition out of it.

Each part of it is one of the guidelines, built.

An isometric drawing of the game: a board with a 1 to 5 track on each side, a standing divider between them, a draw pile of scenario cards, and two cards a couple has written on.
Hover a marker

The mechanic isn't invented. It is the sorting activity from my research, rebuilt so a couple can run it themselves.

06Reflection

Three things I took from this project.

  1. I tested the obvious answer before I committed to it.

    Recognition was the obvious answer, and it was the wrong one. I found that out early because I sketched it and put it in front of couples straight away, instead of waiting until I had the best possible version to test. Two rough rounds took two weeks. Building the polished version first would have taken most of the semester.

  2. I gave each study one question to answer.

    Across , no single study could have carried this. Each one answered one question and set up the next, and chaining small studies got me somewhere a single large one wouldn't have. It is how I plan research now, whatever the subject.

  3. I stopped taking "everything's fine" as an answer.

    Nobody I interviewed reported a problem. Had I taken that at face value there would have been no thesis. Now I treat a group who say nothing is wrong as a reason to look harder, not a reason to move on.

Nine households, none of whom thought anything was wrong. The work was real, it was uneven, and it had no name.

Five guidelines came out of it, and a game built to show they hold up.

Next project

From AI reasoning to human action

An agentic ERP reported what it had decided but never why. Four clicks down to one, shipped and in daily use.

or view other case studies