There's a corner of our kitchen where systems go to die. Not literally, but in my head that's where I put them. The magnetic whiteboard with the chore chart that worked for exactly nine days. The Trello board I set up and color-coded and explained to Marcus, which he used twice. The shared Notes folder. The other whiteboard, smaller, that I thought might feel less formal. The app I won't name because honestly I don't remember which one it was, the one with the cute little household icons that I spent a Sunday afternoon configuring and Marcus opened once and said "hm, interesting" and that was the end of that.
Every single one of those systems had the same problem. I built it. Marcus tolerated it. And then it died.
Setting up a shared household system sounds like an organizational challenge. It isn't. It's a design challenge: how do you build something that actually works for two different people, not just the one who built it?
The death pattern is almost always the same. One person gets frustrated enough to build something. They put genuine effort into it. They introduce it to the other person, usually with some explanation of how it works. The other person agrees it makes sense. They use it for a while. Then life gets busy, the system requires maintenance, and the person who didn't build it stops updating it first. Then it's half-empty and hard to trust. Then it's ignored. Then the person who built it is doing everything themselves again.
I've been the builder in this cycle more times than I want to count.
The thing I kept getting wrong was thinking the problem was the tool. If the whiteboard failed, maybe an app would work better. If that app failed, maybe a different one. I was iterating on the wrong variable. The variable that actually matters is whether both people feel like the system belongs to them — not just whether they were informed about it.
A system one person designed is that person's system. Even if they made it for both of you.
What makes a system stick is different from what makes a system good. A system can be elegant and thorough and die in two weeks. A system can be barely adequate and last for years. The difference is usually adoption, and adoption comes from ownership.
Ownership means both people were in on the design. Not just told what was decided. Actually in the room when the decisions got made, including the boring ones. What do we even need to track? What format feels natural to each of us? What's the minimum version that would actually help? Those conversations are not exciting. They feel like a lot of talking when you could just be doing. But they're the difference between a system one person uses and a system both people use.
It also means both people have to maintain it. Not one person maintaining it for both of them. If updating the system becomes one person's job, you've just created another invisible task and handed it to the same person who was already carrying too many invisible tasks. That's not a failing on anyone's part — it's what happens when the system wasn't designed for shared maintenance from the start.
I want to be honest about something, because I've read a lot of content about household systems and it almost always glosses over this part. The system is not going to fix an unwillingness to engage. If both people don't actually want to participate in running the household, no app or whiteboard or chore chart is going to change that. The tool is not the therapy.
What I mean is this: both people have to actually want the thing to work. Not perform wanting it. Actually want it. That requires a different kind of conversation than "here's the new system I set up."
That conversation is about the load. What's actually involved in running this household. Who's tracking what. What falls through the cracks and who catches it. Most couples I know have never had that conversation explicitly. They've had arguments that were secretly that conversation, but not the actual version.
The reason it doesn't happen explicitly isn't usually that one person doesn't care. It's that the person carrying most of the load hasn't had a way to make it visible, and the other person genuinely doesn't know the full picture. Information asymmetry is the real problem — not motivation.
Once you've named it together, the system becomes much simpler to build, because you're both building it toward the same problem. And you'll both maintain it because you both understand what breaks without it.
We landed on something pretty simple in the end. Fewer categories than I would have chosen on my own. Less granular than my natural instinct. But Marcus helped design it, so he actually looks at it, and that is worth every bit of elegance I gave up.
We landed on something simpler than I would have built on my own, because Marcus helped design it, and that's why he actually uses it. Orbyt is what we built it in, and the thing that mattered most is that it's meant for two people from the start, not one person's system that someone else can technically access.