Problem Discovery and Definition

Creative Mindset as Problem Solving

Creativity is nothing more (or less) than problem solving. Every creative act — whether in art, science, or business — addresses a specific puzzle, aspiration, or “itch.” The key is that the process must be methodical and systematic, not random inspiration.

• Artist → expresses a personal itch
• Scientist → solves a puzzle
• Business person → cracks a market

All three follow the same underlying logic: identify a problem (stated, self-created, or an unmet aspiration) and work toward a solution.

The Systematic Problem-Solving Process

Problem discovery and definition is a structured journey with three core questions:

1. How do you discover a problem? → Move from surface-level awareness to a clear problem statement.

2. How do you go from symptoms to root cause? → Distinguish the observable signals from the underlying driver.

3. How do you prioritize what is worth going after? → Not every problem is equally important; resources must be allocated.

Exam tip: The transition from symptom to root cause is the most critical step — a misdiagnosis leads to wasted effort. In exam contexts, expect techniques (e.g., “5 Whys” or “Fishbone”) even if not named here.

From Symptoms to Root Cause: The Diagnostic Shift

A symptom is an observable effect (e.g., falling sales, user complaints). The root cause is the structural or fundamental reason behind it. Without this distinction, efforts treat the symptom, not the problem itself.

Why it matters:

• Solving symptoms → temporary relief, problem recurs.
• Solving root cause → lasting solution, possibly preventing future issues.

The module introduces specific techniques and methods for making this shift scientific and disciplined. This preview does not name them.

Key takeaways

• Creativity = methodical problem solving, not random insight.
• Three pillars: discover the problem, find root cause, prioritise.
• Symptoms are not the problem — root cause analysis is essential.
• Prioritisation prevents wasted effort on low-value issues.

The Process of Creative Problem Solving

Solving a problem is not a single leap from "what's wrong?" to "here's the fix." It is a structured, stage‑gated process. Trust the process: learn the methods first, then adapt them.

The Three‑Stage Model

The entire creative problem‑solving cycle is split into three compartmentalised stages. When you are in one stage, do not think about the next.

Stage 1: Problem Exploration

Intuition: You often mistake a symptom for the problem. "Students not paying attention" looks like a problem – punish them, create better content. But it is a symptom of a deeper cause. Spend time understanding the problem before acting.

Formal principle: The problem fully understood is half solved. Abraham Lincoln’s analogy: If I had six hours to chop down a tree, I spend the first four hours sharpening my axe.

• Do not generate ideas while exploring. The moment you start solving, you stop thinking about the problem.
• Avoid surface‑level thinking. Most people jump to advice because they see only symptoms. Be a deep thinker.
• Slow down. Use structured methods (Japanese, German, etc.) to nail down the real problem.

Exam tip: When presented with a case scenario, first ask: “Is this a symptom or the root problem?” Many marks are lost by proposing solutions to symptoms.

Stage 2: Solution Generation (Solution Vegetation)

Intuition: You want a few excellent ideas. But excellent ideas come only from a large pool of average ideas. Ideas are like Lego blocks – more blocks → more possibilities.

• Prioritise quantity over quality during generation.
• Do not be judgmental – criticism in a group shuts down contributors.
• Combine and fuse ideas, don’t just discard. Example: from 550 ideas → fused to 50 top ideas, not by removing 500 but by merging the strongest elements.
• The resulting 50 are far superior to 50 generated from scratch.

Worked example: A workshop with farmers generated >550 ideas in two hours. These were fused down to 50, yielding high‑quality, implementable concepts.

Stage 3: Solution Validation (Shortlisting)

Intuition: After boiling the milk (generation), skim the cream (selection). But do not use gut feel – use logic and data.

• Park your intuition. Old yardsticks kill radical ideas. An idea that sounds "bad" may be precisely the breakthrough.
• Triangulate with others. Use data and logical criteria, not emotion.

Key Skills for Effective Problem Solvers

Three habits separate average problem solvers from excellent ones.

1. Listen with Intent – The RASA Framework

• How you ask a question demonstrates empathy. The wording determines whether you attack the person or solve the problem.

2. Observe with Purpose

• Most people are glued to small screens and miss the world around them. This kills creative input.
• Selective attention is a trap. The famous “gorilla video” shows that when focused on one thing, you completely miss an obvious gorilla walking through the scene.
• Deliberate observation recovers the peripheral details that fuel creative thinking.

3. Defer Judgment

Intuition: Judging people or ideas prematurely blocks learning and transformation.

Key stories:

• Stephen Covey on a train platform: Two noisy kids, father looks exhausted. Covey prepares to reprimand him, only to discover the children’s mother had just died. His judgment vanished – replaced by guilt.
• Angulimala (murderer turned saint after meeting Buddha) and Valmiki (hunter turned author of the Ramayana) demonstrate that every saint has a past, every sinner has a future.

Oscar Wilde: “Judge no one, because every saint had a past and every sinner has a future.”

• Non‑judgmental listening allows situations to unfold naturally, creating space for mutual growth.

Divergent vs. Convergent Thinking

