Essays
Designing for the person who inherits.
Every piece of collection software is designed for the collector. That is the obvious user, the one who installs it, the one who has opinions about it. But the collector is not the person the record has to work for at the moment it matters most.
That person has never opened the application. They are not interested in watches. They are dealing with a death, a solicitor, an insurer and a house, probably at the same time. They will give the record one attempt. If it does not answer them immediately, they will fall back on the only strategy available to a stranger holding valuable objects: sell everything, or box it up and defer.
Designing for a reader who will not persevere
This inverts most software instincts. Features that reward familiarity — dense views, configurable columns, filters that repay learning — are exactly wrong for a reader who has none and will acquire none. What that reader needs is a document: finite, ordered, printable, and comprehensible without any software at all.
It also changes what belongs in it. A collector wants totals, market values, cost basis, performance. An executor needs none of that and is actively harmed by some of it — a valuation typed in optimistically two years ago becomes, in the wrong document, a number somebody treats as authoritative when distributing an estate.
The uncomfortable conclusion
Once you take that reader seriously, you stop designing screens and start designing what leaves the screen. The application becomes a machine for producing documents, and the interface is scaffolding around it.
You also start withholding things deliberately. A document handed to an executor should not carry serial numbers or the access code to the safe, because it has no gate in front of it and no idea who will read it next. A document handed to a fellow collector should not carry what you paid. Different readers, different boundaries — and the boundary has to be decided by whoever built the document, not remembered by whoever exports it at a difficult moment.
Where the software fits — and where it does not
Watch Vault Archive produces documents with those boundaries fixed rather than optional, so the wrong figure cannot reach the wrong reader by accident. What it is not is a legal instrument. It records who a piece is meant for; it does not transfer anything to anybody. The instructions still have to exist somewhere legally effective, and that is a conversation with a solicitor, not a field in an application.
One thing worth doing today
Hand your current record — whatever form it takes — to someone who does not collect. Ask them one question: if I were not here, what would you do with this?
Their answer is the real specification, and it is usually not the one you had in mind.