Teams often add events because a template suggested them. Six months later the warehouse is full and product still cannot say why activation dipped last Tuesday.
A practical filter: write the decision sentence first (“We will change onboarding step 3 if completion falls below X”). Only then name the event and the properties that sentence requires.
Retired events deserve the same rigor. Mark them deprecated with an owner and a cut date so dashboards do not silently break when engineering cleans house.
cloudnodes reviews usually find that half the volume comes from three chatty screens and a debug flag left on. Cutting those frees attention for the dozen events that actually steer the roadmap.