Problem solving is not linear (problem → solution). It follows two distinct modes:

• Divergent thinking is harder and less practised. Traditional education tests only convergent (single right answer).
• Creativity requires both – first diverge, then converge.

Exam tip: Remember that the quantity‑to‑quality principle (550 → 50) is a classic example of divergent followed by convergent thinking. Frame your exam answers around this sequence.

---

Key Takeaways

• The three stages are Problem Exploration → Solution Generation → Solution Validation – never mix them.
• Quantity leads to quality. Generate many ideas, then fuse the best.
• Listen with RASA (Receive, Appreciate, Summarize, Ask) to uncover real problems.
• Observe deliberately; avoid selective attention traps.
• Defer judgment – it blocks learning and transformation.
• Problem solving alternates divergent thinking (create options) and convergent thinking (select the best).

Symptoms vs. Problems vs. Root Causes

People routinely confuse symptoms with problems. When you visit a doctor and say "I have a headache, stomachache, can't sleep," you are listing symptoms — not the underlying disease. The same happens in everyday life: we call a thing a "problem" and jump to a solution, but what we actually see is a symptom.

Key insight: You do not know your own problem, let alone someone else’s — you only know their symptoms. Classifying something as a symptom shifts the mindset from solving to understanding.

To move from symptoms to root causes you need diagnosis. The doctor doesn’t stop at diabetes — she investigates why this person is diabetic. Root causes are always plural; they act together like an orchestra.

---

Quick Fix vs. Perma Fix

Two modes of response:

• Quick Fix (Jugaad) – a rapid, pattern‑matched patch that gets you through the immediate symptom. Example: putting folded paper under a shaky chair leg.

  Quick fix is not creativity. It is common sense and pattern matching. Solving a problem once ≠ creating a repeatable solution.

• Perma Fix – a deep solution that addresses the root causes and prevents recurrence. Example: designing a chair that never wobbles.

Both are valid, but Quick Fix should be a choice, not the default.

---

Impact‑Frequency Matrix

Decide which fix to use based on the problem’s impact and frequency.

Exam tip: The high‑impact/low‑frequency quadrant is a common trap. Many people stop after the quick fix and ignore the root‑cause investigation. Full marks require both steps.

Aviation example: Air travel is safe because every crash is investigated (quick fix: rescue; perma fix: black box analysis → global procedural changes). The same logic applies to any high‑impact, rare event.

---

The Zone of Creativity

Between an external event (stimulus) and your reaction lies a zone of creativity. Viktor Frankl: Between stimulus and response there is a space. In that space is our power to choose our response.

• Protect that zone.
• Expand it.
• Generate multiple options within it.

This selective response is what distinguishes humans from animals and machines. When someone shouts at you, you can ignore, rebut, or reframe – you have a choice. Creativity lives in that choice.

---

Key takeaways

• Symptoms are not problems; problems are clusters of symptoms.
• Root causes are multiple and require diagnosis.
• Quick Fix (Jugaad) is for low‑impact, rare problems; Perma Fix addresses root causes.
• Use the impact‑frequency matrix to consciously choose your response.
• The gap between stimulus and response is where creative choice happens.

Determining if a Problem is Worth Solving

Not every problem deserves your effort. Before diving into how to solve, always ask why solve it. If the problem itself is unimportant, no solution can make it important. The trap: most people jump straight to how (solutions), skipping the critical why (justification). A problem fully understood is half solved.

The Two Essential Questions

1. Why solve the problem? – Establishes importance, reframes the real need.
2. How to solve the problem? – Execution details; can often be delegated or automated.

Exam tip: Never proceed to how until why is answered. The most common mistake in problem-solving is solving the wrong problem well.

Worked Example: Bangalore Traffic

A friend drives a Santro and complains about city traffic. He gets promoted and could upgrade to a bigger car. Instead, he hires a chauffeur (cheaper for a Santro) and buys a Kindle. Now he reads books during the commute, turning the "problem" into a boon.

• Original problem: Bangalore city traffic.
• Why should I solve it? → Because it wastes my time.
• Reframed problem: Recover wasted time, not fix traffic.
• Outcome: He didn't solve traffic (unchanged), but solved his problem.

Lesson: Probing why reveals a different, more solvable problem.

Three Dispositions: Pharmacist, Doctor, Surgeon

These mindsets represent different depths of problem engagement:

Key insight: A pharmacist solves symptoms, a doctor solves problems, a surgeon solves root causes. You will be remembered for what you create (like the Taj Mahal’s creator), not for what you manage.

Exam tip: The "pharmacist, doctor, surgeon" analogy is a classic framework for problem-solving depth. Be the surgeon: understand the root cause, customise the solution, and take full ownership.

The Future of Problem-Solving

• Understanding the problem (framing, why) – cannot be delegated, automated, or outsourced. It remains a uniquely human skill.
• Solving the problem (execution, how) – can be automated, delegated, or outsourced.
• Creativity requires thinking hard, not just working hard. In an AI-driven world, deep problem understanding is the skill that will stay relevant for the next 100 years.

Key takeaways

