Write the events before the tickets

Instrumentation survives when the blueprint exists before the pull request.

Abstract data visualization glowing on a screen

Teams that name events inside the pull request inherit whatever the UI component was called that week. Six months later, ‘tap_cta_primary’ and ‘start_checkout’ both claim the same moment, and nobody trusts the funnel.

Prefer intent verbs over widget labels. Put platform in a property, not the event name, so web and app stay comparable. Document required properties on the same day you invent the name.

A Product Event Blueprint spends its first days on one surface only—because a complete catalogue nobody owns is still a mess, just a larger one.

All notes Talk through a similar issue