The information was never missing. It only lived in one head.

When my son was under two, he had a fever and I needed to give him medication. The pediatrician had previously told us the correct dose, so somewhere in our household the answer existed.

My wife knew it. I didn't.

I wasn't prepared to guess a medication dose for a child that small, so I texted her and waited for the answer.

There was nothing dramatic about the mechanics of it. I had my phone, she was reachable, and eventually I got the information I needed. From the outside, it probably looked like an ordinary exchange between two parents.

But it stayed with me because of what would have happened if she hadn't been available.

I was his father. I was the adult looking after him. The medication was there, and we'd already spoken to a pediatrician about it. Yet the information that allowed me to use it confidently wasn't available to me unless I could reach another person.

The problem wasn't that nobody knew the answer. The problem was that only one of us did.

There's an important boundary here. If his fever had been higher, if I had been worried about his condition, or if getting an answer had taken too long, the right move would have been the pediatric on-call line or another appropriate medical service, not waiting indefinitely for a text message.

This isn't medical advice, and it isn't really a story about fever.

It's about something I began noticing all over our family life after that: information could technically belong to the household while still living almost entirely inside one person's head.

Once I noticed it, I started seeing the same problem in places that had nothing to do with fever.

It kept happening, not just once

The doctor's office was where the pattern became hardest to ignore.

I've taken our son to medical appointments several times and found myself sitting there while the doctor asked perfectly reasonable questions that I couldn't answer properly.

What medication does he usually take? What symptoms has he had before? What was he diagnosed with last time?

Sometimes I knew the answer. Sometimes I knew enough to give a partial one. And sometimes I realized, halfway through the question, that my wife would probably have answered immediately.

That's an uncomfortable position to find yourself in as a parent.

You're not absent. You're not refusing responsibility. You've done the practical part: made the appointment, got the child there, and you're sitting in front of the doctor. Yet part of the information needed for that appointment seems to have arrived with the wrong parent.

I could message my wife or look back through old conversations, but that only solved the immediate question. What bothered me was how often the same question came back.

If I had to ask once, fair enough. But when the same type of information repeatedly required another person to retrieve it for me, I started to realize that we hadn't really shared the knowledge. We'd just developed a reliable way for me to request it.

A conversation can solve a problem at 3:20pm on a Tuesday without making the next Tuesday any easier.

That became even clearer with the administrative side of our son's medical care.

On more than one occasion, I left an appointment without asking for something we later needed. I didn't request a medical clearance letter because I hadn't known the school would expect one. At other times, I failed to ask for prescriptions because I assumed the medicines were available over the counter.

Of course I should have known. That's exactly the point.

Somewhere along the way, one of us had learned how these situations worked: which documents the school expected, which medicines required a prescription, what we normally needed to leave the doctor's office with.

But nothing had turned that experience into information the other parent could use independently.

It can feel like you both know something just because you can both ask the person who actually does. That works until the person who needs the answer is standing at the school, the pharmacy or the doctor's office alone.

For us, it wasn't only medical information.

I once took our son out of the house in his pajamas because I didn't know where his normal clothes were kept.

That story makes me laugh now, but I also understand why stories like it can land badly. It would be easy to turn it into the familiar joke about the father who can't find anything without asking his wife. The joke isn't especially useful.

I genuinely didn't know where the clothes were, so I learned.

That should have fixed the problem. Instead, I discovered the next layer.

Once I knew which drawer contained his clothes, I realized I couldn't reliably tell some of his going-out T-shirts from the ones he slept in. To me, they looked much the same and were stored together.

That was oddly clarifying.

The first problem had been location: I didn't know where to look. The second problem was interpretation: I could now find the clothes, but the system still depended on knowledge I didn't have.

From the perspective of the person who already understands the setup, a drawer full of children's clothes is perfectly obvious. From the perspective of someone who doesn't, it may contain several invisible categories.

Digital systems can have the same problem.

You can give someone access to a document without giving them the mental map that makes the document useful. You can share a calendar while still being the only person who understands which events get added. You can make a spreadsheet available to both partners while one of them remains the only person who knows what the categories really mean.

The clothes drawer taught me something I wish I'd understood sooner: putting information somewhere both people can reach is only half the job.

The other half is making sure it makes sense to both of them.

The whiteboard, the app, the Notion page

Once I started thinking about the problem this way, the obvious response was to find a better place to put things.

A whiteboard in the hallway. A shared Google Calendar. A Notion page. Cozi. A dedicated family display such as Skylight.

