Critical Thinking – Study Notes
(M.Tech. – Skill Enhancement)
1. What is Critical Thinking?
- Think clearly.
- Ask questions.
- Check facts before you decide.
- It’s like being a detective in your own mind.
Everyday Analogy
Imagine you’re buying a phone.
- You don’t just trust the advertisement.
- You compare prices, read reviews, ask friends.
- That careful, step‑by‑step check is critical thinking.
2. Why Do We Need It?
| Benefit | Simple Example |
|---|---|
| Better decisions | Choosing the right supplier after comparing offers. |
| Problem solving | Fixing a software bug by isolating the cause. |
| Clear communication | Explaining a research idea to a non‑expert. |
| Adaptability | Adjusting a project plan when new data arrives. |
3. Core Elements (No Jargon)
| Element | What It Means | Quick Check |
|---|---|---|
| Questioning | Don’t accept things at face value. | “Why is this true?” |
| Evidence | Look for proof. | “Do we have data?” |
| Assumptions | Spot hidden beliefs. | “What am I assuming?” |
| Alternatives | Think of other options. | “What else could happen?” |
| Consequences | Predict outcomes. | “What will it lead to?” |
4. The Critical‑Thinking Process (Step‑by‑Step)
-
Notice a problem or idea.
Example: A sudden drop in server uptime. -
Ask “What? Why? How?”
What happened? Why did it happen? How can we fix it? -
Gather facts.
- Check logs, ask teammates, look at metrics.
-
Identify assumptions.
- “We thought the network was fine.”
-
Generate alternatives.
- “Maybe the code, maybe the hardware, maybe the user load.”
-
Weigh evidence for each alternative.
- Compare data, run quick tests.
-
Choose the best option.
- Pick the one with the strongest support.
-
Review the decision.
- Did it solve the problem? What did we learn?
5. Simple Techniques
| Technique | How to Use It | Tiny Example |
|---|---|---|
| Ask “Why?” (5 Whys) | Keep asking “why” until you hit the root cause. | “Why did uptime drop? – Because of 404 errors. Why 404? – Wrong URL.” |
| List Pros & Cons | Write down positives and negatives for each choice. | “Pros: Fast fix. Cons: Might break other modules.” |
| Consider the Opposite | Think about what would happen if you did the opposite. | “What if we kept the old code?” |
| Use a Decision Matrix | Rate options on criteria (cost, time, risk). | Table of options vs. score. |
| Pause & Reflect | Take a 5‑minute break before deciding. | “Step back, think, then act.” |
6. Common Pitfalls & How to Avoid Them
| Pitfall | Simple Fix |
|---|---|
| Jumping to conclusions | Always collect evidence first. |
| Basing on feelings | Cross‑check with data or facts. |
| Ignoring alternatives | List at least three options. |
| Over‑analysis | Set a time limit for each step. |
| Blindly following authority | Question even expert advice if evidence is weak. |
7. Tiny Real‑World Example
Problem: Your team’s code builds every day, but the test suite fails 40% of the time.
- Notice: 40% failure rate.
- Ask: What’s failing? Why? How?
- Gather facts: Look at failure logs → “Timeout on API call.”
- Assumption: The API is always available.
- Alternatives:
- Increase timeout.
- Mock the API.
- Use a different endpoint.
- Weigh evidence: Mocking gives 100% success locally.
- Choose: Implement mock for tests.
- Review: Build passes again, load on real API is unchanged.
8. Practice Exercise
- Pick a recent decision you made (e.g., choosing a software tool).
- Run through the 8‑step process on paper.
- Write a short paragraph on what you learned.
9. Quick Checklist for Critical Thinking
- Did I ask “why” enough?
- Is there evidence for each claim?
- Have I identified hidden assumptions?
- Did I consider at least 3 alternatives?
- Have I weighed pros, cons, and risks?
- Will I review the outcome later?
Use this checklist whenever you’re faced with a decision or problem.
Final Thought
Critical thinking is like a mental toolbox.
- The more tools you master, the easier it becomes to fix problems, make good choices, and learn continuously.
Happy thinking!