August 2026 · Field notes

The questions a house can't answer

A well-run household knows thousands of things. Almost none of them can be looked up. That gap is where the day actually goes.

The principal asks where the navy Prada blouse ended up. It was worn in the city in May, so it may still be in the apartment, or it went out for cleaning and came back to the wrong closet, or it is in the Florida house because that is where she was in June. Nobody is negligent here. The blouse exists, its location is knowable, and the house simply has no way to be asked.

So the question becomes work. Two texts to the housekeeper, a call to the other property, someone climbing a ladder in the storage room. Twenty minutes and three people to answer a question that has exactly one correct answer, and one that somebody in the household already knew.

The house is full of answers with no index

Run the same test on anything else and the pattern holds. How many bottles of the Barolo are left before Saturday? Who did we call the last time the pool heater went? When is the Range Rover's inspection due? Which of the guest rooms has the firm mattress? What did we spend on flowers last month?

Every one of these has a definite answer. Every one of them is documented somewhere, in a cellar book, a stack of invoices, a photo on a phone, a paper list taped inside a cupboard door. The information is not missing. It is unreachable, which in practice is the same thing.

Filing more carefully doesn't solve it. Neither does a better folder structure. The problem isn't where things are stored, it's that storage without retrieval only helps the person who did the storing, and only while they still remember doing it.

What it actually costs

The obvious cost is time, and it is worse than it looks, because a lookup usually interrupts two or three people rather than one. The housekeeper stops mid-task, the manager stops mid-something-else, and the principal waits.

The subtler cost is that the house learns not to ask. When a question takes twenty minutes, people stop asking small ones. Nobody checks the cellar before ordering more, so a case arrives that was already downstairs. Nobody checks the vendor history, so the pool company that did the good work last year gets replaced by whoever comes up first in a search. A household that can't be queried quietly gets worse at its own decisions.

And it lands hardest on new staff. An experienced manager compensates for all of this with memory. A new hire has none, so every small question becomes a large one, and their first months are spent asking colleagues things the house should be able to answer on its own.

A house you can ask

The standard worth aiming at is simple. Anyone with the right permissions should be able to type a plain question and get the answer in a few seconds. Not browse to it through a menu. Not know in advance which module it lives in. Just ask, the way they would ask a colleague who happened to know.

That only works if two things are true. The house has to be written down in one place rather than scattered across apps and paper. And that one place has to be searchable across everything at once, so a question about a blouse and a question about a boiler go into the same box.

Get both right and something changes in the texture of the day. The interruptions stop. The small checks start happening again, because they're cheap. And the twenty-minute hunt for a navy blouse becomes what it always should have been, which is a five-second look at a screen.

← Back to all notes