All of these can give a household somewhere to store or display information. What none of them can decide for you is how your household will use that space.

Who adds something when it changes?

What belongs there in the first place?

When does a useful reference become clutter?

How do two people decide that a piece of information matters enough to preserve?

Those questions exist regardless of whether the container is a €2 marker on a whiteboard or an expensive screen mounted in the kitchen.

That was the part I had been overlooking. I kept thinking about the place where the information lived when I should also have been thinking about the rules around it.

A calendar can display information clearly, but it can't decide what our household considers important enough to record.

A whiteboard can make information visible, but it can't define which updates matter.

Notion can organize almost anything, but flexibility doesn't automatically mean you both understand it the same way.

The difficult part isn't always choosing the right software. Sometimes it's agreeing on what the system is for and making it understandable enough that either person can use it without needing a guided tour.

That also changed how I think about the phrase "shared system."

Shared access is easy to create. Send an invitation, share the document, add the other person's email address.

Getting both of you to actually treat it as yours is harder.

If I build the whole thing according to my logic, decide what belongs in it, create all the categories, and then announce that this is now "our system," I've technically shared it. That doesn't necessarily mean the other person experiences it as theirs.

The reverse is also true. If my wife has developed a perfectly efficient way of running part of our household but I can only use it by asking her what everything means, it isn't really independent access for me either.

The problem isn't whose system wins.

What I want is enough that either adult can handle ordinary household situations without turning the other into an information desk.

That's less exciting than finding the perfect app, but I think it's a more useful problem to solve.

The rule, and what happens when you break it

Eventually I needed a rule simple enough to survive normal family life.

The one I settled on was:

     If you had to text your partner to ask for this information, it belongs here.

I like it because it starts with something that has already happened.

I don't have to imagine every piece of information our family might someday need or spend a weekend building an enormous household database. I only have to notice the questions we are already asking.

What time does this activity finish? Which medicine did we use last time? Who is collecting him?

When one of those questions comes back repeatedly, it means I still need someone else to answer it.

The immediate answer can still happen by text. The difference is that, afterward, we have a choice: leave the information inside the conversation and ask again next time, or give it somewhere else to live.

The second part is a five-minute weekly review.

We check what changed, whether either of us had to ask for information that should already have been available, and whether anything important has become outdated or unclear.

The review exists because information changes quietly. A pickup time moves. A contact changes. A recurring activity switches day. The system can look perfectly intact while becoming less useful one stale detail at a time.

And we'll miss updates. That's part of the design too.

I don't want a household system that only works if two adults behave perfectly forever. If something falls out of date and one of us has to ask the other again, the response shouldn't be, "See? You never update this."

That would turn a household tool into a scorecard.

I'd rather answer the immediate question and then fix the missing information when there's a sensible moment to do it.

If the same failure keeps returning, that's useful information too. Maybe the category isn't clear. Maybe we're recording too much. Maybe the system is making a simple update harder than it needs to be.

The aim isn't to catch someone failing to maintain the system. It's to notice where the system itself is failing us.

I can't tell you that this rule and a weekly review will make a shared household system stick. I haven't proved that.

I've built them around problems I've experienced myself and around the broader adoption problem I wanted to address. I'm testing the approach because it makes sense to me, not because I have evidence that it guarantees a particular behavioral result.

What I can say from my own experience is that I've become much more aware of the difference between answering a question and removing the reason the question had to be asked.

For years, I mostly did the first. Now I'm trying to do more of the second.

Where this lives now

I eventually put these ideas into a spreadsheet I call the Household Wiki.

The name comes from the part of the idea I care about most: this shouldn't be one person's handbook for everybody else to consult. Both adults should be able to add information, correct it, and understand what they're looking at.

But building the spreadsheet actually made me more convinced that the file itself isn't the most important part.

The useful part is noticing when you keep having to ask.

The next time you message your partner to ask for a piece of household information, stop for a moment after you get the answer and ask whether you're likely to need it again.

If you are, give that information somewhere else to live.

It could be a spreadsheet. It could be a shared note. It could be the family calendar or a whiteboard if that genuinely works in your house.

The format matters less than whether both people can find and understand what they need.

If you want a starting point, I made the Standing Reference part of my system available as a free Household Reference template. It's meant for information that shouldn't require a search through old messages every time somebody needs it.

The full Household Wiki exists too, but I wouldn't begin by trying to move your entire household into a new system.

Start with one recurring question or one piece of information only one of you currently knows.

If one of you has a trip coming up, the household handover checklist is a good place to put that first one.

FAQ

More posts on Adoption & Habits