• Always ask why before how – otherwise you risk chasing unimportant problems.
• The Bangalore traffic example shows how reframing (“wasted time”) makes the problem solvable individually.
• Three levels of problem-solving: pharmacist (symptoms), doctor (problems), surgeon (root causes).
• Surgeon-level thinking creates unique, lasting solutions and commands respect.
• Understanding the problem is the core human advantage; solving can be automated.

The Zone of Concern vs. Zone of Influence

To decide which problems deserve your attention, distinguish between two circles:

• Zone of Concern — everything that bothers you, worries you, or captures your attention: news headlines, social media drama, gossip, global crises. This zone expands with every sensational reel or newspaper.
• Zone of Influence — the small subset of your concern that you can proactively affect. What you can actually change through direct action.

The key principle: "Control the controllables" (M.S. Dhoni). Your zone of influence is always much smaller than your zone of concern. Most energy wasted on worries outside that inner circle.

As you grow (student → professional → leader), both zones can expand or contract. The recommended strategy: shrink your zone of concern (cut out small talk, excessive media, irrelevant opinions) and expand your zone of influence. This lets you pour energy into what actually matters.

Exam tip: The single most testable insight from this framework: focus on influence, not concern. Wasting time on uncontrollable problems is the opposite of effective problem discovery.

Problem Solving as Sculpting

Metaphor: a solution is already inside a problem, like an idol inside a stone. The craft of problem solving is chiseling — removing excess to reveal the solution. Most people chisel coarsely and settle for a rough outcome. Fine chiseling (attention to detail, perseverance over generations, as seen in the Ajanta and Ellora caves) creates work that endures for centuries.

The lesson: pick a small piece and do it exceptionally well, then move on.

Time-Based Problem Classification: Bruise vs. Cancer

Every problem behaves in one of two ways with the passage of time:

• Bruise — a problem that resolves itself or becomes irrelevant over time. Example: a small cut on your finger; healing time is fixed regardless of whether you apply ointment or do nothing.
• Cancer — a problem that worsens if left unattended. Example: a small liver bulge; ignoring it risks growth and complications.

The trap: every problem feels like a cancer when it first appears. The rational response is to step back and ask: If I don't address this right now, what happens? Most of the time the answer is nothing bad — the problem will solve itself. Overreacting wastes time and can even worsen the situation.

Exam tip: COVID taught that the world keeps moving without you. Accept that most problems are bruises. This frames problem selection: invest full might only into the 5–10% of problems that are truly cancerous.

Key Takeaways

• Your zone of influence is a small fraction of your zone of concern. Shrink concern, expand influence.
• Problem solving is fine chiseling — reveal the solution by removing excess, not by rushing.
• Bruise problems dissolve with time; cancer problems worsen. Classify before acting.
• ~80–90% of problems are bruises; don't treat them as emergencies.
• The ultimate question: Is this problem worth my full attention? If not, let it go.

Creative Mindset: Parallel Thinking with Six Thinking Hats

When solving problems in teams, vertical thinking – stacking one belief on another – often causes friction. Each person defends their own view (“talking to strangers is bad”, “never give to beggars”), treating others’ beliefs as threats. This wastes time and spoils relationships.

The antidote is parallel thinking (Edward de Bono): everyone in the team thinks in the same dimension at the same time. No conflict because nobody is arguing a different angle. The tool that enforces parallel thinking is the Six Thinking Hats – each hat represents one mode of thought. Crucially, all team members wear the same hat simultaneously.

The Six Hats – Intuition and Meaning

Exam tip: The most common mistake in applying the hats is letting different people wear different hats at the same time – that recreates vertical conflict. The whole point is parallel: every person wears the same hat.

Suggested Sequence (Flexible)

The moderator (always wearing Blue) guides the group through a typical sequence:

1. White Hat (2–3 min) – Get all data on the table.
2. Red Hat (2 min) – Invite emotional responses to the data.
3. Green Hat (10 min) – Generate ideas without judgment.
4. Yellow Hat (2 min) – Find positives in the ideas generated.
5. Black Hat (2 min) – Identify weaknesses or risks.

Hats can be interspersed as needed – e.g., if energy drops, call Yellow to lift mood; if ideas stall, call Green again. The Blue Hat moderator stays on throughout, owning the process.

Why It Works

Vertical thinking → conflict → waste. Parallel thinking → focused contribution → efficient problem definition.

Worked Illustration

A team must decide whether to launch a new product. Instead of arguing, the moderator says:

• “White hat – share only sales data and costs.” (No opinions.)
• “Red hat – how do you feel about the market?” (One member: “My gut says competitors will react fast.” No one demands proof.)
• “Green hat – what alternative launch strategies can we think of?” (Ideas flow without critique.)
• “Black hat – what could go wrong with each idea?” (Risks listed calmly; no defensiveness.)

Because every hat is worn by all, the discussion stays productive.

Key takeaways

