Why Learn Data Science?

Your actual job as a product manager is to make decisions that create value — not just to gather opinions or chase every customer request. The trap is to treat unsolicited feedback as representative of all users. Most PMs fall into this because they lack an objective lens on who their customers really are and how they use the product.

Carefully collected feedback combined with other data gives you that lens. It moves you beyond the vocal minority to an evidence-backed understanding of your entire customer base.

This is what separates good PMs from great ones: customer feedback fuels your ideas, but customer data fuels your decisions. When you rely on both, your roadmap becomes well-rounded and more likely to succeed.

Feedback and data are complementary fuels — not substitutes

Customer feedback is invaluable for uncovering new ideas, pain points, and feature requests. But it is often noisy and biased toward the most vocal users.

Data, on the other hand, offers a quantitative and objective view of how all users behave. It answers questions like:

• Who uses which features?
• How often?
• What is the lifetime value of different customer segments?
• Which cohorts are churning and why?

When deciding between competing priorities, you can combine these inputs. For example, if several customers ask for an update to an existing feature, while others request a new one, you can look at the lifetime value (LTV) of the customers behind each request. This helps you prioritize the initiative that will deliver the most value to the business.

Later, you can monitor the impact of your decision using usage data and customer feedback to validate success or course correct.

You don’t have to be a “math person” or data scientist to use data effectively

A common excuse I hear is, "I’m not a math person," or "I’m not a data scientist." That is no longer valid.

Most modern analytics tools come with powerful but user-friendly dashboards. You don’t need to write SQL or do complex regressions to understand basic usage patterns and trends. Tools like Mixpanel, Amplitude, Google Analytics, and even Excel can surface clear, actionable insights.

According to a Harvard Business Review article, you don’t even need to be a “math person” to make smart data-driven decisions. A basic refresher on statistics is helpful, but you don’t need to go back to school.

Nate Silver’s advice is simple and practical: “Getting your hands dirty with the data set is far better than spending too much time reading about it.” That means exploring the data yourself, asking questions, testing hypotheses, and learning by doing.

If you prefer a textbook approach, many resources exist:

• Mind the Product’s analytics guide for PMs
• Big data fundamentals courses on Udemy, Coursera, and Cornell’s online platform

The point is: you can and should build your data literacy incrementally. You don’t need to become a data scientist, but you must become comfortable working with data.

The PM’s role is framing questions and interpreting results — not just crunching numbers

You will have quantitative analysts and data scientists on your team. Their job is to run the analyses and generate reports. Your job is to frame the right questions and interpret the results in the context of your product and customers.

Thomas Davenport’s 2013 article Keep Up with Your Quants lists six critical questions managers should ask their analysts to push back on conclusions confidently:

1. What was the source of your data?
   Is it complete and reliable? Are there gaps or biases?

2. How well do the sample data represent the population?
   Are you looking at all users or a subset? Does it reflect your target customer?

3. Does your data distribution include outliers? How did they affect the results?
   Are extreme cases skewing your averages or trends?

4. What assumptions are behind your analysis? Might certain conditions render your assumptions or model invalid?
   Are you assuming linear relationships or ignoring seasonality?

5. Why did you decide on that particular analytical approach? What alternatives did you consider?
   Could a different method reveal other insights?

6. How likely is it that the independent variables are actually causing changes in the dependent variable? Might other analyses establish causality more clearly?
   Is correlation being mistaken for causation?

These questions help you critically evaluate data findings instead of accepting them at face value.

The cleanest way to think about data science for PMs

Data science is a broad field with many technical skills — SQL, Python, R, statistics, machine learning, visualization, and more. But as a PM, you don’t need to master all of these.

Your focus should be on:

• Defining clear product questions and hypotheses. For example: Does introducing an onboarding video reduce time to first key action?

• Understanding what data you need to answer those questions. What metrics, events, or user segments?

• Knowing the tools that can get you the data. This might be running simple queries, using dashboards, or working with your analytics team.

• Interpreting the results to inform decisions. What do the numbers say? Are they conclusive? What’s the next step?

If you want to go deeper, basic familiarity with SQL and spreadsheet functions can help you explore data independently. Tools like Tableau and QlikSense provide visual analysis without code. For heavier lifting, your data engineering and analytics teams will support.

Product managers in India must build data fluency to compete

Indian startups and enterprises are rapidly adopting data-driven product management practices. The companies that win are those where PMs can combine customer insights with data confidently.

This is not about replacing intuition — it is about sharpening it with evidence. When you see a customer complaint, you look at the data: is this a widespread issue or a rare edge case? When you get a feature request, you check whether it aligns with strategic goals and user behavior.

Take Razorpay or Swiggy as examples: their PMs rely heavily on data to optimize user funnels, measure feature adoption, and prioritize roadmap items. Without data literacy, PMs get stuck in opinion wars or reactive firefighting.

Practical first steps to build your data skills

1. Start with your product’s existing analytics tools. Spend time exploring dashboards and reports. What metrics matter? What user behaviors can you observe?

2. Pair feedback with data before deciding. When multiple customers ask for something, check usage data and customer value before prioritizing.

3. Ask your analysts the six critical questions. Push back on conclusions until you understand the data’s limitations.

4. Take a short course or workshop on product analytics. Mind the Product and Pragmatic Leaders offer relevant resources.

5. Practice framing hypotheses and testing them with data. For example, “I believe adding a walkthrough video will reduce onboarding time” — then check the data before and after.

6. Learn basic SQL or spreadsheet functions to run simple queries. This helps you explore data independently.

Test yourself: Data-driven prioritization at a Series A SaaS startup in Bangalore

Where to go next

• If you want to master user research combined with data: User Research Methods
• If you want to learn how to translate data into product strategy: Product Vision and Strategy
• If you want to develop your data literacy step-by-step: Analytics and Metrics for PMs
• If you want to practice framing and analyzing data questions: Data-Driven Decision Making
• If you want to explore data visualization tools: Data Visualization for PMs