How to Run a Shared Kitchen Without the "I Thought You Bought Milk" Fight
Shared kitchens waste more food than solo ones, for structural reasons. Here's a household food system that works for families, couples and flatshares.
Two people come home with milk on the same evening. Four days later, one of those bottles goes down the sink.
The reverse happens just as often: nobody buys milk, because each person assumed the other one had. Somebody makes a special trip. Somebody is mildly annoyed about it.
This isn’t a communication problem in the way it’s usually framed — it’s not solved by “just talk to each other more.” It’s a structural problem. Shared kitchens waste more food than single-person ones, per person, and the reasons are mechanical. WRAP’s UK research consistently finds that households with children waste more than households without, often linked to meal changes and overbuying. Every additional person in a kitchen adds another independent shopper, another set of preferences, and another gap in the shared picture of what’s already in the fridge.
The fix is a small amount of structure. Here’s what actually works, and what to use depending on whether you’re a family, a couple, or four people who found each other on a flatshare site.
The four ways shared kitchens leak food
Before fixing it, it’s worth naming what’s actually going wrong. In most households, it’s some combination of these.
1. Nobody owns the inventory
In a one-person kitchen, one brain holds the model of what’s in the fridge. Imperfectly, but consistently.
In a four-person kitchen, four partial models exist and none of them is authoritative. You know about the yoghurts because you bought them. Your partner doesn’t, so they buy more. Neither of you knows about the leftover rice because your teenager made it at 11pm.
The result isn’t just duplication — it’s that food nobody has a mental model of is food nobody plans a meal around. Unplanned food gets eaten last, if at all.
2. Diffusion of responsibility
The bag of spinach at the back of the drawer belongs to everyone, which means it belongs to no one. In a solo kitchen, you see it wilting and it’s obviously your problem. In a shared kitchen, three people notice it, three people register a mild sense that someone should do something, and it gets thrown away by whoever eventually cleans the fridge.
Classic bystander dynamics, applied to vegetables.
3. Preference mismatch
WRAP’s food waste diaries found that “personal preference” — someone simply didn’t want to eat it — accounts for around 22% of the food households throw away, on a par with food that had actually spoiled.
That’s disproportionately a shared-household phenomenon. Someone buys a vegetable with genuine enthusiasm; nobody else in the house will touch it. A child goes off a food they liked last month. Somebody’s plans change and Wednesday’s dinner is now nobody’s dinner.
4. The plan and the reality drift apart
One person meal-plans and shops for seven dinners. Two of those dinners don’t happen, because someone worked late, someone else ate out, and Thursday turned into a takeaway. The ingredients for the two ghost dinners sit in the fridge, becoming steadily less appealing, until they’re bin material.
The more people in the household, the more the schedule fluctuates, and the more the plan diverges from reality.
The system: one source of truth, and three rules
Establish one shared list — and make it the only one
Everything else depends on this. One place, visible to everyone, that reflects what the household actually has and needs. Not “we all just tell each other.”
The failure mode is having several half-lists: a note on your phone, a magnet pad on the fridge, and a message you sent yourself. If a list isn’t the definitive one, people stop trusting it, and once people stop trusting it they revert to memory, which is where the second bottle of milk comes from.
What it needs to be:
- Accessible to everyone, from wherever they are. A fridge whiteboard fails the moment someone is standing in a shop three miles away, which is precisely when it’s needed.
- Editable by everyone. If one person is the gatekeeper, the list is a bottleneck and people route around it.
- Live. If two people are in different shops at the same time, both need to see the same state.
A shared note in your phone’s notes app is a legitimate starting point and it’s free. It covers the shopping list half of the problem. What it doesn’t cover is the inventory half — what you already have, and what’s about to go off — which is the half that actually prevents waste. That’s the specific gap Korgo’s Family tier fills: one household pantry, synced in real time, so scanning something into the fridge means everyone sees it immediately, and taking the last of something can push it straight onto the shopping list.
The technology matters less than the principle: one list, everyone can see it, everyone can change it.
Rule 1: Agree a staples list, and only buy staples when they’re on it
Sit down once, for ten minutes. Write down the twenty or thirty things your household always has: milk, eggs, bread, pasta, rice, tinned tomatoes, onions, butter, coffee, whatever yours are. Agree roughly how much of each you want in stock.
Then the rule is simple: staples get bought when the list says they’re low, not when someone notices them in the shop.
This kills the duplicate-buying problem almost entirely, because duplicate buying is nearly always someone acting on an uncertain memory in the middle of a shop. Replace the uncertain memory with a list and the behaviour stops.
The corollary matters too: if it’s not on the list, don’t buy it. This is the harder half, especially for anyone who finds supermarkets interesting.
Rule 2: Perishables get one owner
Every perishable that isn’t a staple should have a person attached to it.
If you bought the fennel because you had an idea about fennel, you’re responsible for the fennel. Not in a punitive sense — just that “someone will use it” is exactly the assumption that ends with fennel in the bin.
Two things make this work in practice:
- Say what it’s for when you buy it. “I got salmon for Thursday” is a complete transfer of information. The salmon now exists in everyone’s model of the week.
- Have an amnesty. If you’re not going to use it by day two, say so, and someone else can claim it or it goes in the freezer. The failure mode isn’t buying something you don’t use; it’s not admitting it in time.
Rule 3: One ten-minute reset per week
Pick a time — the evening before the big shop is ideal. It’s ten minutes and it’s the highest-leverage ten minutes in the household week.
- Open the fridge and actually look. Front to back, drawers included.
- Pull everything with fewer than three days left into a single “eat me first” box at eye level.
- Build the next few days’ meals around that box, before deciding anything else.
- Freeze the things that won’t make it. Half a loaf, herbs, the last of the mince.
- Then write the shopping list, in that order — after you know what you have, not before.
The sequencing is the whole trick. Most households write the list first and check the fridge afterwards, if at all, which guarantees they buy things they already own.
Different households, different rules
Families with children
The specific problem is unpredictability: kids’ preferences change without notice, and school and activity schedules shift meals around.
- Plan four dinners, not seven. The remaining nights are leftovers, freezer stock, or something easy. This absorbs the variance instead of fighting it. Households that plan every night rigidly waste the most when the plan breaks.
- Involve the kids in the “eat me first” box. Children are unexpectedly good at treating “what can we make from this?” as a game, and it makes the food visible to more people.
- Serve less, offer seconds. WRAP’s diary research found that “too much cooked or served” is the single biggest cause of household food waste, at around 25%. Plate waste is unrecoverable — food scraped off a plate can’t be saved. Food left in the pan can.
Couples
Usually the most fixable, because two people can hold a shared model reasonably well — they just need a tie-breaker.
- Decide who shops, or split by category. The worst arrangement is “whoever’s passing,” because that’s precisely how you end up with three jars of the same thing.
- Say the meal out loud. “I’m doing the chicken tonight” prevents someone else from starting on the same ingredients.
Flatshares
The hardest case, because there’s no shared budget and food ownership is contested.
- Separate genuinely shared items from personal ones. Shared: oil, salt, pepper, condiments, cleaning stuff, maybe milk. Personal: everything else. Trying to share all groceries in a flatshare almost never survives contact with reality.
- Give shared staples a fixed shelf, and split the cost on a simple rotation — one person buys the shared stuff each month.
- Label personal perishables with a name and a date. It looks petty; it prevents 90% of flatshare food arguments.
- Run an amnesty shelf. One shelf where anything unlabelled is fair game. This is how the fennel gets eaten instead of composted.
Making it stick
Every household system dies the same way: it becomes more effort than ignoring it.
So the design constraint is that the correct behaviour has to be the easy one.
- Attach logging to unpacking. The moment food comes out of the bag, it goes on the list. Never as a separate task later.
- Don’t build a system that needs one champion. If it only works when one specific person maintains it, it will fail during their busy week, and it won’t come back.
- Make restarting cheap. After a chaotic fortnight, the list will be wrong. Don’t rebuild it from scratch. Start from tonight’s shopping and let it become accurate again on its own — most kitchens turn over in about two weeks.
- Measure something. Even loosely tracking what gets binned changes behaviour, because it turns a vague guilt into a specific fact: it’s the bagged salad, every week, without fail. Then you stop buying bagged salad and you’ve solved it permanently.
The short version
Shared kitchens waste food because there’s no single source of truth, no clear ownership of perishables, and a plan that drifts from reality.
Fix all three with: one shared list everyone can see and edit. Staples bought from the list, not from memory. Perishables with an owner. Ten minutes on the fridge before the shop.
The milk argument disappears not because everyone communicates better, but because there’s no longer anything to be uncertain about.