• Vertical thinking (fixed beliefs) causes team conflict; parallel thinking reduces it.
• Six Thinking Hats: White (data), Red (emotion), Yellow (positive), Black (negative/caution), Green (creativity), Blue (process/control).
• All team members wear the same hat at the same time – never mix hats.
• The moderator always wears the Blue hat and sequences the others.
• Typical order: White → Red → Green → Yellow → Black, but flexible.
• Tool works for any group discussion, not just formal brainstorming.

5 Why Analysis

The 5 Why Analysis is a root‑cause technique from Toyota’s production system. Intuitively, instead of solving the surface symptom, repeatedly ask “Why?” until the underlying mechanism is exposed — usually in 3–5 iterations. The process itself often reveals the solution.

How it works

1. State the observable problem.
2. Ask “Why does this happen?” and write the answer.
3. For each answer, ask “Why?” again.
4. Repeat until the root cause emerges (typically after 3–5 whys). No need to force exactly five.

Worked examples

Example 1 – Students inattentive

• Problem → Why? → Course not engaging → Why? → Too simple/complex → Why? → Teacher didn’t assess students → Why? → Teacher not incentivised → Root cause: lack of incentive for upfront student assessment.

Example 2 – People breaking traffic signals Two possible investigative branches (each valid):

1. No fear of getting caught → few traffic police → too many signals → Possible solution: automated enforcement.
2. It’s a norm → low discipline in society → discipline not taught early → society does not respect discipline → Root cause: cultural attitude towards discipline.

Exam tip: You may reach the root cause in 3 or 4 whys. The technique is flexible — do not mechanically force five iterations. Also, avoid using the method as a blunt interrogation; it should be a collaborative discovery tool.

Key takeaways

• 5 Why Analysis drills down from symptom to root cause.
• Each “Why” builds on the previous answer.
• Different starting branches can lead to different root causes; explore multiple lines.
• The technique is both a problem‑discovery and solution‑finding tool.
• Encourages courage to question assumptions — a creative mindset.

---

5W2H Analysis

5W2H systematically explores a problem by answering Who, Why, What, When, Where, How, and How much. This creates a multi‑dimensional understanding of the problem space, revealing leverage points for intervention.

The seven dimensions

Worked example – Children watching mobile phones

Who – Children as young as 2–3 years, across all social strata (daily‑wage to millionaires). Why – Boredom; cheap entertainment; parents use it as a pacifier; socially acceptable; side effects not immediately visible. What – Initially cartoons, songs, funny videos; can escalate to inappropriate content. When – During meals, when alone, when travelling, before sleep. Where – Everywhere, especially outdoors (restaurants, transport). How – Parents give phone; child demands it (tantrums); snatches it; watches alone or with parent. How much – 30 min to 5 hours per day; higher in rural areas than urban.

Insight from the example

The real issue is that the brain does not distinguish between the dopamine hit from a phone and that from a cigarette. Withdrawal symptoms from phone use resemble those from substance addiction. The solution is not to snatch the phone, but to provide better alternatives (books, musical instruments) and to model desired behaviour (adults reading instead of scrolling).

Exam tip: 5W2H does not prescribe one solution — it reveals that multiple dimensions must be addressed. A single intervention (e.g., banning phones) is rarely sufficient. Look for patterns across the dimensions.

Key takeaways

• 5W2H maps a problem across seven structured questions.
• Each dimension uncovers a different facet of the problem.
• The technique can be applied to any complex social or behavioural issue.
• Understanding the full dimensionality prevents simplistic, one‑size‑fits‑all solutions.
• Combining 5W2H with 5 Why can deepen root‑cause analysis (e.g., asking “Why” within each dimension).

Fishbone (Ishikawa) Diagram

A fishbone diagram (also called Ishikawa diagram) is a cause‑and‑effect tool that breaks a problem into six major categories (the “6 Ms”) to uncover root causes. It looks like a fish skeleton: the problem (effect) is the head, and the bones represent causes grouped into the six buckets.

Definition: A structured, visual method to systematically list and organize potential causes of a problem by grouping them under predefined categories.

The 6 Ms

How to use it

1. Define the effect clearly (e.g., “frequent bike breakdown”).
2. Brainstorm causes under each of the 6 Ms.
3. The diagram forces exploration of causes you might otherwise miss — e.g., without the method, you would likely overlook environmental or measurement factors.

Exam tip: The fishbone is excellent for group brainstorming but works individually too. It is most powerful when you list at least 2–3 causes per M before moving on.

Discipline and creativity

The speaker notes that creativity requires discipline — methods like Ishikawa are not anti‑creative. “Trust the process before you break the process.” The 6 Ms originated in Japanese manufacturing but apply to service and abstract problems as well.

Key takeaways – Fishbone diagram

• A cause‑and‑effect tool that organizes root causes into six pre‑defined buckets (Man, Machine, Material, Method, Measurement, Mother Nature).
• Use it to systematically explore a problem from multiple angles, avoiding obvious or narrow views.
• The diagram is visual and can be used in both manufacturing and service contexts.
• Applying a disciplined method enhances, not hinders, creative problem‑solving.

---

Mind Mapping

A mind map is a radial, visual technique for exploring a problem by branching out from a central topic into related causes, themes, or sub‑problems. It gives an “at‑a‑glance” picture of the entire problem space.

