It's a wrap! ??

So we just wrapped our 5th anniversary Product Drive conference (don't worry - you can still sign up for replays if you missed it!) - and it was a mind-blowing amount of great content.

Over 6000+ product people (??) signed up online and 230+ live - so there was obviously something special to it. Apart from a fantastic time with you (photographic evidence here!), our team, the amazing guest speakers - Maja Voje , the author of the Go-To-Market Strategiest, ?Kevin O'Sullivan - our own Head of Product Design , and the few near-heart attacks that only organizing events can bring, it gave me a ton of food for thought that I will soon marinade and spoon feed you over the next couple of weeks.?

I know we've had tons of pizza - but if you didn't make it in person, I hope you're still hungry for knowledge!

It's a hard choice when you had talks from folks like Mary Cagan or Dan Olsen, but since I'm totally unbiased (ekhm) I will start with Kevin - because it's he spoke on a topic that I really, really care about (and kinda pushed him to make a presentation on).?

Why does Product Analytics SUCK so much??

He didn't quite put it that way - but I did.? It's 2024 and most product analytics tools are still inefficient (require tons of engineering resources to set up - pass events - and maintain + are super-expensive if they charge by events), prone to error (ever tried GA4? I know, I know, a rhetorical question) and hard to act on (or downright impossible - because it's either that the analytics tools don't have any tools to act on the insights, or that tools that would allow you to do something - don't actually provide any way to visualize or analyze the data for insights!)?

And that's why most product and marketing teams still make decisions that aren't exactly data-driven.? Even though being data driven and acting on product analytics is very important for both resource management, user experience, and revenue:?

And that comes at a price. Of mostly bad decisions...hence all the bad products and marketing we see. And tons of wasted engineering resources, useless growth experiments, and lost income.?

But it doesn't need to be like that.?

So how can you actually act on the data that you're collecting??

Here are a few quick tips:?

• Choose a solution that automatically captures all your user data (both quantitative = in-app events, and qualitative = feedback and session recordings) so you don't need to rely on your engineering resources (Userpilot ???)?
• Make sure your tool allows you and other teams in your organization (marketing, CS, CX etc) to bring their data through integrations and?visualize them with shared?dashboards - to create a single source of truth rather than silos (so common!)?
• Create a data-driven culture by e.g. scheduling weekly cross-functional?workshop sessions to review the key user metrics that correlate with retention and revenue (activation, product adoption depth, adoption of core features etc). Better yet - set up weekly alerts so everyone gets a copy of these data reports.?
• User ready-made report templates for these key metrics so you don't overcomplicate things!? (Userpilot ???)?

Watch the replay of Kevin's presentation to learn more about how to act on your product data!? And I promise to deliver a more in-depth review of the other talks next week - stay tuned!?

Emilia from Userpilot