Name events before you chart them
Dashboards fail quietly when the same click has three names. A short naming ritual saves weeks of cleanup.
Teams often ask for a funnel chart before they agree what a successful step means. That order produces three competing definitions of “signup complete” and a weekly meeting that argues about the chart instead of the product.
Start with a named dictionary: one event, one trigger, a short property list, and the decision the event supports. If nobody can name the decision, the event does not belong in the first release.
charts become useful only after the names stop drifting. Treat renaming as a product change with a changelog, not as a silent fix in a ticket.