Worked example: Why don’t people wear helmets?

Central problem: People (especially young adults) not wearing helmets.

Branches (causes)

• Discomfort

  • Helmet is heavy, restricts vision
  • Storing the helmet (gets wet, collects dust)
  • Reduces the “fun” of riding

• Affordability

  • Helmets cost ₹100–₹500; cheapest (₹100–150) are often ineffective but satisfy RTO requirements
  • Large families (3 riders) may not afford multiple helmets

• Access

  • Helmet shop far away → “forget about it”

• Awareness

  • Lack of understanding: head injuries are the most serious in road accidents (brain cannot be replaced)
  • Effective campaigns: Delhi showed gory accident videos instead of penalising

• Law enforcement

  • In tier‑2/3 cities enforcement is weak → “nobody’s watching”
  • Social pressure to not wear a helmet (e.g., “you’re so afraid”)

• Social norms

  • Norms often override laws (e.g., bribery is a norm, intercaste marriage is legal but not a norm)
  • What is socially acceptable drives behaviour more than legal rules

Additional example (brief)

For the problem “placements not happening in colleges”, a mind map could include:

• Outdated curriculum
• AI reducing jobs
• Teachers not raising standards
• Students slacking / studying only for placements
• Lack of practical understanding

Key takeaways – Mind mapping

• A radial diagram that branches out from a central problem to capture multiple causes and perspectives.
• Encourages exhaustive exploration — includes discomfort, affordability, access, awareness, enforcement, and social norms.
• Reveals connections and hidden drivers (e.g., norms vs. laws).
• Effective for personal, social, or organisational problems; easy to extend iteratively.

Problem Exploration Methods: Stakeholder Maps and Journey Maps

Problems are rarely caused or solved by a single person – they involve multiple stakeholders. Two structured techniques help unpack this complexity before attempting any solution: the stakeholder map and the journey map (also called value stream map). Both force the problem-solver to hold many moving parts in mind simultaneously – a hallmark of creative, complex thinking.

---

1. Stakeholder Map

A stakeholder is any individual or group that either influences the problem, is impacted by it, or can be instrumental in solving it. Mapping them reveals the web of causes and potential leverage points.

Example: Low voter turnout in a democracy

The observable symptom is that only 50–60% of eligible voters turn up. The stakeholder map uncovers why:

Each stakeholder’s influence is a cause of low turnout. Because the problem is multi‑faceted, the solution must be multi‑faceted too – no single intervention will work.

Using the map

• List every stakeholder on a mind‑map or diagram.
• For each, ask: How does this stakeholder contribute to the problem? How could they help solve it?
• The same technique works for any multi‑party problem – e.g., placing students in internships (stakeholders: student, placement officer, recruitment team, supervisor, family, faculty).

Exam tip: Stakeholder maps prevent narrow problem framing. On an exam question about a complex real‑world issue, immediately ask yourself “Who else is involved?” to generate comprehensive analysis.

Key takeaways – Stakeholder Map

• A stakeholder is anyone who influences, is affected by, or can solve the problem.
• Problems are caused and solved by multiple stakeholders – not one person.
• Map them systematically (mind‑map or table) before attempting any solution.
• The richer the map, the more nuanced the eventual solution.

---

2. Journey Map (Value Stream Map)

A journey map is a temporal understanding of an experience – it breaks a process into sequential stages and identifies where things go wrong at each stage. This reveals pain points that are invisible when looking at the whole.

Example: Airport entry journey

Divide the passenger’s experience into four stages:

Each stage has its own set of problems. By mapping the journey, an airport operator can prioritise which touchpoints to improve – e.g., better signage, multiple language announcements, or a mobile app that notifies gate changes.

How it works

• Define the start and end of the process.
• Identify 3–6 critical stages in between.
• For each stage, list everything that can go wrong from the user’s perspective.
• Do not jump to solutions – the goal is deep understanding.

Key takeaways – Journey Map

• A journey map captures the sequence of a user’s experience.
• Each stage is analysed for pain points (not just overall satisfaction).
• Widely used in service design, product development, and process improvement.
• “Solve the problem later – understand it first.”

Problem Prioritization Methods

Once a set of problems has been identified, not every problem is worth solving. The goal is to select the high-leverage problems — those whose solution yields disproportionate impact. Two complementary methods help narrow the list: the Pareto principle and the MECE framework.

Why Prioritize?

• Resources (time, money, people) are limited.
• Solving all problems is inefficient — most will have little effect.
• Focus on the few problems that produce the greatest improvement.

Pareto Principle (80/20 Rule)

Intuition: A small number of causes drive the majority of effects. In problems, roughly 20% of the issues account for 80% of the total negative impact or opportunity.

Formal statement: For any collection of problems, the distribution of impact is skewed: about 80% of the consequences come from 20% of the causes, and vice versa.

Application to problem prioritization:

• List all identified problems.
• Estimate the weight or impact of each.
• Select the top 20–30% (e.g., 4 out of 10) that together capture ≈80% of potential benefit.

