Blog · Use case
One shopping list and meal planning the household shares
A shared shopping list only works if adding to it is easier than remembering. Sivella keeps the pantry, the meal planning and the list in one place for the household, so whoever is near the shop buys what the house is short of and whoever cooks knows what is already in.
Food is the chore with the shortest feedback loop in the house. Get it slightly wrong and you find out at seven in the evening, standing in front of a fridge with three ingredients that do not combine.
It also fails in a specific way. Not through laziness, but through split information: one person knows what got used up, another knows what is planned for Thursday, and the shopping happens without either of them.
The list has to be where the thought is
Everybody has kept a list on the back of an envelope, in a note app, on the fridge. They all fail the same way. The moment you notice the olive oil is running low is the moment you are holding a pan, and the list is in another room, or on somebody else's phone.
A list that lives with the household rather than with a person survives that. Sivella keeps the shopping list alongside the pantry and the rest of the kitchen, so anything added is visible to whoever ends up doing the shop, and it does not matter which of you noticed.
The rule worth holding to is that adding an item must be trivially fast. Any friction and the item becomes a thing you intend to write down later, which means it becomes nothing.
Planning meals against what is actually in
Meal planning done in the abstract produces a beautiful week and a second shopping trip. Done against the pantry, it produces a shorter list and less waste, because you start from what is in the house and fill the gaps.
Sivella's kitchen holds the pantry, meal planning and the list together for this reason, and can suggest dinner rather than leaving you to answer the question cold at the end of a long day. The suggestion is a starting point, not an instruction. The value is not being asked to think creatively at the exact hour you are least able to.
Whoever cooks should not also plan
In most households the cooking and the deciding sit with the same person, and the deciding is the tiring half. Someone who genuinely does not mind cooking five nights a week may still resent it, because what they are actually doing five nights a week is running a small restaurant with no menu.
Splitting those two jobs is one of the cheapest changes a household can make. One person sets the week's meals, another cooks them. Neither has to do both. In Sivella both halves are visible to the household, so the person cooking on Thursday can see what Thursday is, and the person planning can see what was bought.
What this looks like in a normal week
The pantry gets updated when something runs out, by whoever notices. Meals for the week get set once, against what is already in, in about ten minutes. The list fills itself from the gaps, plus whatever anyone adds during the week. One shop covers it.
Nothing here is clever. It is the same work you are already doing, done once by the house instead of three times in three heads, with the result somewhere both of you can see it at four in the afternoon when it matters.