//pragmatic leaders

How to Put Critical Thinking in Action

Reading time
5 min
Section
Introduction to Critical Thinking
5 min left0%
how to put critical thinking in action0%
5 min left
Critical thinking is a systematic approach to evaluating information and arguments so you can make informed, logical decisions.
Talvinder Singh, from a Pragmatic Leaders session on critical thinking

Critical thinking is not just a buzzword — it is the backbone of every good product decision you will make. The actual job is a systematic process: you identify the problem, gather and evaluate evidence, consider multiple perspectives, make a judgement, and then reflect on how you arrived there.

Skipping any step leads to shallow or biased decisions. This lesson walks you through that process in detail, with real-world examples from product management.

Critical thinking is a systematic process, not a one-off skill

The critical thinking process has five key steps:

  1. Identify the problem or issue at hand. Clearly define the problem or question you are trying to answer. If you cannot articulate the problem, you cannot solve it.

  2. Gather and evaluate evidence. Collect relevant data, arguments, and information. Evaluate their quality and relevance critically.

  3. Consider multiple perspectives. Look at the problem from different angles — your team, stakeholders, customers, and even competitors. This expands your understanding and reduces blind spots.

  4. Make a judgement. Use logical reasoning and the evidence gathered to reach a conclusion or decision.

  5. Reflect on the process. Evaluate your thought process. What worked? What didn’t? What can you improve for next time?

// thread: #product-critical-thinking — Critical thinking process in a product team
Meera (PM)We’re seeing a 15% drop in daily active users. What’s causing this?
Rahul (Data)Initial analysis shows the drop started after the last feature release.
Anjali (Design)Could it be the new onboarding flow? User feedback was mixed.
Meera (PM)Let’s gather more data on user sessions and interview some churned users.
Rahul (Data)I’ll pull cohort data segmented by onboarding experience.
Meera (PM)Great. We’ll reconvene once we have more evidence and perspectives.

This dialogue shows the process in action — identifying the problem, gathering evidence, and including multiple perspectives before making any decisions.

Step 1: Identify and define the problem clearly

You cannot solve a problem you do not understand. The first step is to articulate the issue precisely.

  • Gather information through data, research, and conversations.
  • Identify root causes, not just symptoms. Break down complex problems into smaller parts.
  • Prioritize problems based on impact and urgency.
  • Define success criteria upfront — how will you know when the problem is solved?
// scene:

Weekly product review meeting at a Series A fintech in Bangalore

You (PM): “Our churn rate has risen by 8% this quarter. Let’s dig into why.”

Priya (Data Analyst): “User feedback points to poor transaction failure handling.”

Karthik (Customer Support): “Support tickets about failed payments have tripled.”

You (PM): “So the problem is not churn in general, but churn caused by transaction failures. Let’s focus there.”

// tension:

Defining the problem precisely to avoid chasing the wrong issues.

Step 2: Gather and critically evaluate evidence

Collect all relevant data and information. This can include:

  • Quantitative data: usage metrics, conversion rates, A/B test results.
  • Qualitative data: user interviews, support tickets, expert opinions.
  • Competitive intelligence: what are others doing?
  • Historical context: previous attempts and outcomes.

Critically evaluate the quality of evidence. Ask:

  • Is the data reliable and recent?
  • Are there confounding factors?
  • Does the evidence support or contradict your hypotheses?

Step 3: Consider multiple perspectives before deciding

Your own viewpoint is limited. Include others to broaden your understanding:

  • Team members with different expertise: engineering, design, data, marketing.
  • Stakeholders with varying priorities.
  • Customers who use the product daily.
  • Even skeptics or competitors for counterpoints.

This avoids groupthink and uncovers hidden assumptions.

// thread: #cross-functional — Gathering perspectives on feature prioritization
Neha (Design)Users are asking for better onboarding tutorials.
Vikram (Sales)Our enterprise clients want deeper analytics.
You (PM)Both are valid. Let’s weigh impact, effort, and strategic fit before deciding.
Meera (Engineering)Onboarding improvements require UI work, analytics is mostly backend.

Step 4: Make a judgement using logical reasoning

Use the evidence and perspectives to reach a conclusion.

  • Weigh trade-offs explicitly.
  • Avoid emotional or political bias.
  • Be ready to justify your decision with data and reasoning.
  • Recognize uncertainty and build in experiments to learn.
