Category posts
Data and analytics
Editorial

Data drives product management. Product managers rely on data for everything from creating an easy buying experience to determining if a product should even be developed. And while data is used to inform all aspects of managing a product, are there different considerations for using data for long-term strategy vs. daily decisions?
It turns out that the answer is yes. While there are many similarities, like needing to ensure success is clearly defined, for strategic decisions more context, expertise, and qualitative data is required. Data used for strategic decisions tends to be higher quality, take longer to collect, and be more expensive than data used for everyday decisions. Data mistakes, such as bias or incorrect benchmarking, are also more costly to the organization when they happen in the context of creating a strategy.
(more…)Editorial

A quantitative data-driven culture is generally seen as very positive. It’s great for understanding performance and tweaking strategy. Quantitative data is useful for reducing risk and can be used for decisions that need a high degree of certainty. These situations are usually high enough of a priority that adequate time is allotted to use data to verify various experiments before the decision is made.
But there can be very real downsides. Data alone isn’t particularly useful for big transformations or concepts that don’t exist in the market. Henry Ford, founder of Ford Motor Company, famously said, “If I had asked my customers what they wanted they would have said a faster horse.” Ford’s customers actually wanted a faster way to travel, but lacked the language and vision to describe an automobile. Ford had to make the leap from “faster horse” to “car.” Data cannot do that.
(more…)Editorial

Product managers or analysts will often say something like: “My analysis of the data shows that users who do action X are more likely to buy the premium version or become successful.” Based on this insight, they decide to invest time and effort into making more users do X.
But this is a classic example of assuming causation where there is only correlation. Maybe one thing really does cause the other—or maybe it’s just another case of two metrics happening to grow at the same time.
We have all heard the time-old caution: “Correlation does not imply causation.” It sounds obvious, almost too obvious. Yet time and again, even very experienced people, whether by accident or design, treat them as the same thing.
Here we will look at why it’s so easy to gloss over the difference between correlation and causation, how to prove causality, and why it’s important to keep all this in mind when working on a product.
(more…)Editorial

Product managers know that understanding their market and competition inside and out is vital to the success of their products. Comprehensive market knowledge tells you what problems your customers are trying to solve, what they want, and ultimately what new features or products to build. Knowing the competitive landscape helps to set your business apart, allows you to create a strategy to deal with new competitive developments, and helps to arm your sales team to win against the competition.
(more…)Editorial

When an organization says they are data-driven, they typically mean that they base decisions on data. But there can be vast differences with how data is used to make these decisions. Is data only being used to validate straightforward decisions? Are multiple sources of data combined with other factors to determine priorities like the features to be worked on next quarter? Or is an exploration of data being used to spark innovation and determine new strategy? Each situation requires different skills, tools, and ways of working with data to be successful.
This is why the concepts of data-informed and data-inspired are being added to the data-driven discussion; they allow for a more nuanced definition of how data is actually used in an organization. Data-informed and data-inspired decisions consider depending not only on data for clear-cut decisions, but on using data in conjunction with other important influences and to invent something new.
Some may argue that adding the terms data-informed and data-inspired to the data-driven discussion adds complexity and muddles the discussion around data. While that may be true in some cases, really understanding how to correctly use data based on a particular need is critical to creating products that customers love. In the end, the terminology isn’t as important as making sure you’re getting the most out of data.
(more…)Editorial

Product managers use data at the heart of their decision making. There are two types of data that they rely on: quantitative and qualitative. Quantitative data refers to numerical data that can be measured; examples include number of clicks, number of users, and monthly recurring revenue. Qualitative data cannot be counted, but instead describes traits or features such as ease of use, user likes and dislikes, and motivations behind user actions.
(more…)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.
→ Learn growth and realize the maximum potential of your product in Product Growth Simulator.
→ Join our discussion on LinkedIn. New topics to talk about every week.

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 user 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 user activation
- How “aha moment” and the path to it change depending on the use case
- How to find “aha moment”: a qualitative plus quantitative approach
- How to determine the conditions necessary for the “aha moment”
- Time to value: an important lever for user activation growth
- How time to value and product complexity shape user activation
- Product-level building blocks for designing activation
- When and why to add people to the user activation process
- Session analysis: an important tool for designing activation
- CJM: from first encounter to the “aha moment”
- Designing activation in reverse: value first, acquisition channels last
- User activation starts long before sign-up
- Value windows: finding when users are ready to benefit from your product
- Why objective vs. perceived product value matters for activation
- 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
- Correlation and causation: how to tell the difference and why it matters for products
- How product habits are formed and what dopamine has to do with it
- Hook Model: encouraging a product habit to improve retention
- Not every product is habit-forming, but all products can have loyal users
- 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
- 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 move from engineering to product management?
- Losing sight of real users and their needs behind the metrics. How can product teams avoid this?
- Quantitative vs qualitative data: what is the difference and when should you use one instead of the other
- Pros and cons of a data-driven culture
- Data-driven, data-informed, and data-inspired product decisions. What are the differences and when should you use each one?
- Using data to understand competitive and market dynamics
- Moving from a startup to an enterprise as a product manager
- The downsides of a data-driven culture
- Using data for strategic decisions
- 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
- How to move from engineering to product management?
- Product growth, reinvented: what growth hacking is (and isn’t)
- Moving from a startup to an enterprise as a product manager
- Product manager interview: real questions plus guide for employers and candidates
- 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