Event names that survive a redesign
Designers rename buttons. They should. Analytics should not invent a new journey every time the label changes from “Continue” to “Next”. In User Journey Mapping for Apps, the event name belongs to the decision, not to the copy.
Our rule is dull on purpose: object + intent + outcome, with no UI chrome. kyc.submit.succeeded survives a purple redesign. btn_continue_v3_tap does not. Properties may carry the visible label for debugging. The name that appears on the map must not.
Aliases are a debt instrument
When a redesign ships without a dictionary update, warehouses accumulate aliases. Cross-surface Journey Stitching will not start until those aliases are retired in writing. We have watched teams “stitch” checkout_start to bag_begin and call it one path. It was two names for the same intent, counted twice in a funnel that then looked like drop-off.
Who owns the name
Product proposes. Engineering implements. The studio mentor only accepts a name both sides can say out loud without looking at Figma. If they cannot, the map waits. That pause is cheaper than a year of fake steps. Funnel Grammar drills this until it is boring. Boring names are a feature.