Worked example: voter turnout

Improving voter enrolment for immigrants and out-of-city residents could cause a “substantially high jump” in turnout. This single problem – simplifying registration – is a high-leverage 20% problem. Similarly, mobilising NGOs and volunteer groups to educate first-time voters and help with logistics (e.g., polling station location, best time to vote) is another high-impact area. Online voting, though futuristic, could be a game-changer.

Selection can be done mathematically (weighted scoring) or intuitively (expert judgement). The key is to skim the cream – pick the few problems with the largest expected payoff.

MECE (Mutually Exclusive, Collectively Exhaustive)

Intuition: When you break a problem into sub-problems, ensure that (a) no sub-problem overlaps with another (mutually exclusive), and (b) the sub-problems together cover the whole original problem (collectively exhaustive). This eliminates double-counting and gaps.

Formal definition:

• Mutually exclusive: The categories do not intersect – an issue belongs to exactly one sub-problem.
• Collectively exhaustive: The union of all sub-problems equals the original problem – nothing is left out.

Example: A class divided into girls and boys.

• Mutually exclusive? Yes – a student is either a girl or a boy, not both.
• Collectively exhaustive? Yes – the sum of girls and boys equals total class strength.

Why MECE matters for prioritisation:

• Prevents overlapping work (different teams solving the same part).
• Avoids interdependencies (a solution to one sub-problem does not cascade into another).
• Makes the reduction from 10–20 problems to ~5 problems clean and efficient.

Exam tip: MECE is especially useful when assigning problems to different teams. If sub-problems are not mutually exclusive, fixing one may break another, creating a domino effect.

Impact–Frequency Matrix (recap)

Earlier in the module, problems were assessed using a two‑dimensional grid: impact (severity of effect) vs. frequency (how often the problem occurs). Prioritise problems that lie in the high‑impact, high‑frequency quadrant. This matrix can be combined with Pareto and MECE to validate the final shortlist.

How the Methods Work Together

---

Key takeaways

• Prioritisation is essential because not all problems have equal leverage.
• Pareto (80/20): Focus on the few problems that deliver ~80% of the benefit.
• MECE: Ensure selected sub‑problems are mutually exclusive (no overlap) and collectively exhaustive (no gaps).
• The Impact–Frequency Matrix cross‑checks that selected problems are both frequent and severe.
• Combining these methods yields a shortlist of high‑leverage, well‑defined, independent problems.

The Two Doctors: Why Listening Trumps Prescription

Two equally qualified doctors. The same patient. The same complaint (headache, stomachache, insomnia, drowsiness).

• Dr. A does not make eye contact, scribbles on a prescription while the patient speaks, cuts the story short, and hands over medicine. The patient recovers.
• Dr. B maintains eye contact, asks follow‑ups (duration, family history), diagnoses overwork, prescribes rest — no medicine. The patient also recovers.

Which doctor would you revisit? Dr. B — not because the outcome was better, but because he paid attention. Empathy — the ability to sense and respond to another’s emotional state — builds trust. Dr. A solved the technical problem but ignored the human one. In fast‑paced, digital lives, people default to “Dr. A” behaviour: sending texts instead of connecting, rushing to solutions, never listening.

Exam tip: The “two doctors” story is a classic illustration that empathy precedes accurate problem definition. Even a correct diagnosis feels incomplete if the patient was unheard.

Behavioural Problems vs. Technical Problems

Problems like traffic violations, low voter turnout, or not wearing seatbelts are behavioural, not technical. They cannot be solved with logic alone.

• Technical problems have known inputs and outputs.
• Behavioural problems require understanding people’s innate motivations, fears, and drives.

Without empathy, the deepest root causes remain hidden.

Emotional Intelligence (EI) vs. Cognitive Intelligence (IQ)

Traditional education rewards cognitive intelligence (IQ) — logic, science, maths. Yet many high‑IQ individuals struggle with relationships, careers, and life satisfaction.

People are not homo economicus (rational calculators) but homo sapiens (emotional beings). To understand a problem, you must first understand the emotions behind it — your own and others’.

Daniel Goleman’s Four Levels of Emotional Intelligence

1. Self‑awareness Know that you are angry, sad, or anxious. Observe your emotional state without judgment. Many people feel depressed but deny it — they lack the first step: acknowledging “I am depressed.” Technique: Imagine a camera five feet above yourself. Watch your own reactions from outside to regain control.

2. Self‑management Once aware, do something constructive.

• If angry: sit quietly, breathe, avoid driving or writing emails.
• If depressed: seek food (like curing hunger) or professional counselling — it is a state, not a stigma. The goal is to prevent emotions from contaminating decisions and relationships.

3. Empathy “The way I understand my own emotions so well, can I understand other people’s emotions also?” Empathy requires pausing the endless self‑talk (“me, me, me”) to see the world from another’s perspective. Example: A five‑year‑old behaves like a five‑year‑old. An emotionally immature adult behaves according to their development. Instead of blaming, ask: “What in their past, upbringing, or immediate environment explains their behaviour?”

