A new implementation can be exciting! It’s a fresh canvas to work with. A new client can present opportunities to try out ideas you’ve only thought of. These are just two of the scenarios that analytics implementation engineers are presented with that create the pull to collect all of the data.
While this can be fun, exciting, and provide unique sets of data, there are problems that can result from an over-engineered analytics data collection solution. Problems such as:
- Many times the solution designer has ideas for novel data that the analytics team doesn’t find useful so there is data going unused.
- Development time that could have been spent on other more useful work has been wasted.
- The team now has a complex solution that requires more maintenance than it should.
How can engineers and architects resist the urge to “tag everything”? What are steps that analytics teams can put in place to ensure the implementation work is focused on what is truly needed and valuable?
On this week’s episode of the 33 Tangents podcast, Jim and Jenn discuss their history with implementing analytics solutions and how they’ve fallen into this trap before. They talk through their thoughts on a less is more approach and how that applies to the current state of the digital analytics & martech space.
Subscribe & Review
Are you subscribed to our podcast? If you’re not, we want to encourage you to do that today. We publish fresh content every Friday morning and we don’t want you to miss a single episode.
And…if you’ve enjoyed this episode, we would be really grateful if you left us a rating and review on your favorite podcast platform. The reviews are extremely useful in helping new listeners find our podcast. Thank you!
