Field notes
Building an event dictionary that survives a release
Naming patterns and ownership rules that keep onboarding events readable after the next sprint ships.
An onboarding completion metric dies quietly when event names drift. One release adds onboard_done, the next prefers activation_complete, and the board chart loses continuity.
Prefer verb-object names tied to the user action
Names like profile_photo_saved or first_transfer_succeeded age better than abstract labels such as milestone_3. Tie each name to something a user does on a screen your team can still find six months later.
Assign an owner per event family
Someone in product or analytics should approve new onboarding events. Without that gate, well-meaning engineers invent parallel signals that never join the official completion path.
Version the dictionary with the release
When a release changes the path, note which events were added, deprecated, or redefined. Cloudmeshpoint clients who keep a dated dictionary spend far less time reconstructing history during an audit.