This may seem simplistic and very centrally controlled…but a large spreadsheet showing the taxonomy of an app, was very helpful.

Our team could “peek” into the taxonomy for other team’s apps. This helped engineers on our team get a feel for how other teams understood events. (How did they describe “action”, category, etc?)

One key thing that helped was having an initiative to help explain why we track, with a team that volunteered to present and explain how best to implement it.

This was at a Fortune 500 company, with lots of legacy software, so perhaps a smaller team with a younger app could get by with just a taxonomy and not a evangelistic analytics team.

Good luck!