Notes ·
Naming Events for Future Teammates
The person who named signup_complete_v2 will leave. Write names that survive handoffs.
Cryptic event names feel clever in the week you invent them. Six months later a new PM asks what checkout_funnel_x meant and nobody is sure whether it fired on intent or confirmation.
Prefer object-plus-action patterns that match the user-visible outcome: plan_selected, invite_sent, workspace_created. Avoid version suffixes in the name; put versioning in documentation and property fields instead.
Document the business meaning next to the technical name. A one-line definition in the taxonomy sheet saves hours of Slack archaeology.
If two teams disagree on a name, resolve it in the workshop—not in parallel tracking that forever diverges.