The quiet cost of unowned analytics properties
An event without an owner is a rumour. A property without an owner is worse, because it looks like structure. plan_type, role, source — fields that seem obvious until two teams fill them from different enums and a third team reads them as gospel.
The cost is not only wrong charts. It is the meeting in which two competent people discover they have been arguing about different worlds. One person’s “premium” is a billing flag. The other’s is a feature gate that was never turned off for a trial. App Analytics then becomes a blame ritual. The property, which had no steward, cannot speak.
Ownership here is not a RACI poster. It is a name in the tracking plan, a slack handle or an email, and a rule: no new values without a note. When that person leaves, the field is either reassigned in the same week or marked deprecated. Companies that skip the reassignment grow haunted columns — still populated, no longer meant.
We see this most clearly in United Kingdom product teams that scaled from a founding analyst to a constellation of squads. The analyst used to be the implicit owner of everything. Then they were asked to “enable” rather than govern. Enablement without a clerk is how source acquires fourteen spellings of “organic.”
The Signal Chamber spends a surprising portion of Day I on this dull census: which properties are loved, which are inherited, which are radioactive. Students sometimes want to skip to the north-star. The north-star is downstream of whether role means the same thing on Tuesday as it did on Thursday.
If you do one administrative kindness this quarter, print the property list, write a name beside each row, and schedule the awkward conversation about the blanks. The studio can teach the rest. It cannot invent a steward who does not wish to exist.