Metadata
- Author: Franciska Dethlefsen
- Full Title:: Who Should Really Own Your Tracking Plan?
- Category:: 🗞️Articles
- URL:: https://amplitude.com/blog/tracking-plan-owner
- Finished date:: 2024-02-16
Highlights
The product team has defined the goals and metrics for this new feature and will have a view of what event tracking is needed to measure those metrics. The iOS, Android, and web development teams are responsible for instrumenting (and ideally testing) those events in the code and will have an opinion on what’s feasible. An analyst or analytics engineer is responsible for modeling the data and will care about its structure, and you might have several teams responsible for building reports and analyzing the data in several tools. In short, in data-led company analytics involves almost everyone. (View Highlight)
event tracking matters and without it you’re left in the dark. The reality is that for most teams analytics is an afterthought (View Highlight)
analytics tracking is just as important as the feature itself. No tracking, no release. (View Highlight)
The best ownership process happens when the product team acts as the ultimate owner. Product managers should be the main driver and ensure analytics tracking is part of every feature release (View Highlight)
Missing tracking? Fail the build. The notion of done needs to evolve to include analytics tracking as a part of every release. This doesn’t mean blocking releases right before launch, it means implementing a process that includes tracking considerations from the start. (View Highlight)