Category posts
Interviews with expert PMs
Editorial

While most product managers know that using data in their daily activities can have tremendous benefits, sometimes they find themselves in an environment where doing so is not easy. Perhaps they don’t have access to the data they need, the data is unreliable, or there is no support in place to incorporate data into their processes. These product managers are not in a data-driven culture.
A data-driven culture is when an organization embraces data to make decisions at all levels. The organization has the infrastructure and talent needed to collect, transform, and analyze data, along with reliable and trustworthy data sources. There is an importance on using data to support hypotheses and resolutions. Data-driven cultures embrace data and bake it into their everyday processes.
But a data-driven culture doesn’t just happen on its own. It needs both top-down and bottom-up support in the organization. Upper management must make the decision to invest in data and infrastructure while the teams must believe that using data in their daily jobs is beneficial. And while data enthusiasts in an organization can plant the seed, the entire organization’s support is needed for a data-driven culture to blossom.
(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 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

Where a product manager works affects their life, skills, and career. Startups and enterprises, i.e. large IT companies, are at opposite ends of the tech company spectrum, but they do have some things in common. Core product management skills are used in both environments, and both places have motivated, smart, and skilled professionals that want to help their customers. Both settings offer rich experiences that grow talent, however they differ in the types of skills that are most developed.
A startup teaches product managers how to move fast, tackle new problems, and wear many hats; an enterprise provides a chance to hone the product management craft and learn from successful experts in the field. Enterprises typically move slower than startups by design, and much of the extra time is spent communicating and negotiating with stakeholders. Because of the large user base, the impact of a product manager is usually broader than at a startup.
(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

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…)
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
- Testing user activation fit for diverse use cases
- When to invest in optimizing user onboarding and activation
- Optimize user activation by reducing friction and strengthening motivation
- Reducing friction, strengthening user motivation: onboarding scenarios and solutions
- How to improve user activation by obtaining and leveraging additional user data
- Tax/benefit framework for analyzing user activation
- How well do you articulate value during user activation? Check with the value communication framework
- How product teams get the “aha moment” wrong
- 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
- 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 design and run JTBD research interviews: guide and templates
- 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