Remove Customer Feedback Remove Technical Cofounder Remove UX
article thumbnail

Common technical hiccups in your product analytics that are easy to spot

Mixpanel

The good news is that many technical quirks tend to follow certain patterns that can be easily spotted—even by non-engineers. Here are four technical hiccups associated with corrupt event tracking data, how to spot them, and what to do about them. So how can you tell as a non-technical individual if this data is real or a stutter.

article thumbnail

My Biggest Takeaways?—?Being a Product Manager at an Early Stage Startup

The Product Coalition

He considered product managers to be on a spectrum from “librarian” who is focused on facilitating communication and coordination to “poet” who formulates product strategy based on customer insights. I saw the needs for UX research but we didn’t have a UI/UX team. The best product managers I know are flexible.

Startups 101
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Data thinking vs. product thinking

Mixpanel

UX design, branding, feature-set, nuanced differences in user perspectives, and a million other variables can impact (with varying levels of influence) whether our products get used or ignored. The ultimate outcome should be reality-aligned insights. Here’s how. Understand the role of data with nuance. But you’d be wrong.

article thumbnail

Mobile app event tracking: Telling the story of how your app works (or doesn’t work)

Mixpanel

When a user uses an app, they do stuff. And each of these kinds of events can be “meaningful” based on how they represent our users’ behaviors and expectations as they navigate the app experience. But events aren’t just limited to direct actions taken by users. Events tell stories about your users (and your app).

article thumbnail

Why it’s never too early to add product analytics to your app

Mixpanel

So it’s tempting to think the additional add-on of measuring user events in your code (i.e., implementing product analytics) is something that can wait until your team is bigger, until you have more users, or until you have more money. You know where users clicked and didn’t click, when they clicked, and in what order.

article thumbnail

Always implement analytics as part of feature development. Here’s why.

Mixpanel

They need to be actively aware of all of the requirements, why those requirements exist, and the nuanced value the feature intends to deliver to the user. Engineers are technical. They tend to process technical information better than less formal information, and that’s where analytics comes in.

article thumbnail

How to be the go-to engineer for product analytics

Mixpanel

The point is that some of these might be catchable by non-technical team members whose job it is to analyze the data, but a lot of cases could only ever be noticed by someone who understands how the implementation actually works on a technical level: an engineer like yourself. Keep the product folks technically up-to-date.