Every decision needs an address

After I took ownership of several connected features, the software did not change. The way questions travelled did.

Earlier, a request often began with a search for the right person. Support, Product and Project Management could all recognise part of the problem, but nobody was sure where it should start. Routing the question sometimes took longer than answering it.

Gradually, people began bringing those questions to one place. No process was announced and no organisation chart changed. The team had simply learned where the relevant context lived.

Ownership is usually discussed as accountability: who approves, decides or delivers. It also provides orientation. A clear owner gives a question an address.

That address should not make one person the permanent container for every answer. It should make the first step obvious, then connect the question to documents, decisions and other people who hold the rest of the context.

Without that starting point, work begins with navigation rather than reasoning. Expertise may already exist, but the organisation spends its energy locating it.

A decision needs an address because shared knowledge still needs a reliable entrance.