//pragmatic leaders

What Is Critical Thinking and Problem Solving?

Reading time
5 min
Section
Introduction to Critical Thinking
5 min left0%
what is critical thinking and problem solving?0%
5 min left
Critical thinking is the ability to analyse and evaluate information, arguments, and evidence in order to make informed and logical decisions.
Talvinder Singh, from a Pragmatic Leaders session on critical thinking

Critical thinking is not just a buzzword — it is the fundamental skill that enables you to make well-informed decisions in the face of complexity and uncertainty. It means analysing information rigorously, questioning assumptions, and using logic rather than emotion or bias to reach conclusions.

As a product manager, you will constantly encounter ambiguous situations with conflicting data and opinions. Your actual job is to cut through the noise and figure out what really matters. That requires deliberate, structured thinking.

The trap is treating critical thinking as passive acceptance of facts or opinions. Instead, it is an active process of interrogation: What’s the evidence? What else could explain this? What assumptions am I making? What perspectives am I missing?

The cost of skipping critical thinking

Imagine you are prioritising features for your product roadmap. Your stakeholders each have a strong opinion backed by anecdote. The CEO wants a flashy new dashboard. Sales want a quick demo feature. Engineering says the platform stability is at risk.

If you accept any one voice without critical evaluation, you risk shipping the wrong thing and wasting resources. The alternative is to apply critical thinking: gather data on user needs, evaluate technical risk, balance business impact, and make a reasoned call. This will not make you popular with everyone — but it will make your product better.

How to put critical thinking into action

Critical thinking is a process, not an event. It involves these steps:

1. Identify the problem or question clearly

Before you can solve anything, you must know exactly what you are solving. Vague or broad problems lead to wasted effort.

For example, "Our user engagement is down" is too broad. A clearer problem might be "Our new onboarding flow has a 40% drop-off at the account verification step."

2. Gather and evaluate evidence

Collect relevant data, feedback, and arguments. This could be product analytics, customer interviews, competitor analysis, or expert opinions.

Critically evaluate the credibility and relevance of each piece of evidence. Ask: Where did this data come from? Is it recent? Are there biases?

3. Consider multiple perspectives

No single viewpoint has a monopoly on truth. Seek input from diverse stakeholders — engineering, design, sales, customers.

This helps uncover blind spots and surface hidden assumptions.

4. Make a reasoned judgement

Use logic to connect the dots. Weigh the evidence and perspectives to reach a conclusion or decision.

Avoid jumping to conclusions based on incomplete information or gut feeling alone.

5. Reflect on the process

After the decision, review what worked and what didn’t. What assumptions proved wrong? What data was missing? How can you improve next time?

Reflection is critical for building your critical thinking muscle.

// thread: #product-critical-thinking — A PM applying critical thinking to a product crash issue
Neha (QA)We've seen crashes spike after the last release.
You (PM)Let's gather logs and user reports to identify patterns.
Rahul (Engineer)The crashes seem linked to the new payment feature.
You (PM)What other factors could be influencing this? Could it be device-specific or network issues?
Neha (QA)Mostly Android 11 devices on spotty networks.
You (PM)Good. Let's test the payment flow under those conditions and consider a rollback if needed.

Critical thinking overlaps with analytical thinking but is broader:

  • Analytical thinking breaks down complex problems into parts, looking for patterns and relationships.
  • Critical thinking questions assumptions, evaluates evidence, and considers alternative explanations.
  • Deductive thinking moves from general principles to specific conclusions.
  • Creative thinking generates novel ideas and solutions.

Together, these skills form a toolkit for problem solving.

Examples of critical thinking in product management

Identifying new product opportunities

You spot a gap in the market: users struggle to track their expenses effectively. You gather customer feedback, study competitors, assess your team’s capabilities, and evaluate market size before deciding whether to build a budgeting feature.

Prioritising features

Your team has limited bandwidth and multiple feature requests. You collect data on user demand, revenue impact, and technical complexity. You consult stakeholders and use logical reasoning to rank features by value and feasibility.

Solving product issues

A new feature causes crashes. You gather logs, user reports, and test results. You question whether the issue is the code, integration, or external dependencies. You consider different perspectives — engineering, QA, customer support — and decide on a fix plan.

// exercise: · 15 min
Practice the critical thinking process

Pick a current problem or decision you face in your product work. Follow these steps:

  1. Clearly state the problem or question.
  2. Gather all relevant evidence you can find.
  3. List the key perspectives involved.
  4. Make a reasoned decision based on evidence and logic.
  5. Reflect on your process and note improvements for next time.

The role of questioning in critical thinking

Questions drive critical thinking. The right questions expose assumptions and gaps.

Here are examples you should ask regularly:

  • What data supports this claim?
  • Could there be alternative explanations?
  • What am I assuming here?
  • What biases might influence this perspective?
  • Who else should I consult?
  • What are the risks if I am wrong?
// scene:

Product prioritization meeting at a Series A fintech startup in Bangalore

CEO: “We need to launch the new credit scoring model ASAP. It’s our competitive edge.”

You (PM): “What evidence do we have that this model improves approval accuracy over the existing one?”

Data Scientist: “Preliminary tests show a 5% lift, but the sample size is small.”

You (PM): “What risks are there if the model underperforms in production?”

Engineering Lead: “It could lead to higher default rates and regulatory scrutiny.”

You (PM): “Let’s plan a phased rollout with monitoring and fallback mechanisms.”

This questioning ensures the team balances speed with risk management.

// tension:

Balancing urgency with due diligence

Common pitfalls to avoid

  • Accepting information at face value. Don’t trust claims without evidence.
  • Ignoring alternative viewpoints. One perspective rarely tells the whole story.
  • Jumping to conclusions too quickly. Take time to evaluate data carefully.
  • Letting emotions or biases drive decisions. Stay objective and logical.
  • Failing to reflect and learn. Reflection builds better judgement over time.

Critical thinking in the Indian product context

India’s diversity and complexity mean product decisions involve many stakeholders and ambiguous data. Critical thinking helps you navigate conflicting customer feedback, varied market signals, and fast-changing technology.

For example, Razorpay’s product managers must evaluate feature requests from merchants across industries and geographies, balancing technical feasibility with diverse user needs. Meesho’s PMs juggle vernacular content preferences and trust signals in tier-2/3 cities. Critical thinking is the compass that keeps the product team aligned and focused amid this complexity.

Test yourself: The feature prioritization dilemma

// learn the judgment

You are the PM at a Series B SaaS startup in Hyderabad. The CEO wants to prioritize a flashy analytics dashboard for investors. The sales team wants a quick demo feature for a large client. Engineering warns that platform stability issues are causing customer complaints. You have limited engineering bandwidth this quarter.

The call: How do you prioritize these competing demands, and how do you communicate your decision to stakeholders?

Your reasoning:

// practice

You are the PM at a Series B SaaS startup in Hyderabad. The CEO wants to prioritize a flashy analytics dashboard for investors. The sales team wants a quick demo feature for a large client. Engineering warns that platform stability issues are causing customer complaints. You have limited engineering bandwidth this quarter.

Your task: How do you prioritize these competing demands, and how do you communicate your decision to stakeholders?

your reasoning:

0 chars (min 80)

Where to go next

PL alumni now work at Razorpay, Meesho, Swiggy, Flipkart, and 30+ other Indian startups and enterprises.