Category posts
Data and analytics
Editorial

Working with data helps companies across the board to unlock their potential and become more productive and better at making decisions. However, making people in the team and company rely on data involves a lot of work. Product managers must often set a strategy, reinvent processes, and change organizational behavior.
(more…)Editorial

Data is an essential part of the work of every product manager. It helps to form and validate hypotheses, provide more insights about user behavior, and make better decisions and track product changes.
But the misuse of data can be harmful. One important example is selecting only data that confirms a particular hypothesis and ignores relevant contradictory evidence.
(more…)Editorial

Data is a key part of product management. We gain our intuition by looking at data. We come up with hypotheses based on our observations of data. We test and validate these hypotheses using data. And we make key product decisions and monitor and track changes in data. In a nutshell, data helps us go from ideas to facts to decisions.
However, working with data is also wrought with pitfalls that every product manager should avoid. Data can sometimes be misleading or incomplete. It might not tell the whole truth and lead you in the wrong direction. And it might amplify your own erroneous assumptions.
(more…)Editorial
Teams that don’t use experiments usually think they know their product, its users, and what they should do to achieve their intended results. In contrast, teams that use experiments acknowledge that they know very little about their product and users. This way of thinking presents the team with a unique opportunity to improve. Our former student Anton Rifco dived deeper into the topic to tell our readers more about it.
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
Failing fast and often will help you learn from your mistakes sooner rather than later. This is an advice you hear often from successful product managers. But what you hear less often is that not every failure is a successful learning experience.
A product’s success is largely dependent on coming up with a hypothesis and designing the right tests. Without those elements, you might draw the wrong conclusions and steer your project in the wrong direction.
In his guest post for the GoPractice blog, Ethan Garr, VP of product at TelTech.co, shares some hard-earned experience in product testing. Through concrete case studies, Ethan shows us how to avoid key pitfalls when designing tests for hypotheses.
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
You can make many mistakes while designing, running, and analyzing A/B tests, but one of them is outstandingly tricky. Called the “peeking problem,” this mistake is a side effect of checking the results and taking action before the A/B test is over.
An interesting thing about the peeking problem is that even masters of A/B testing (those who have learned to check if the observed difference is statistically significant or not) still make this mistake.
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
When conducting experiments, teams usually include all the active users in their tests, or sometimes they tend to add all the new users who join the app during this test. So when calculating the metrics for different test groups, all the data from the moment the A/B test kicks off is taken into account.
Today I’ll talk about how you can reduce the time required to get the signal on the change you are testing in a product. You can do that by changing the process of adding users to the A/B test, and in this essay I will show you how you can do it.
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
Let’s start with a practical task.
Say a company’s management wants to allocate significant resources to the development of infrastructure that would increase their app’s speed. The hypothesis is that increasing the speed of the app will have a positive effect on the user experience and the key metrics.
Think of an experiment (an A/B test) to validate this hypothesis.
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
Creating the app of your dreams can be a daunting challenge. But an even greater challenge is making sure your users find and experience its value. To do this, you need to have visibility on how users navigate through your app and interact with its features.
This is where analytics and event-tracking platforms come into play.
Analytics help you answer important questions about your users such as what do they like about your app, where are they struggling, which features need improvement, which features are hindering the user experience, and many more.
The foundation of analytics is data collection. Every analytics platform comes with a software development kit (SDK) that you can integrate into your app to send events. Developers add code that calls special application programming interfaces (API) in the locations where an event must be fired (for example, when users launch the app for the first time or when they send a message). If event logging is set up poorly, you will be blinded when working on your product, or you will work with erroneous data, which in my opinion is even worse than not having any data.
In this article I will be talking about the following:
- Common mistakes in setting up analytics for mobile apps
- The right approach to integrating analytics in mobile apps
- Some hacks that will allow you to use data more efficiently
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Oleg Ya
The general perception is that data analytics and data-driven product management is more suited for business applications, social media apps, and communications platforms. But the reality is, any kind of product can benefit from a data-driven perspective.
One of the domains where the value of data is often underestimated is games.
In my experience, most teams working on mobile games don’t fully use the potential of data. They tend to track topline metrics, measure effectiveness of paid marketing campaigns, analyze the impact of product changes all while running meticulous AB tests. This may sound like enough, but it really isn’t. Not if your goal is to climb onto the top of the grossing charts and stay there.
There are many more ways how data can increase your chances of building and operating a successful mobile game. The key is to stop thinking of data as a way to look back at what you have done, but instead start using data as a tool that can help you make decisions, decrease uncertainty and remove main product risks as early as possible.
In this post, I will walk you through a few examples of how data can drive key product decisions at different stages of product development cycle. But first, let me tell you a story…
Test your product management and data skills with this free Growth Skills Assessment Test.
Learn data-driven product management in Simulator by GoPractice.

Other content series
that you might find useful
- Addressing user pain points vs solving user problems better
- Product manager skills: evolution of a PM role and its transformation
- Product metrics, growth metrics, and added value metrics
- Customer retention levers: task frequency and added value
- How to measure the added value of a product
- Should a product be 10 times better to achieve product/market fit?
- Product/market fit can be weak or strong and can change over time
- Two types of product work: creating value and delivering value
- What is the difference between growth product manager, marketing manager, and core PM
- When product activation matters and you should focus on it
- User activation is one of the key levers for product growth
- The dos and don’ts of measuring activation
- How “aha moment” and the path to it change depending on the use case
- Slack vs Teams vs Workplace: the intriguing dynamics of the work messenger market
- How the “Slack vs Microsoft Teams” race evolves as the world switches to remote work
- How Revolut Trading was built. The importance of industry expertise and the balance of conservative and new approaches
- The values and principles of Wise. Key ideas from the Breakout Growth Podcast by Sean Ellis
- How to calculate customer Lifetime Value. The do’s and don’ts of LTV calculation
- How to calculate unit economics for your business
- Guide to ARPU: formula, calculation example, LTV vs ARPU
- Experiments where you make your product worse – the most underrated product manager tool
- Why your A/B tests take longer than they should
- Peeking problem – the fatal mistake in A/B testing and experimentation
- Mistakes in A/B testing: guide to failing the right way
- Designing product experiments: template and examples
- To reduce your product’s churn rate, first find out why users stay
- How to estimate the revenue, downloads and audience of a competitor’s app?
- What is product/market fit and how to measure PMF
- How engagement metrics can be misleading
- How to forecast key product metrics through cohort analysis
- Cohort analysis. Product metrics vs growth metrics
- How to move from marketing to product management?
- Key data skills for product managers: experienced PMs sharing their thoughts
- Data mistakes to know and avoid as a product manager: experienced PMs sharing their thoughts
- Data cherry-picking to support your hypothesis. What is it? Why is it bad?
- How can PMs encourage more teammates to use data?
- Metrics to focus on before and after product/market fit. How to better understand your product at different stages?
- How to establish effective collaboration between product managers and data analysts
- How to increase the effectiveness of your product analysts
- Why every team member should know the key product metrics
- How to move from marketing to product management?
- Key data skills for product managers: experienced PMs sharing their thoughts
- Product manager skills: evolution of a PM role and its transformation
- What is the difference between growth product manager, marketing manager, and core PM
- Rolling retention, Day N retention, and the many facets of the retention metric
- Long-term retention – the foundation of sustainable product growth
- Errors in calculating ROI and unit economics. Impact of attribution models and incrementality on the ROI calculation of marketing channels
- Traffic attribution models. Why attribution models need to change along with growth channels, product, business objective and external environment