4. Skilled relationship Knowing yourself + knowing the other → build a relationship that suits their emotional state, not yours. Every relationship is unique: parent, spouse, boss, child, friend. Adapt your communication style. The phrase “I’m like that only” is a weakness, not a badge of pride.

How Empathy Unlocks Real Problem Definition

Only when the other person feels heard will they reveal the real issues — the hidden needs, fears, and behaviours.

• Dr. A solved the stated problem.
• Dr. B uncovered the underlying problem (overwork → stress → symptoms).

Empathy is not just “nice to have”; it is the prerequisite for accurate problem discovery. A solution built without empathy addresses symptoms, not causes.

Key takeaways

• Empathy is the ability to understand another person’s emotions; it builds trust and enables honest disclosure.
• Behavioural problems (traffic, voting, health) require emotional, not merely logical, understanding.
• Emotional intelligence has four ascending levels: self‑awareness → self‑management → empathy → skilled relationships.
• High IQ without EI often leads to poor relationships and life dissatisfaction.
• A problem solver who rushes to solutions (Dr. A) misses the human context; the empathetic solver (Dr. B) gets to the real problem.

Types of Empathy

Empathy is not a single ability; Daniel Goleman’s research distinguishes three distinct types. Most people demonstrate one or two in specific contexts, but genuine empathy requires all three working together.

1. Cognitive Empathy

What it is — understanding another person’s perspective, their thoughts, and what they are trying to say. It is a “thinking” skill (cerebral).

• Key action: perspective-taking.
• Example: A student striving to grasp a teacher’s explanation, even when the teaching style is unfamiliar.
• Pitfall: Cognitive empathy alone can lead to manipulation. A call-centre agent who reads a script may understand your problem and resolve it, but you feel no emotional connection — the interaction feels hollow.

Exam tip: Cognitive empathy is the foundation, but without the other two types it is incomplete and can be weaponised. Always ask: Do I only understand, or do I also feel and act?

2. Emotional Empathy

What it is — feeling what another person feels. This engages the limbic system (the emotional brain) and builds genuine rapport.

• Key action: shared feeling.
• Common gender difference (example):
  • A man asks another man “Are you hungry?” → expects a cognitive yes/no answer.
  • A woman asks another woman the same question → interprets the question as a signal that the asker is hungry, leading to a shared decision to stop and eat. Interpretation: Women in this example are more attuned to the emotional subtext (the need behind the question).
• Pitfall: Emotional exhaustion. A call-centre rep who constantly absorbs customers’ anger and apologises for eight hours may suppress frustration. At home, the accumulated emotion can explode over a minor incident (e.g., a child spilling water). Over-empathising emotionally harms both the helper and the recipient — the customer never learns self-regulation, and the helper risks burnout.

3. Empathic Concern (Empathic Action)

What it is — not only understanding and feeling, but doing something to alleviate the problem. This is the rarest and most complete form of empathy.

• Key action: active help.
• Example: Your mother has a headache.
  • Cognitive: You ask why → she explains it’s from the sun.
  • Emotional: You feel her pain.
  • Empathic concern: You press her head, give her medicine, ask her to lie down.
• Core idea: Empathy is an emotional action, not just an emotion. Knowing someone is in pain does not relieve it — you must actively address the pain.

How the Three Types Connect

Geniune empathy emerges only when all three work together:

Without action, empathy remains superficial. The air hostess thanking you “from the bottom of her heart” is cognitively following a script; you sense the lack of genuine concern. Real empathy adjusts behaviour — e.g., a flight at 2 a.m. should cut non-essential announcements to let passengers sleep.

Applying Empathy to Problem Discovery

When investigating why people behave in a certain way (e.g., not wearing helmets, not voting, children addicted to phones), you must:

• Go beyond census data (age, income, etc.). Numbers can be measured but often miss the emotional need.
• Descend to the user’s level. To understand a child’s phone addiction, sit at the child’s height. From that angle, the child looks up at the TV (causing neck ache) — the phone is simply more comfortable. The problem is not “bad behaviour” but an unmet physical need.
• Sense weak signals. As Einstein said: “Not everything that counts can be counted, and not everything that can be counted counts.”

Comparing the Three Types

Key takeaways

• Empathy has three distinct components: cognitive, emotional, and empathic concern.
• Cognitive empathy alone can enable manipulation; emotional empathy alone can cause burnout.
• Genuine empathy requires all three: understand → feel → act.
• When discovering problems, go beyond numbers: sense emotional needs and adopt the user’s physical/mental perspective.
• Empathy is an emotional action — not just a connection of minds or hearts, but a hand that reaches out to fix the problem.

Listening Skills and the Empathy Map

Empathy begins with listening. Most people listen with the intent to reply, not with the intent to understand (Stephen Covey). Rushing to solutions means you never grasp the problem in its totality – you only treat symptoms. Effective problem discovery requires deliberate listening.

---

Listening Positions (Julian Treasure)

Three paired dimensions of listening. Each pair is a continuum; the appropriate position depends on context.