// learn the judgment

You are PM at a Series B SaaS startup in Mumbai. Customer feedback shows many users struggle with onboarding, but your sales team says enterprise clients prioritize analytics features. Engineering capacity is limited. You have to pick which feature to prioritize for the next release.

The call: Which feature do you prioritize and how do you communicate your decision to stakeholders?

Your reasoning:

// practice

You are PM at a Series B SaaS startup in Mumbai. Customer feedback shows many users struggle with onboarding, but your sales team says enterprise clients prioritize analytics features. Engineering capacity is limited. You have to pick which feature to prioritize for the next release.

Your task: Which feature do you prioritize and how do you communicate your decision to stakeholders?

your reasoning:

0 chars (min 80)

Step 5: Reflect on your thinking process and outcomes

Reflection is often overlooked but critical for growth.

  • Did your judgement solve the problem?
  • What evidence did you miss or misinterpret?
  • Were any perspectives ignored?
  • How can you improve your process next time?

Reflection builds your critical thinking muscle and prevents repeated mistakes.

// thread: #retrospective — Reflecting on a failed feature launch
You (PM)The new onboarding didn’t reduce churn as expected. Let’s figure out why.
Neha (Design)User testing showed confusion around the new flow.
Rahul (Data)Our A/B test had a small sample size — results may not be reliable.
You (PM)Next time, run a larger test and involve support earlier. We missed those signals.

Critical thinking applied: three real product management cases

Case 1: Identifying new product opportunities

You spot a gap in the market or unmet customer need.

  • Define the problem: What is missing or broken?
  • Gather evidence: Market research, customer interviews, competitor analysis.
  • Consider perspectives: Team input, customer feedback, sales insights.
  • Make a judgement: Is the opportunity viable and aligned strategically?
  • Reflect: What did you learn? How can you improve discovery next time?

Case 2: Prioritising product features

You must choose what to build next under constraints.

  • Define the problem: Limited resources, tight deadlines.
  • Gather evidence: Market demand, customer feedback, team capacity.
  • Consider perspectives: Stakeholders’ priorities, engineering input, user impact.
  • Make a judgement: Which features deliver the most value?
  • Reflect: Did the prioritization improve outcomes?

Case 3: Solving a problem during product development

You encounter a bug or user experience issue.

  • Define the problem: What exactly is broken or causing friction?
  • Gather evidence: Logs, user reports, expert opinions.
  • Consider perspectives: Developers, testers, users.
  • Make a judgement: What is the root cause and best fix?
  • Reflect: Could testing or processes be improved to prevent recurrence?

Practice applying critical thinking to a product problem

// exercise: · 15 min
Practice applying critical thinking

Choose a current product challenge you face or imagine one:

  1. Write a clear problem statement.
  2. List all data and evidence you have related to it.
  3. Identify stakeholders and perspectives you need to consider.
  4. Draft a reasoned judgement or decision.
  5. Reflect on your process: what assumptions did you make? What could you improve?

Repeat this exercise regularly to build your critical thinking muscle.

Analytical thinking supports critical thinking

Analytical thinking is a subset of critical thinking focused on breaking down complex problems into parts to understand relationships and root causes.

Critical thinking uses analytical thinking plus questioning assumptions, evaluating evidence, and considering perspectives to make judgements.

Together, these skills enable you to approach product problems systematically and logically.

The trap of rushing to conclusions

I have watched thousands of PMs make the same mistake: jumping to decisions before fully understanding the problem or gathering evidence.

The trap is optimizing for speed over quality. But a rushed decision often leads to rework, missed opportunities, or stakeholder distrust.

Take the time to follow the process. The time you invest upfront saves weeks of wasted effort later.

Test yourself: Prioritising under pressure

// interactive:
Feature Prioritization Under Pressure

You are a PM at a Series B B2B SaaS startup in Hyderabad. Your CEO demands a roadmap update tomorrow. Engineering says they can build only one of these features next quarter: (A) a new analytics dashboard requested by sales, (B) an improved onboarding flow to reduce churn, or (C) a mobile app for a new segment. Stakeholders are pushing strongly for their favorites.

You have limited time to decide and communicate your recommendation to the CEO.

PL alumni now work at Flipkart, Razorpay, PhonePe, Swiggy, Amazon, and 30+ other companies.

Where to go next