Default setting: Most people default to active, reductive, critical – interrupting, concluding, analyzing. This blocks true understanding. Shift deliberately toward passive, expansive, empathetic when the goal is discovery.

---

RASA Technique (Julian Treasure)

An acronym for a structured listening practice.

Exam tip: The order matters – summarize before asking. Jumping to ask too early can feel like an interrogation.

---

Empathy Map

A framework to capture and organise interview / observation data about a persona – their drivers, motivators, thinking patterns, inputs, and outputs.

Structure of an Empathy Map:

• Hear – What does the person hear from environment, peers, media?
• See – What does the person see in their surroundings?
• Say & Do – What does the person say to others? What actions do they take?
• Think & Feel – What occupies their mind? What emotions arise?
• Pains – Fears, frustrations, obstacles, costs.
• Gains – Desired outcomes, benefits, satisfactions.

A well-built map reveals why a person behaves the way they do – often because pains outweigh gains.

Worked Example 1: Helmet non‑use among teenagers

Result: Pains (10 items) far outweigh gains (3). Hence the behaviour persists.

Worked Example 2: Low voter turnout

Result: Gains are dwarfed by pains – so the problem (low turnout) persists.

---

Connecting to Problem Discovery

Listening skills and the empathy map are tools to surface the real problem. Without them, you solve symptoms. The empathy map transforms raw interview data into a structured profile of pains (motivators for change) and gains (desired outcomes). This directly feeds into problem framing – defining a problem worth solving.

Key insight: If the pains of the current situation exceed the gains, change will not happen. The empathy map exposes that imbalance.

Key takeaways

• Three listening dimensions: active/passive, reductive/expansive, critical/empathetic. Choose based on context.
• Most people default to active, reductive, critical – block true understanding.
• RASA: Receive → Appreciate → Summarize → Ask. Summarise before asking.
• Empathy map captures hear, see, say/do, think/feel, pains, gains.
• Use the map to diagnose why a problem exists: pains > gains → no change.
• Problem solving is rigorous: empathy + listening = accurate problem definition.

Problem Framing

Framing a problem means defining its boundary conditions — where to focus and when the problem is solved. Without a clear frame, problem-solving becomes an endless pursuit. A well-framed problem motivates action, channels creativity, and prevents wasted effort.

Three Essential Parameters of a Good Problem Frame

Exam tip: The trick is balance — a good frame has all three. No constraint → no pressure to innovate. No vagueness → no room for imagination.

---

Illustrative Examples

1. Kennedy’s Moon Mission

“We need to put a man on the moon and bring him back safely by the end of this decade.”

• Impact: Land a human on the moon and return safely.
• Constraint: Finite timeline (end of decade) + safe return.
• Vagueness: “How to do it?” — left open; engineers could choose technology, trajectory, materials.

Without the timeline or the safety condition, the goal would lack urgency and specific challenge.

2. Reducing Employee Attrition — A/B/C Comparison

Statement B has the ideal combination: impact, a clear non-negotiable (cost cap), and enough vagueness to allow creative solutions beyond just adjusting salary.

3. Tata Indica Design Brief

“We need to design an Indian car from scratch … internal volume of an Ambassador, size of Maruti Zen, ease of entry/exit, priced close to Maruti 800, economy of diesel, contemporary design.”

• Impact: A brand-new Indian car — a category first for Tata Motors.
• Constraints:
  • Diesel engine economy
  • External size as small as Maruti Zen or Maruti 800
  • Internal volume as large as Ambassador
  • Affordability (priced near Maruti 800)
• Vagueness: “Contemporary design” — no specific styling instructions, leaving room for designers.

The contradictory constraints (small outside, big inside) forced innovation in packaging — a key reason for Indica’s lasting success.

4. Google’s Metaphor: The Web as Fast as Flipping Through a Magazine

“Make the web as fast as flipping through a magazine.”

• Impact: Speed, ease, intuitiveness, high-quality image/text rendering.
• Constraint: Implicit — must be as effortless and rapid as a physical magazine.
• Vagueness: The metaphor captures multiple attributes (speed, intuitive navigation, bookmarking, random access) without prescribing a technical solution.

Metaphors in problem framing compress complex requirements into a vivid image. Canon used the beer can metaphor (easy to transport, stack, buy, affordable) for printer/copier design. Honda City used city boy (agile, efficient, man-maximum-machine-minimum). Mahindra XUV500 used cheetah — the design team studied the animal in Kenya and translated its posture, grille, and door handles into the car body.

---

The Framing Process (Flow)

A problem fully defined (with impact + constraints + vagueness) is half solved — it focuses effort on high-leverage opportunities.

---

Key takeaways

• Problem framing requires impact, constraint, and vagueness — all three are essential.
• Constraints liberate creativity; without them, solutions wander.
• Vagueness prevents “leading to the solution” — it preserves room for multiple approaches.
• Metaphors (e.g., flipping a magazine, cheetah) are powerful framing tools — they compress many requirements into an intuitive image.
• A well-framed problem motivates teams, sets clear success criteria, and avoids endless problem-solving.
• Prioritize only problems that, if solved, give the highest return — then frame them precisely.