Design Your Thinking — Notes

IIM Bangalore BBA in Digital Business and Entrepreneurship · Term 3 · 4 modules, 258 topics.

Creativity and Ideation

Module 3 – Creativity and Ideation: Overview

Design thinking separates problem-framing from problem-solving. Before generating ideas, the problem must be understood from every angle — through empathy work (stakeholder maps, journey maps, empathy maps, etc.). Deferring ideation is a deliberate principle: jumping to solutions before understanding the problem in its totality is a common mistake. Only after deep, 360-degree exploration does the process move to creative idea generation.

Module 3 covers the creative core of design thinking:

What creativity is
How creativity differs from intelligence
How to measure creativity
How to become more creative as an individual
Various idea generation methods (brainstorming, SCAMPER, etc.)

Module 4 then builds on this: prioritising ideas, validating them, building prototypes, and scaling solutions.

The sequence of design thinking (empathise → ideate → prototype)

The earlier modules gave tools to empathise (e.g., the cafeteria project revealed how food is distributed in a short time). With that deep understanding, ideation can be done effectively.

flowchart LR
    A[Empathise & Define] --> B[Defer Ideation]
    B --> C[Understand problem 360°]
    C --> D[Ideate creatively]
    D --> E[Prioritise, Validate, Prototype]

Exam tip: The key differentiator is that ideas are generated after thorough empathy, not before. Many students mistakenly begin solving before defining. The “defer ideation” rule is a high-yield principle.

Key takeaways

Ideation is deliberately postponed until the problem is fully understood from all perspectives.
Module 3 explores creativity: definition, difference from intelligence, measurement, and enhancement.
Idea generation methods are the practical tools for coming up with solutions.
Module 4 follows with prioritisation, validation, and prototyping.
The cafeteria project example shows how real empathy work grounds the ideation phase.

Definition

An idea is creative only if it is simultaneously novel (original, never thought of before) and useful (practical, solving a real need). Both conditions are sacrosanct – missing either disqualifies the idea.

Novel but not useful: e.g., a phone powered by body heat. Novel concept, but low utility (you would not keep the phone next to your body to charge it). → Not creative.
Useful but not novel: e.g., using a stone as a doorstopper or a mobile as a paperweight. Works, but is obvious. → Not creative.

Definition: Creativity = Novelty + Utility. The bar rises when both must be met.

Creativity vs Intelligence

Creativity and intelligence are related but not identical. Highly creative people are not necessarily highly intelligent, and vice versa.

Pattern Recognition vs. Pattern Breaking

Intelligence is the ability to recognize and predict a pattern – the most primitive form of intelligent behaviour (even apes do it). Patterns reduce cognitive load; the brain loves them (e.g., muscle memory for daily routines).
Creativity is the ability to break an existing pattern and form something new. Breaking patterns is difficult – try writing with your non-dominant hand. The brain resists because patterns make life efficient, but they also cause mistakes when the context changes.

Exam tip: The book Thinking, Fast and Slow by Daniel Kahneman explains why humans rely on mental patterns (heuristics) and how to overcome them. This is a high-yield reference for the pattern-breaking argument.

Convergent vs. Divergent Thinking (J.P. Guilford)

Guilford distinguished two thinking modes:

Thinking Type	Goal	Example	Role
Convergent	Find the single right answer	$5 \times 5 = 25$	Measures intelligence; most education trains for this
Divergent	Generate many possible answers	"Ways to use two numbers to get 10" (e.g., $5+5$ , $5\times2$ , $20\div2$ , ...)	Measures creativity; rarely taught in school

Convergent = intelligence → one correct outcome.
Divergent = creativity → multiple possibilities, exploration.

Intelligence as Choice, Creativity as "And"

Intelligence is about making the best choice among given options (like chess: "move here or there?").
Creativity is about combining or surprising – not just choosing, but creating new options. In chess, at grandmaster level (e.g., Viswanathan Anand), everyone knows your moves from YouTube. The only way to beat a prepared opponent is to be creative (break the expected pattern) – not just intelligent.

Example: IBM's Deep Blue defeated Garry Kasparov in 1997 using brute computation (intelligence). Yet humans still play chess because beyond a certain ELO (e.g., 2300), creativity, not raw intelligence, decides the winner.

IQ and Creativity: The Role of Latent Inhibition

The relationship between IQ (a measure of intelligence) and creativity is mediated by latent inhibition – the brain's tendency to filter out familiar or irrelevant stimuli.

IQ = $\frac{\text{mental age}}{\text{chronological age}} \times 100$ . Typical around 110–120; above 140 considered genius; below 90 indicates mental age lagging.
High IQ does not guarantee high creativity. Creativity emerges only when latent inhibition is low – i.e., the person is less inhibited by fear of failure, criticism, or social perception. Low latent inhibition means being open to trying new things and accepting failure.

flowchart TD
    A[High IQ] --> B{Latent Inhibition}
    B -->|Low| C[High Creativity]
    B -->|High| D[Low Creativity]

People with high latent inhibition criticise themselves before every move, stifling creativity.
Thomas Edison on failing 9,999 ways to invent the light bulb: "I haven't failed. There are 9,999 ways in which I know how it doesn't work." – Low latent inhibition enables creative persistence.

Exam tip: The key conclusion: intelligence is a matter of aptitude; creativity is a matter of attitude. IQ gets you into the office; creativity (and emotional intelligence) wins in the long run.

Key Takeaways

Creativity = Novelty + Utility. Both are required; neither alone suffices.
Intelligence is pattern recognition and convergent thinking; creativity is pattern breaking and divergent thinking.
Convergent thinking (one right answer) vs. divergent thinking (many possibilities) – most education trains convergent thinking.
Creativity requires low latent inhibition – willingness to fail and ignore social judgment.
High IQ does not automatically give high creativity; low latent inhibition is the mediating factor.
In the AI era, intelligence tasks can be delegated; creativity (especially identifying applications) becomes the premium skill.

Testing Creativity

Can creativity be measured? Emphatically yes. Creativity is not a mystical trait — it can be systematically tested. Pioneered in the 1960s (J.P. Guilford and later Ellis Torrance), these tests remain valid today. The distinction between intelligence and creativity is critical: intelligence helps you go deeper within a domain; creativity helps you go wider across domains, connecting apparently unrelated ideas.

Divergent vs. Convergent Thinking

Guilford introduced divergent thinking (generating multiple options) and convergent thinking (choosing one option). Divergent thinking is the harder part — it is the core of creativity and design thinking. Example: choosing between five courses is easy; creating five course titles from scratch is difficult.

Definition: Divergent thinking — the ability to produce many different ideas or solutions from a single starting point. Convergent thinking — the ability to narrow down to the best solution.

Alternative Uses Test (Guilford, 1961)

A classic test: given a common object (e.g., a comb), think of as many alternative uses as possible. The test measures four independent parameters:

Parameter	Meaning	Example (comb)
Fluency	Smoothness and quantity of ideas; did you get stuck?	Generating 10+ uses easily vs. only the hair-combing use
Flexibility	Ability to shift perspectives; openness to different categories of use	From hair care → drawing tool → doorstop → toy airplane
Originality	Uniqueness — ideas that no one else would think of	Using the comb as a stirrer or a musical instrument
Elaboration	Degree of detail and development of the idea	Not just “throw it” but “use it as a catapult by bending the teeth and releasing a paper pellet”

A creative person scores high on all four.

Functional Fixedness

The enemy of creativity: functional fixedness — the tendency to see an object only for its original intended purpose. Children are naturally more creative because they lack this fixedness. Adults impose patterns: "a comb is for combing hair." To be creative, you must break patterns.

Exam tip: The Alternative Uses Test is often used in selection (e.g., military, innovation roles). Expect to be evaluated on fluency, flexibility, originality, and elaboration — not just raw number of ideas.

Torrance Test of Creative Thinking (TTCT)

Ellis Torrance built on Guilford’s work, creating the most widely used creativity test in schools (still valid today). It assesses two dimensions:

flowchart LR
  A[Torrance Test of Creative Thinking] --> B[Verbal]
  A --> C[Figural]
  B --> D[Generate new words, anagrams, etc.]
  C --> E[Complete drawings, e.g., 10 circles → 10 different images]

Verbal: e.g., from the word “VERBAL”, create as many meaningful words as possible (VERB, LAB, REAL, etc.).
Figural: e.g., given 10 circles, draw a different object inside each circle. Or: improve an existing product (e.g., comb — make it foldable, self-cleaning, replaceable bristles).

The TTCT builds on Howard Gardner’s multiple intelligences concept.

Remote Associates Test (Sarnoff Mednick)

Creativity as the ability to connect apparently distinct domains. Given three words, find a fourth that associates all three:

Three words	Common associate	Domains
cottage, swiss, cake	cheese	Food, cheese varieties, dessert
computer, trap, mickey	mouse	Computing, hunting, cartoon

This test measures associative breadth: creative people can traverse widely separated semantic fields.

Exam tip: The Remote Associates Test predicts creative problem-solving more than standard IQ tests. Practice by finding links between unrelated concepts.

Key Takeaways

Creativity can be measured via divergent thinking tests (Guilford, Torrance, Mednick).
Alternative Uses Test → assess fluency, flexibility, originality, elaboration.
Functional fixedness blocks creativity; break patterns by forcing new uses.
Torrance Test covers verbal and figural creativity, widely used in education.
Remote Associates Test measures ability to connect distinct domains — the hallmark of creative intelligence.
Creativity is not fixed; you can train it by exposing yourself to multiple disciplines, cultures, and perspectives.

Honing Creativity Part-I

Creativity is not fixed; it can be developed. The mechanisms for honing creativity go beyond intelligence tests and require deliberate practice in four key areas: curiosity, associative thinking, hobbies, and multiple affiliations.

Curiosity — The Driving Force

Unbounded curiosity is the foundation of creative genius. It pushes individuals to explore across domains without regard for formal labels.

Leonardo da Vinci – illegitimate, no formal education, driven by insatiable curiosity. He dissected animals (including humans), designed military instruments, helicopters, a working parachute, painted, sculpted, wrote. His notebooks (one bought by Bill Gates for millions) show a mind that refused to be categorised: artist, anatomist, painter, sculptor, biologist, astronomer, mathematician.
Modern obstacle: Super-specialisation. Society compresses identities into narrow boxes (“doctor”, “engineer”, “artist”). Creativity thrives when these boundaries dissolve — when art and science mingle.

Exam tip: Curiosity is not just about asking “why” but about traversing fields. Any question about da Vinci’s creativity should highlight his refusal to be labelled and his constant learning across domains.

Associative Thinking

Associative thinking (or associative skills) is the ability to quickly connect ideas from disparate fields. Clayton Christensen, in The Innovator’s DNA, identifies this as a core trait of innovators.

How it works: You read something, see a video, hear a podcast, read a newspaper article, have a conversation — then seamlessly blend those inputs into your current work.
Why it boosts creativity: Creativity = novelty + utility. Novelty arises from new combinations. Everything in the physical world is made from ~120 elements (periodic table), each atom made of the same electrons, neutrons, protons, and ultimately energy (string theory). Creativity recombines existing building blocks into new forms.

Analogy for depth: At the subatomic level, matter and energy are the same vibration — Advaita philosophy (Adi Shankaracharya) spoke of this as Maya. The point: reality is already one interconnected field; associative thinking mimics that truth.

Risk: Over-identifying as a “science student” or “management student” limits associative thought. “Your professional identity is not your life.”

The Role of Hobbies

Unstructured time and unstructured play are essential for developing imagination, curiosity, and self-control. Modern schedules (especially for children) often leave zero free space, killing these abilities.

Hobbies are not “unproductive” – they restore creativity.
Personal example (instructor): chess (left brain, temporal thinking – planning moves ahead) + guitar (right brain, spatial thinking – music lives in space). This dual practice boosts memory and creative idea generation.
Famous examples:
- Albert Einstein – violin hobby; he said if not a physicist, he’d have been a musician.
- Haruki Murakami – long-distance running (10–15 km daily) + swimming; attributes enormous creativity to these hobbies.
- Nobel laureates – 20% more likely than peers to have an artistic hobby.

Three benefits of hobbies:

Benefit	Explanation
Self‑confidence	A domain free from competition and one‑upmanship.
Different perspectives	Breaks the tunnel vision of work/study; an idea from a hobby can solve a day‑job problem.
Exposure to different people	Hobby groups connect you with diverse backgrounds, breaking the “same people, same drag” cycle.

Exam tip: The Nobel laureate statistic (20% more likely to have an artistic hobby) is a high‑yield data point. It directly links leisure to creative achievement.

Multiple Affiliations

Who all are you? (Hindi: tum kaun kaun ho?) Having multiple identities — artist, scientist, social worker, meditative person, etc. — prevents a hollow life and fuels creativity.

The consulting partner story: In a Big Five firm, 50 partners achieved their 20‑year dream — yet none was happy. They had poured all energy into one goal; once attained, life felt pointless. The joy was in the pursuit, not the arrival.
Warning: When you invest all your identity in a single job/career, that job becomes parasitic. If the employer turns on you, your whole life crumbles.
Solution: Deliberately cultivate multiple affiliations. Something gives you money, something gives pleasure, something gives purpose, something gives learning, something gives solace. Balance is critical from the start of your career.

Key insight: “No cause is worth your life. Before you manage an organisation, manage yourself.”

Key takeaways

Curiosity is the foundational driver — follow it across domains without letting labels limit you.
Associative thinking creates novelty by recombining ideas from different fields; avoid over‑specialisation.
Hobbies (especially musical or physical) boost self‑confidence, broaden perspectives, and connect you to diverse people.
Multiple affiliations prevent identity collapse and sustain long‑term creativity and well‑being.
The happiness is in the pursuit, not the arrival — cultivate multiple dimensions of life before you reach any single pinnacle.

Honing Creativity – Part II

This part continues the practical principles for honing creativity, covering networking (flesh-and-blood, not online), taking half chances, the role of humor, and meditation as a daily practice. Each principle builds on the idea that creativity thrives on deliberate exposure to uncertainty, vulnerability, and non-attachment to outcomes.

Networking: Wide and Shallow vs. Narrow and Deep

Networking here means face-to-face, purposeful interaction – not social-media follower counts. Two distinct networks serve different roles:

Network	Ideal shape	Why?
Personal	Narrow and deep	Too wide drags you down with others’ expectations, dampening radical or creative moves.
Professional	Wide and shallow	Maximises exposure to diverse ideas, people, and uncertainty. Resist converting professional contacts into personal ones – blending leads to difficulty saying “no”, eroding trust and draining emotional energy.

Exam tip: The key trap is trying to “get intimate” with professional contacts (a common cultural inclination). Maintain the boundary – you can be warm and purposeful without deepening every relationship.

Networking boosts creativity because it forces you to:

Expose yourself to uncertainty – you don’t know how the other person will react.
Listen and learn – show genuine interest; you gain insights from strangers (e.g., a Turkish traveller’s geopolitical views, an Egyptian visitor’s perspective on India).
Be the first to strike – setting the agenda of the conversation gives you the upper hand, even if the other person is talkative. Use active listening to steer the dialogue.
Accept non-permanence – not every encounter needs to become a long-term association. A single fruitful transaction is enough. Avoid the emotional toll of trying to convert every meeting into something “big”.

Taking Half Chances

Creativity requires the willingness to act before you feel fully ready. A “half chance” is an opportunity that lies near your zone of influence (but not outside your zone of concern). When it does, say an emphatic “yes” and then prepare yourself on the way.

Effect of taking half chances	Explanation
Lowers fear of failure	Inhabits the idea that “I must be fully prepared”.
Reveals hidden competencies	Like the mythical Hanuman, you may not know your own strength until you are forced to use it. The mind is a parachute – it opens only when you’re falling.
Creates serendipity	The lecturer’s book Design Your Thinking (Penguin Random House, 2020) arose from a LinkedIn article read by an editor. He had no chapter ready – he sent a 2000-word article, converted from an existing piece. That half chance led to a national bestseller, whereas his planned PhD-based book remains unwritten.

Example: M.S. Dhoni’s half chance – He entered the Indian cricket team as a wicketkeeper, not as a batsman or bowler. That provisional role turned into captaincy of a rookie T20 team in 2007, then a World Cup win – converting half chances into full chances.

Exam tip: The boundary is critical – if the opportunity lies beyond your zone of concern, say no clearly. If it is within or near your zone of influence, take it.

Humor and Creativity: Shared Neural Circuits

Creativity and humor are almost synonymous in their neural circuitry. Both follow the same structure:

80% linear – The idea (or joke) starts in a familiar, logical pattern to hook the audience.
20% pattern break – A sudden violation of that logic produces either a laugh (humor) or an “amazing” insight (creativity).

Definition: Humor is a benign violation of logic – a logical break that is safe, not threatening, leading to the “haha” moment.

	Humor	Creativity
Starting point	Linear story (80%)	Common, familiar idea (80%)
Break	Benign violation of logic (20%)	Novel twist (20%)
Outcome	Laughter	Novel, useful idea

Why stand-up comedians are highly creative:

They are always in content-creation mode – observing, writing (e.g., Jerry Seinfeld writes two hours daily).
They improvise on stage when a joke fails – a pure creative response.
They practice self-deprecating humor – a hallmark of creative people. Taking yourself lightly (“nobody takes you seriously anyway”) frees you to tolerate randomness and rejection.

Meditation: The Three Daily Practices

Meditation (distinct from religion – spirituality asks questions, religion offers answers) centres the mind where the body is. The goal is mindfulness: full awareness of the present moment. The lecturer uses three practices daily:

Non-resistance – Accept reality as it is. Most psychological pain comes from resisting what has already happened (e.g., “I shouldn’t have had that accident”). Acceptance gives you the power to deal with the situation; denial fuels self-pity.
Non-attachment – Aspire, but do not become attached to outcomes, people, or ideas. The philosophy of Advaita (non-duality) teaches that your fundamental self (Brahman) does not change with success or failure. Equanimity reduces the pain of desire (as taught by Gautama Buddha).
Non-judgment – Avoid prematurely evaluating people, situations, or ideas. (Referenced from earlier discussion in the module.)

Practical tip: The practices do not require closed eyes or mantras. Any technique that centres attention on the present moment is meditation. The lecturer meditates each morning and finds it improves focus, productivity, and creative structuring of courses and books.

Exam tip: In the Indian context, these meditative principles are indigenous – no need to import. They are nuggets from 5,000 years of culture. Even though design thinking is an imported concept, the underlying mindset (non-resistance, non-attachment, non-judgment) has long been practised in India.

Key takeaways

Build a wide, shallow professional network and a narrow, deep personal network – do not blend them.
Take half chances when they fall near your zone of influence – they reveal hidden strengths and create serendipity.
Humor and creativity share an 80/20 pattern: linear setup → benign violation. Practice self-deprecating humor to embrace randomness.
Daily meditation (non-resistance, non-attachment, non-judgment) sharpens focus and fosters a creative, equanimous mindset.
Creativity demands tentativeness, tolerance for rejection, and accepting non-permanence in relationships and outcomes.

Rules of Ideation

Ideation sessions often feel chaotic, but a set of counterintuitive rules separates productive brainstorming from aimless discussion. These rules are grounded in the behavior of highly creative people and the principles of design thinking.

Rule 1: Quality Comes from Quantity

Intuition: Most people would rather have a few good ideas than a lot of average ideas. But great ideas almost never appear fully formed; they emerge from a vast pool of mediocre, half-baked, or even bad ones. The "secret of greatness" is ferocious productivity – creating a large volume of work so that, by the law of averages, some of it becomes remarkable.

How it works: A funnel process. Generate as many ideas as possible (quantity), then distill them into the best subset (quality). The final set derived from a large pool is far richer than one taken from a small pool.

Example – Marico Coconut Farmers Workshop (India):
A two-day workshop in Tamil with 35 coconut farmers generated 500 ideas on the single topic "How to improve the yield of copra (coconut)."
The facilitator did not start from zero to 50; they distilled 500 → 50. The resulting 50 ideas were far more insightful than any "first 50" would have been.

Key insights:

Nature: At any given time, nature produces a gigantic variety of species. By the law of averages, some subspecies thrive.
Linus Pauling: "If you want good ideas, have a lot of them."
Thomas Edison: "Genius is 1% inspiration and 99% perspiration."

Takeaway: In a brainstorming session, do not settle for 2–3 ideas. Challenge the team to generate 100 or more. The methods and techniques enable reaching that target.

Rule 2: Build on Others’ Ideas (Yes, And)

Intuition: The default response to a new idea is often "No, but…" – a reflexive dismissal that kills confidence and blocks collaboration. Instead, adopt a "Yes, and…" mindset: acknowledge the idea and add to it.

Technique: Replace no-butt (saying "No, but…") with "Yes, and…" – explicitly state that the idea is good and propose a way to improve it. This principle:

Strengthens the idea by adding perspectives.
Preserves team morale and encourages further contribution.
Avoids unnecessary friction and hierarchy clashes.

Rule 3: Defer Judgment

Intuition: Judging an idea prematurely (or judging the person who proposed it) shuts down innovation. Many ideas that seem impossible in foresight become obvious in hindsight. Being non-judgmental opens learning possibilities for both the self and the group.

Story – Stephen Covey on the Subway:
Covey saw two teenagers creating a disturbance. He approached their father angrily, demanding he control them. The father replied, "We are returning from the hospital; their mother just passed away. I don't know how to tell them." Covey instantly regretted his judgment. The dominant emotion after judging is regret, not enlightenment.

Historic examples of "impossible" ideas now reality:

Leaving home without a wallet.
Walking into an airport without showing ID.
Paying a street vendor (panwala) directly to his bank account without knowing his account number, IFSC code, or even his name. (UPI-based payments)

Victor Hugo: "Nothing can stop an idea whose time has come."

Practical rule: When an idea surfaces, do not evaluate it immediately. Let it breathe. Judgment belongs later in the process.

Rule 4: Sketch, Don’t Speak

Intuition: The human hand and brain co-evolved. Using hands for sketching, doodling, or modelling engages the brain more deeply than speaking or even writing. Visual thinking (a core tenet of design thinking) forces the idea to be fleshed out with concrete details.

Three methods of expressing an idea:

Speak – verbal description (abstract, can be vague).
Write – text (still linear).
Draw – visual (non-linear, detailed, rich in context).

Drawing is the most powerful because it:

Adds detail and clarifies the concept for the drawer.
Makes it easier for others to add to the idea (they can modify a sketch rather than argue with a spoken statement).
Enables anonymous brainstorming – when ideas are written/drawn and posted without names, hierarchy and reputation disappear. A junior team member can freely improve on a boss's sketch.

Exam tip: In any group with power distance (e.g., boss vs. junior), anonymous sketching prevents the junior from feeling unable to critique or build. This yields better ideas.

Summary Table of Ideation Rules

Rule	Core Action	Benefit	Pitfall to Avoid
1. Quality from quantity	Generate many ideas first, then filter	Breakthrough ideas emerge from volume	Settling for few good ideas too early
2. Build on others’ ideas	Use "Yes, and…" instead of "No, but…"	Strengthens ideas, preserves team confidence	Dismissing an idea and the person
3. Defer judgment	Suspend evaluation during generation	Allows impossible-seeming ideas to evolve	Judging prematurely (regret later)
4. Sketch, don’t speak	Draw ideas instead of only verbalizing	Adds detail, enables anonymous collaboration	Relying only on spoken or textual ideas

Key takeaways

Quantity first: The best ideas come from a large pool – push for volume, then refine.
Yes, and: Build on every suggestion; avoid "no, but" to keep the flow going.
Defer judgment: An idea that looks impossible now may be obvious tomorrow; judge later.
Sketch: Visual thinking engages the brain and reduces hierarchy; use anonymous sketching to flatten power dynamics.
All four rules together create a safe, productive environment for radical innovation.

Exam tip: Remember the Marico example (500 → 50) and the Covey subway story – they illustrate the why behind the rules. Be ready to explain why quantity precedes quality and why judging an idea too early is dangerous.

Why Brainstorming Doesn't Work

Brainstorming – the classic group idea‑generation method – was coined by American marketing executive Alex Osborne in the 1950s. Its tenets include free‑flowing conversation, focusing on one idea at a time, and building on others’ ideas. Yet decades of research show a stark result: brainstorming fails. Both the quantity and quality of ideas produced by a group are lower than the total output of the same number of people working alone.

Why then does it remain so prevalent? Because brainstorming serves other functions (e.g., team bonding, feeling of participation). But for pure idea generation, the evidence is clear – it underperforms.

Four Causes of Brainstorming Failure

Cause	Description	Result
Idea blocking	While listening to another person, a new idea pops up. You either ruminate on it (stop listening) or listen (lose the idea). Often you “park” the idea, but if it’s tangential it never gets voiced.	Many ideas – especially novel ones – are lost.
Groupthink	The group converges on one way of thinking, often driven by power differentials (e.g., a senior’s idea is not challenged). Everyone complies, saying “great idea” even when it is poor.	Ideas never get contested, evaluated, or evolved.
Evaluation apprehension	Participants fear their ideas will be critically judged, especially if contrarian. Radical or divergent ideas (e.g., replacing IC engines with battery or hydrogen fuel cells) are suppressed.	Only safe, incremental ideas surface; breakthroughs are stifled.
Social loafing (free riding)	In a group, some individuals exert less effort, relying on others to carry the load. Per‑person productivity drops as team size grows – like a tug‑of‑war where not everyone pulls equally.	Fewer total ideas; uneven contribution.

Exam tip: The four causes are a high‑yield list. Remember: idea blocking, groupthink, evaluation apprehension, social loafing. Each is distinct – know the mechanism.

Breaking Groupthink – The Alfred Sloan Method

Alfred Sloan (former CEO of General Motors) deliberately disrupted groupthink. After a meeting where everyone agreed, he would say: “Now that we all agree on this, let’s meet again tomorrow so that we don’t agree.” He understood that unanimous agreement signals insufficient thinking; disagreement is necessary for ideas to evolve.

The Alternative: Brainwriting

Brainwriting addresses the flaws of brainstorming by replacing spoken ideas with anonymous, written contributions. How it works:

Each person receives a pack of Post‑it notes.
Everyone writes their ideas on the notes.
Notes are placed in a central urn (or shared space).
Anyone picks a note at random, reads it, adds to it, and returns it.
Over time, the pool of ideas grows in both quantity and quality.

Why it works:

Anonymity – no name on the idea; no vested interest; anyone (including the author) can critique it.
No compulsion to convince – writing avoids the social pressure to defend or sell an idea.
Anonymity breeds creativity – just as superheroes wear masks to do radical things, removing identity frees people from the fear of losing status or being judged.

Key insight: In online settings (anonymous submissions, aliases), the wisdom of crowds becomes unbiased – “you can’t fool everybody every time.”

Optimal Team Size: Two

Size 2 – The best. Aligned on objective, but can differ in personality and perspective. Minimises all four failure modes.
Size > 2 – A crowd. All the brainstorming problems (idea blocking, groupthink, evaluation apprehension, social loafing) reappear.
Size < 2 – A loner. Lacks the benefit of collaborative generation.

Pair with people who are unlike you – different personality types, complementary skills – to produce creative “aberrations” that are more creative than abrasive.

Key takeaways

Brainstorming as typically practised reduces idea quantity and quality compared to individuals working alone.
Four root causes: idea blocking, groupthink, evaluation apprehension, social loafing.
Groupthink can be mitigated by leaders who actively challenge agreement (e.g., Sloan’s “agree to disagree” method).
Brainwriting (anonymous written idea exchange) overcomes these flaws by decoupling contribution from identity.
The ideal team size for idea generation is two – a pair that is aligned on objectives but divergent in perspective.

Challenging Assumptions

Challenging assumptions is a technique that identifies and questions the implicit beliefs underlying a product, service, or behavior. Every product, service, or behavior carries a set of unexamined assumptions; systematically breaking them uncovers radical improvements.

Intuition and Why It Matters

Most innovation happens not by adding features but by removing a hidden constraint. For example, transferring money used to require the recipient’s bank account number and IFSC code – an assumption that was never questioned until UPI arrived. UPI removed the assumption that you need account details; then QR codes removed the need to know the phone number; SMS-based transfers even removed the need for a smartphone. Each “remove” was a birth of innovation.

The Process

Write down all assumptions about the product, service, or behavior you want to improve. Be exhaustive – include everything from physical attributes to social norms.
Example: For a car – assumptions include “needs four wheels”, “needs five seats”, “needs two wipers”, “needs a spare tyre”, “needs a steering column”, “needs a driver’s license”.
Challenge every assumption – nothing is sacrosanct. Ask “Why do I need this?”, “Why must it be this way?”
Example: In cricket, the assumption that saliva is needed to shine the ball was challenged during the pandemic; sweat became the alternative.
Overcome the assumption – find a way to solve the problem without the assumed element.
Example: Steve Jobs removed the fan from the original Mac by designing a heat dissipation system that worked without fans – eliminating noise and dust collection. He also removed screw holes from the bottom of the Mac, preventing dust accumulation.

Classic Examples of Assumptions Challenged

Product / Concept	Assumption Challenged	Innovation
Phone	A phone must have physical buttons.	iPhone – touchscreen only.
Computer	A computer must have a fan to cool.	Mac – fanless design.
Fan	A fan must have blades.	Dyson Air Multiplier – bladeless.
Scooter	A scooter must carry a spare wheel.	Modern two-wheelers no longer have a stepney (tyre quality and tubeless tech made it obsolete).

Beginner’s Mind

A beginner’s mind – viewing the problem as if for the first time – is essential. Preconceived notions are “vestiges of the past.” As the story of the emperor’s new clothes shows, only a child (a beginner) can see the obvious truth that everyone else is blind to. Students living in the canteen daily may never challenge its assumptions, but an outsider can question everything.

Exam tip: The “student canteen” example is a classic test – be ready to list assumptions of a canteen (e.g., food is served at a counter, payment is cash, seating is fixed) and propose improvements by challenging each one. This is a high-yield application.

Key takeaways

Innovation often comes from removing, not adding – challenge the core assumption.
Process: write assumptions → challenge each → overcome without the assumption.
Fundamental assumptions (e.g., “phone needs buttons”) yield the most radical innovations.
Adopt a beginner’s mind; ignore “how it has always been done.”
Apply the technique to everyday life to build a creative habit.

Brain Writing (Mind Mapping)

Brain writing is a structured ideation method that uses a mind map to capture and connect ideas spatially. The term mind map was coined by Tony Buzan, who showed that our brain thinks spatially and associatively, not linearly.

Why Mind Maps Work

When you watch a movie, you remember the plot (gist) easily but struggle to recall character names (detail). The brain is an optimization engine: it stores gist and loses detail. Mind maps mimic this structure – the core idea at the centre, with branches for sub-problems and solutions radiating outward. Because the map is spatial, ideas can “talk to each other” – connections emerge that would be missed in a linear list.

Step-by-Step Brain Writing

Define your objective at the centre of a page.
Example: “Improve performance of an electric bike.”
Identify the main problems or sub-topics as branches.
Example for electric bike: range, charging time, vibrations, safety & comfort, drainage/short circuit.
For each problem, list possible solutions as further branches.
Each sub-problem can be delegated to a specific team – narrow focus allows laser-sharp solutions.
Look for connections between ideas on different branches – novel combinations are the essence of creative ideas.

Practical Tips for Effective Mind Mapping

Use an unruled notebook – no lines force you to write spatially, not linearly.
Use multiple colours – colour coding activates different parts of the brain and aids memory.
Doodle and draw – your brain thinks in pictures, not words. Drawing bypasses the effort of translating mental images into language.
Write in your native language – translating into a foreign language loses nuance and slows thinking. Many highly creative cultures (Germany, Japan, Korea) insist on brainstorming in their mother tongue.

Exam tip: The three tips (unruled notebook, multiple colours, doodling/native language) are a common short-answer question. Also remember: “a creation takes place twice – first in the mind, then in reality.” The mind map of a book usually comes before the book is written.

Key takeaways

Brain writing uses mind maps to capture spatial, associative thinking.
Process: centre (objective) → branches (problems) → sub-branches (solutions) → connect branches.
Mind maps reveal novel connections that linear lists miss.
Practical tips: unruled pages, colour, doodles, native language – they reduce translation loss and enhance creativity.
The technique applies to note-taking, project planning, and any complex ideation task.

Across the Value Chain (Buyer Utility Map)

This technique, adapted from the buyer utility map in Blue Ocean Strategy (Kim & Mauborgne, 2005), breaks a problem into stages along a customer journey (or any process). At each stage, the innovator asks: What value can we add? The matrix approach systematically generates ideas by crossing stages with strategic objectives.

The matrix structure

Stages – Sequence of steps in the customer’s journey (e.g., purchase → use → disposal).
Objectives – Desired value dimensions (e.g., convenience, efficiency, sustainability).

Each cell (stage × objective) is a prompt: How can we improve [objective] at this stage?

Worked example: cafeteria customer journey

Five stages:

Stage	Description
1. Get coupon	Obtain a physical paper coupon from the cash counter
2. Join queue	Wait in a single queue for food
3. Find a seat	Secure a table and sit
4. Eat	Consume the meal (including possible refills)
5. Dispose tray	Return tray, separate waste (spoons, leftovers, bowls, tissue, glass)

Three objectives:

Convenience – How easy is each step?
Efficiency – Time and cost savings.
Sustainability – Minimize waste (paper, plastic, food).

The matrix has 15 cells (5 × 3). Example ideas from the lecture:

Stage	Convenience	Efficiency	Sustainability
Get coupon	Use an app to pay digitally; no paper coupon needed	–	Eliminates physical paper waste
Join queue	–	Separate queues: one for full meals, one for refills only	–
Dispose tray	–	Streamlined disposal with labelled containers	Separate leftover food → reduce food waste
Eat / refill	–	–	–
Find a seat	Different table sizes (individual, small team, large team)	–	–

Exam tip: The power of this technique lies in breaking the problem into small, concrete pieces. A broad question (“improve the dining experience”) yields fewer ideas than asking specific questions for each cell. You are expected to fill all 15 boxes; an empty box is a missed opportunity.

Why it works

Focuses attention on one sub-problem at a time, avoiding the overwhelm of a vague challenge.
Guarantees coverage – every stage–objective combination is considered.
Reveals hidden opportunities at stages that might be overlooked (e.g., disposal).

Key takeaways — Across the Value Chain

Map the customer journey (or process) into discrete stages.
Define 2–4 high-level objectives (e.g., convenience, efficiency, sustainability, cost, safety).
Generate one idea per cell in the resulting matrix.
The approach is generic: applicable to any product, service, or process.
Borrowed from Blue Ocean Strategy (Kim & Mauborgne); also known as the buyer utility map.

Tiers of Customers

A companion technique from Blue Ocean Strategy that segments current and potential customers into four groups. The goal: identify how to expand the market by understanding why each group behaves as it does.

The four tiers

Tier	Description	Example (cafeteria)
Loyal customers	Always choose your product/service despite better alternatives.	Staff who eat all meals at the canteen, give feedback, waste little food.
Dissatisfied customers	Were users but are actively looking to switch due to unmet needs.	Those bored with the same menu; want non‑vegetarian options not offered.
Refusing non‑customers	Have consciously decided not to use your offering.	People who feel the canteen is “beneath them,” have heard bad reviews, or prefer eating outside.
Unexplored non‑customers	Not even in your consideration set; unaware the offering exists or is available to them.	Campus visitors who do not know the staff canteen is open to guests (at a higher price).

Using the tiers for ideation

For each tier, ask three questions:

Who are they? – Identify the specific segment.
Why are they in this tier? – Root causes (e.g., boredom, misinformation, lack of awareness).
How can we move them? – Actions to retain, convert, or onboard.

flowchart LR
    A[Loyal] -->|Retain loyalty| A
    B[Dissatisfied] -->|Fix pain points| A
    C[Refusing] -->|Remove barriers & encourage trial| B_or_A
    D[Unexplored] -->|Educate & make accessible| C_or_A

Exam tip: The largest segment in most markets is unexplored; the smallest is loyal. The most profitable opportunities often lie at the bottom of the pyramid (refusing and unexplored) because they represent entirely new demand.

Key takeaways — Tiers of Customers

Four tiers: loyal, dissatisfied, refusing, unexplored.
Loyal – smallest group; protect them. Unexplored – biggest group; educate them.
For each tier, diagnose why they behave that way, then design ideas to shift them upward.
Works hand‑in‑hand with the value‑chain matrix: use the tiers to define which customer journey to analyse.

Connecting the two techniques

The value‑chain matrix focuses on what can be improved at each stage of a journey. The tiers of customers focuses on who the targets are. Together, they provide a complete framework:

Use tiers to identify an underserved segment (e.g., refusing customers avoid the queue).
Use across the value chain to generate specific ideas for that segment’s journey (e.g., redesign the queue system, add a fast‑track lane).

This structured, two‑pronged approach prevents vague brainstorming and ensures every cell and every segment is consciously examined.

Lateral Thinking

Lateral thinking (coined by Edward de Bono) means thinking "sideways" — deliberately suspending logic to generate novel ideas. The opposite is vertical thinking, which proceeds step-by-step, logically. Lateral thinking encourages introducing random words, making errors, and taking deviations, with the aim of returning to the original problem with a fresh insight.

Four Trigger Tools for Lateral Thinking

Trigger	Definition	Example (Cafeteria Context)
Subtraction	Remove a component entirely.	Remove the physical coupon; use a mobile phone receipt instead.
Task Unification	Combine two tasks into one.	While taking food, automatically record food preferences (quantity, type) by observing selection behaviour.
Multiplication	Multiply a component — make multiple copies.	Have two food queues instead of one; multiple disposal stations; multiple coupon counters.
Division	Split a component into parts.	Separate queues for vegetarian/non-vegetarian, South Indian/North Indian, or guests/staff.

Why generate many ideas: Seemingly stupid ideas can combine to create profound innovations. Examples: sand + glued paper = sandpaper; cellophane + glue = cello tape; tape + adhesive on both sides = double-sided tape. Innovation often arises from combination, not entirely new elements.

Exam tip: Lateral thinking triggers are applied by zooming in on a specific step (e.g., getting a coupon) and asking Can I subtract, unify, multiply, or divide this?

SCAMPER

SCAMPER is an acronym providing seven more triggers for ideation (an extension of lateral thinking triggers).

Letter	Stands for	Meaning	Example: Parking Problem
S	Substitute	Replace one element with another.	Substitute private vehicles with campus shuttles (guests park outside, use shuttles).
C	Combine	Merge two elements or processes.	Encourage carpooling via registration system (same destination → reduce cars).
A	Adapt	Temporarily adjust existing infrastructure.	Use grounds or non-parking areas for overflow parking during events.
M	Modify	Permanently change a system or structure.	Convert roads to one-way to free one side for parking.
P	Put to another purpose (Repurpose)	Use the element for a different function.	Use parked cars as a showcase for market research (brands, colours).
E	Eliminate	Remove a component entirely.	Eliminate need for parking (drop-off policy; let attendees attend online).
R	Reverse (Rearrange)	Flip logic or sequence.	Instead of free parking, charge a fee — or offer a rebate for not bringing a car (mall parking reimbursement model).

Exam tip: Distinguish Adapt (temporary, like a chameleon) from Modify (permanent, designed preemptively). This distinction is often tested.

Analogous Design

Analogous design (from analogy = similarity) draws inspiration from unrelated domains where the same fundamental problem has already been solved. The process:

flowchart LR
    A[Your problem] --> B[Generalize the problem]
    B --> C[Shift to a far-away domain]
    C --> D[Understand their best practice]
    D --> E[Contextualize that best practice to your problem]

Example: Improving canteen service (IIMB) using airline food service

Problem element	Airline best practice	Contextualized idea
Space optimization	Tray design fits snugly into cart; single serving limits quantity.	Design canteen trays of fixed size to reduce wastage and serve uniform portions.
Quick service during peak hours	Divide passengers into aisle sections; each air hostess handles one aisle.	Divide canteen counters by zones; assign staff to specific zones.
Food allergy / preference	Airlines ask veg/non-veg beforehand.	Display full menu in advance; allow partial ordering (e.g., only chapati).

Key principle: Go far from your domain

The farther the domain, the more novel the ideas. Example exercises:

Improve parking efficiency? Learn from stadiums managing crowds during World Cup or Olympics.
Increase student attention span? Learn from pilots staying alert on long, boring autopilot flights.

Key takeaways – Lateral Thinking & SCAMPER

Lateral thinking suspends logic to generate ideas; opposite of vertical thinking.
Four triggers: Subtraction, Task Unification, Multiplication, Division.
SCAMPER adds seven more: Substitute, Combine, Adapt, Modify, Put to purpose, Eliminate, Reverse.
Apply triggers by zooming into one step of a process and asking "Can I ___ this?"
Many ideas → combine simple ones → breakthrough innovations (sandpaper, cello tape).
Distinguish Adapt (temporary) vs Modify (permanent).

Key takeaways – Analogous Design

Find problems already solved elsewhere: generalize → shift domain → learn → contextualize.
The more distant the domain (e.g., airlines for canteens, stadiums for parking), the more original the solution.
Analogous design works by transferring principles, not copy-pasting solutions.

Design for the Extreme

Design for the Extreme pushes a product or service into an extreme context (user, environment, constraint) to uncover hidden challenges; solutions developed for that extreme are then brought back to the mainstream — often unlocking unexpected benefits for everyone.

How it works

Identify an extreme scenario: a user with a disability, a rare constraint, a crisis.
Design or adapt the product/service to solve that extreme case.
Return to the normal context and evaluate how the same solution improves the mainstream experience.

Examples from the lecture

Extreme user/situation	Solution designed for extreme	Mainstream benefit
Hearing‑impaired movie viewers	Subtitles in foreign films	Increased viewership for all audiences
Visually impaired phone users	Vibration alert feature	All users rely on vibration mode
Visually impaired readers	Read‑aloud feature in MS Word	Proofreading aid for everyone
Pandemic lockdown (extreme situation)	Quick‑commerce delivery (10‑minute deliveries)	Became a permanent new industry
Theaters closed during pandemic	OTT direct movie releases	New normal of streaming releases

Why it works

The extreme case forces designers to solve fundamental friction that is often ignored in routine design. Those frictions are latent for mainstream users too — addressing them makes the product more robust, inclusive, and often more convenient.

Applying it to a cafeteria (exercise from lecture)

List extreme users (e.g., wheelchair user, no mobile phone, foreigner with different palate) and extreme situations (e.g., food poisoning, gas outage, flooding, blocked route) → preemptively engineer solutions.

Exam tip: The key trade‑off is over‑engineering in the extreme case vs. simplicity in the normal case. The pandemic proved that companies prepared for extremes (e.g., quick commerce) emerged stronger.

Key takeaways

Design for the Extreme = solve for the edge case → harvest benefits for the mainstream.
Examples: subtitles, vibration, read‑aloud, quick commerce, OTT releases.
Method: identify extreme user or context → design solution → adapt to normal.
Proactive anticipation beats reactive crisis management.

Six Paths Framework

The Six Paths Framework (from Blue Ocean Strategy) provides six lenses to break out of a crowded market and create an uncontested space. Each path shifts the focus from competing within existing boundaries to reconstructing them.

The six paths

Path	Question	Example (Electric Vehicles)
1. Alternate industries	Which other industries can use this product?	Cargo intracity transport; rental fleets (e.g., BluSmart Cabs)
2. Strategic groups	Can you move from one tier to another?	Position EVs for luxury segment (Tesla, BMW, Audi) instead of economy
3. Buyer chain	Are you targeting the wrong user group?	Focus on non‑traditional users (e.g., corporate fleets vs. individual buyers)
4. Complementary products/services	What else does the customer need?	Lifetime free charging network bundled with car
5. Emotional vs. functional orientation	Shift from functional to emotional appeal	Market EVs as caring/silent personality rather than just eco‑friendly
6. Time and trends (retro/future)	Can you revive past trends or leap to future trends?	Retro: banana‑leaf dining, clay‑pot tea; future: self‑driving subscription models

Worked application (from lecture)

For electric cars in a crowded market:

Path 1: Use EVs for intra‑city cargo or rental (BluSmart).
Path 2: Target luxury (status symbol of environmental consciousness).
Path 4: Offer complimentary charging network as differentiation.
Path 5: Rebrand EV as “a quiet, caring choice” — emotional branding.

Exam tip: The Six Paths Framework is especially powerful for startups entering a saturated market. Apply all six systematically to find a unique differentiator.

Key takeaways

Six Paths = alternative industries, strategic groups, buyer chain, complementary products, emotional/functional pivot, time/trends.
Each path redirects focus from competition to value innovation.
Use a table to map your product across all six paths.

Nine Windows (TRIZ)

The Nine Windows technique, drawn from TRIZ (Theory of Inventive Problem Solving, by Altshuller), breaks a problem into a 3×3 grid of time (past, present, future) and system level (subsystem, system, supersystem). It reveals intervention points that are invisible when looking only at the current system.

The 3×3 matrix

	Past	Present	Future
Supersystem	How did the broader context work?	Current network, social value, infrastructure	Future connectivity, policies, norms
System	What was the original product/service?	The current offering (e.g., bus)	Next‑generation offering
Subsystem	What were the components?	Current seats, ticketing, pricing, routes	Future technological upgrades

Application to public transport (lecture example)

Problem: People unwilling to use public transport.

	Past	Present	Future
Supersystem	Status of public transport as a social equalizer	Poor connectivity, low status in many cities	Multimodal single‑ticket systems (Singapore), carpooling income integration
System	Double‑decker buses (old charm)	Standard single‑decker diesel buses	Electric double‑decker buses (Mumbai)
Subsystem	Conductor‑based ticketing, bench seats	Digital ticketing, air conditioning, CCTV	Interiors matching aircraft comfort (Vande Bharat); high‑speed dedicated corridors

How to use it

Place the current system in the centre cell.
Populate the eight surrounding cells by asking: What existed before? What’s the broader context? What are the components?
Look for innovations by borrowing past features (retro) or leveraging future possibilities (super‑system integration, subsystem upgrades).

Expanding innovation dimensions

The technique works beyond transport. For a coffee house:

Subsystem innovation: Coffee preparation method, interior design, pricing model, product mix.
Supersystem innovation: Reposition the coffee house as a coworking space, dating venue, counselling centre, study hall, art studio, or bookshop.

Exam tip: Nine Windows is most powerful when the product itself cannot change — innovate at the subsystem or supersystem level instead.

Key takeaways

Nine Windows = 3 (time) × 3 (system level) grid.
Reveals opportunities in past practices, subsystem components, and supersystem purposes.
Examples: Mumbai’s retro electric double‑decker bus; Vande Bharat (aircraft‑like interiors); Singapore’s single‑ticket multimodal transport.
Can be applied to any product or service, especially when incremental product innovation is hard.

Learn, Observe and Ideate

After identifying problems, the next step is to generate creative solutions. Ideation is a deliberate, structured process that pushes beyond obvious answers by applying specific techniques. The raw material for this process comes from observing and learning about the problem context—typically through stakeholder interviews, immersion, and data collection.

The Ideation Process Flow

flowchart LR
  A[Identify Problems] --> B[Observe & Learn\n(stakeholder interviews,\nfield insights)]
  B --> C[Ideate\n(apply creativity techniques)]
  C --> D[Prototype\n(Module 4 – build &\ntest ideas)]
  D --> E[Refine & Implement]

The output of ideation is not a final solution but a set of candidate ideas ready for prototyping and testing.

Key Ideation Techniques

Technique	Description	Example Application
Challenging Assumptions	Question taken-for-granted constraints (e.g., "Why must the canteen close at 3 PM?")	Rethink operating hours or menu structure
SCAMPER	Structured checklist: Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse	Modify serving process → self-service kiosks
Lateral Thinking	Approach indirectly via provocation, random words, or reframing	Use a hospital tray system to inspire a canteen layout

These techniques can be applied across the entire value stream—from sourcing and preparation to dining and waste disposal.

Working Mode

Individual or team – collaboration with course peers and people outside the cohort enriches ideas.
Value-stream thinking – don't limit ideation to a single pain point; consider all stages of the user journey.

Exam tip: The strongest ideation sessions layer techniques. Start by challenging assumptions to break fixed thinking, then run SCAMPER for systematic variation, and finish with lateral thinking to leap into genuinely novel territory.

Link to Prototyping (Module 4)

Ideation feeds directly into prototyping – building low-fidelity models (physical, digital, or role-playing) to test the most promising ideas. The goal is to demonstrate solutions quickly and gather feedback before investing in full development.

Key takeaways

Ideation is a structured step after problem identification, not unstructured brainstorming.
Core techniques: SCAMPER, lateral thinking, and challenging assumptions.
Work collaboratively and across the entire value stream.
Ideas from ideation are candidates for prototyping, not final solutions.
The process is iterative: learn → ideate → prototype → test → refine.

Inspire, Empathise and Define

Module 2: Inspire, Empathise, and Define – Overview

This module marks the beginning of a live project set in the IIM Bangalore staff canteen (≈400 daily diners). The goal is to practise the first three stages of the design-thinking process:

Inspire – uncover why a problem is worth solving.
Empathise – understand users (both service providers and consumers) from their vantage point.
Define – narrow down the broad problem space to a specific, actionable problem to take forward.

The three stages at a glance

Stage	Core question	What you do
Inspire	Why should we solve this?	Elevate understanding of the bigger picture, sense unmet needs.
Empathise	What do the users really need?	Immerse yourself in users’ experiences; gather raw, unfiltered responses.
Define	Which specific problem should we solve now?	Synthesise empathy findings; filter out noise; pick a problem worth solving.

The live-project context

Setting: IIM Bangalore staff canteen (≈400 diners/day).
Approach: Dr. Soni and a crew actively work through the live case; you are invited to think along even though the project is conducted on campus.
Your role: As the module unfolds, identify problems, empathise with both service providers (canteen staff) and consumers (diners), propose solutions, and eventually test them in the real setting.

How the stages connect

flowchart LR
    A[Inspire] --> B[Empathise]
    B --> C[Define]
    C --> D[Ideate (next module)]

The output of Define becomes the input for the next module (ideation – not covered here).

Key takeaways

The Inspire stage shifts focus from “what to design” to why design at all.
Empathise means stepping into the user’s shoes – not with preconceived answers, but with genuine curiosity.
Define is a filtering step: among all the needs and pain points uncovered, select the one that is most worth solving.
This module’s live project (staff canteen) provides a concrete, testable setting to apply the three stages.
You are expected to engage virtually – think along as the case progresses.

Mind of a Design Thinker

A design thinker operates at three levels: tool sets, skill sets, and mindset. Tools are the raw materials and instruments (brushes, knives, software). Skills are the ability to use those tools effectively (a trained chef vs. a novice with the same knife). The mindset is the “glue” that holds them together — the internal stance that determines how tools and skills are applied. Without the right mindset, even the best tools and skills produce mediocre results.

Layer	What it is	Example
Tool sets	Physical or digital instruments	Paint, canvas, knife, software
Skill sets	Proficiency in using tools	Painting technique, knife handling
Mindset	Internal attitude and worldview	Willingness to experiment, empathy, resilience

The mindset is the hardest to develop, yet it makes the decisive difference between a competent practitioner and a great one.

Why mindset matters: the Picasso example

Pablo Picasso produced over 15,000 artworks in his lifetime (roughly one per day as an adult). What set him apart was not just skill — it was his mindset of constant reinvention. Whenever his style became saturated, he reinvented himself. He invented collage by asking: “Why must art use canvas and paint? Why not everyday objects, even garbage?” That act of questioning assumptions, ignoring audience expectations, and redefining the medium is the essence of a design‑thinker’s mindset.

The three facets of a design‑thinker’s mindset

The mindset of a design thinker can be captured by a Venn diagram of three overlapping attributes: clear head, deep heart, and thick skin.

flowchart TD
    A[Clear Head] -->|Know your priorities| B(Design Thinker's Mindset)
    C[Deep Heart] -->|Empathy & compassion| B
    D[Thick Skin] -->|Resilience to criticism| B

Clear head

“Temporary clarity is better than permanent blindness.”

Having a clear head means knowing your priorities at any stage of life. Priorities change, but confusion about them is toxic. Example from practice: clients who ask “Teach me design thinking” have no clear purpose; those who say “Here is a problem — solve it using design thinking” have a clear objective and learn far more effectively. In an age of social‑media noise and constant comparison, clarity of purpose is a prerequisite.

Deep heart

Deep heart is compassion – the ability to understand others’ pain, aspirations, and desires without them having to explain fully. This is empathy, not sympathy.

Empathy ≠ being emotional. Empathy = being considerate and proactive. If someone asks you for food and you give it, that’s sympathy, not empathy. Empathy senses the need before it is spoken.

In collectivist, high‑population contexts (like India), compassion often gives way to self‑serving competitiveness. A design thinker must deliberately cultivate empathy.

Thick skin

Thick skin is the courage to act without being paralysed by others’ opinions. Many people have great intent but are timid – overly concerned with approval from strangers. As long as you are not deliberately hurting anyone, being yourself is more important than pleasing others.

The opposite of being yourself is not hurting others; the opposite of being yourself is not being yourself.

In a collectivist culture that prizes agreement and external approval, thick skin is especially hard to maintain, yet it is essential for moving away from the status quo.

Reconciling deep heart and thick skin

These appear contradictory: deep heart means caring about others’ feelings; thick skin means not caring about others’ judgements of you. The resolution: you can be empathic about others’ needs while being unconcerned about their approval of your actions. One is outward focus, the other is inward resilience.

Exam tip: The reconciliation of “deep heart” and “thick skin” is a frequently tested concept. Understand the distinction: deep heart = care about others; thick skin = don’t care about their opinion of you.

Key takeaways

Design thinking requires tool sets + skill sets + mindset; mindset is the hardest and most critical.
A design thinker’s mindset has three overlapping parts: clear head, deep heart, thick skin.
Clear head: know your priorities (purpose-driven learning).
Deep heart: empathy, not sympathy; proactively sense unspoken needs.
Thick skin: resilience to criticism; do not seek approval from others.
Deep heart and thick skin are reconcilable: one cares about others’ needs, the other disregards others’ judgement of oneself.

Honing a Clear Mind

Honing a clear mind means deliberately focusing your mental energy on what you can actually affect, while letting go of everything else. The core idea: your attention and time are finite – every concern outside your control steals resources from the things you could change. This is a prerequisite for the Inspire phase of Design Thinking: clarifying why you need to solve a problem.

The Two Zones

Every person has two mental territories:

Zone	Description	Size
Zone of concern	Everything that bothers you: your car, the Ukraine war, an asteroid, workplace gossip. Expands as far as you let it.	Potentially vast
Zone of influence	All the things you can actually do something about – act on directly.	Always small

Key insight: The zone of influence is always a tiny subset of the zone of concern. The goal is to shrink the zone of concern and expand the zone of influence until they overlap – that is the zen state (a state of flow).

Why your thoughts are unlimited – but your senses aren’t

The five senses have finite ranges: smell ~5 ft, sight ~1–2 km, hearing ~50 m, taste and touch only within reach. Only thoughts are unbounded – you can imagine a solar eruption or the Big Bang in less than a second. This is why the zone of concern can balloon uncontrollably: thinking is effortless and limitless. You must consciously bound it.

Shrinking the Zone of Concern: Saying No

Use the word no – a high-quality no (said without regret). Be selective about:

People, activities, books, entertainment, food, places, sources of news
Projects you take on (only say yes when you can do it better than anyone else)

Example: The lecturer declines teaching marketing or HR – that is a clear, regret-free no.

Expanding the Zone of Influence: Saying Yes

Within the boundaries you’ve set, say yes to actions you can influence. Expand influence by taking responsibility for what you can change. The one person you can truly change is yourself; everything else – parents, friends, spouse, children – you can only create conditions for change.

The Zen State (Flow)

When zone of concern === zone of influence (complete overlap), you achieve a state of flow. You are concerned only about the ball coming at you – like Roger Federer at Wimbledon: no thoughts of score, legacy, past, or future.

The ITC Model – What to Do When Distractions Arise

Use this three-tier framework to decide how to react:

flowchart TD
    A[Something happens that bothers you] --> B{Is there any upside beyond ego?}
    B -->|No upside| C[Ignore 50%]
    B -->|Upside for self-development| D[Tolerate 40%]
    B -->|Very high upside that justifies cost| E[Confront 10%?]
    C --> F[Let it pass like x-rays]
    D --> G[Absorb feedback / difficult situations]
    E --> H[Need courage; fight to the end]

I – Ignore (~50% of events)

Let it pass completely; no emotional absorption.
Example: A car brushes yours on the road – not worth the fight (minor miracle you survived traffic).
Don’t ignore people – ignore their behavior. Behavior is largely shaped by environment (e.g., people clean in Delhi Metro but litter outside; same person, different context).

T – Tolerate (~40% of events)

Absorb the situation because there is an upside for self-development.
Example: A PhD supervisor asking to delete a six-month chapter – painful but necessary for improvement.
Always keep the feedback channel open – never kill the messenger for the message. Even inaccurate feedback trains the channel to deliver valuable information later.

C – Confront (only when necessary)

Confront only when the upside is very high and you are willing to pay the cost in time, energy, or reputation.
Example: Witnessing cheating in an exam or facing abuse – these require courage and commitment to see the battle through.
Do not confront trivial matters with low upside (auto driver). In the age of social media, “mind your business” is often the smartest strategy.

Exam tip: The ITC model is a decision hierarchy – you try I first, then T, then C. The percentages (~50%, 40%, remainder) emphasise that most daily irritants should be ignored or tolerated, not confronted.

Connecting to Design Thinking’s “Inspire” Phase

The Inspire phase asks: Why do I need to solve this problem? – not Can I solve it?
A clear mind (small zone of concern, large zone of influence) allows you to focus energy on problems that truly matter and that you can affect. Saying no to irrelevant concerns and yes to meaningful influence is the foundation.

Key takeaways

The zone of concern is large; the zone of influence is small. Shrink the first, expand the second.
Zen state = the two zones overlap – complete focus on what you can act on.
Use no to reduce concern, yes to expand influence; a high-quality no is said without regret.
ITC model: Ignore 50% (let pass), Tolerate 40% (absorb for growth), Confront only when upside justifies the cost.
Never ignore people – ignore their behavior; behavior is environment-driven.
A clear mind is essential for the Inspire phase – it clarifies why you are solving a problem.

Inspire – The "Why" of a Problem

The Inspire stage reframes the first step of design thinking. Before empathising with users or generating solutions, you must step back and ask: Why solve this problem at all? The trap is assuming every incoming problem is important. Two questions exist for any problem:

Why solve it? (more vital)
How to solve it? (easier, delegable)

Most people – conditioned not to question authority – jump straight to how. This leads to solving the wrong problem or missing a deeper opportunity.

The "Why" Question – a Worked Example

Customer asks	"I want a hole in the wall"
Typical reaction	"They need a drill (maybe a pink one for a lady)."
Asking why	"Why do you want a hole?"
Chain of reasons	To hang a painting → to make walls beautiful → to make house beautiful.
Redefined problem	How to make the house look beautiful (without drilling a hole).

Another example: stamping boarding passes at airports. The stated problem is "how to stamp efficiently". Asking why reveals the real need: authentication. Physical stamping is messy, ink-heavy, and risky (lost pass → restart). Solution: virtual authentication. Today many airports have eliminated physical stamps, and even visas and passports are moving to biometric/virtual formats.

Exam tip: The "why" chain (5 Whys) is a standard tool to reach root causes. In exams, illustrate with a concrete chain – e.g., hole → painting → beauty – to show how the problem shifts.

Why This Matters More in the Age of AI

AI excels at answering how (e.g., "you're hungry → here are five restaurants"). It is a good slave but a bad master – it does not ask why. To lead a fruitful life, humans must focus on the why question; otherwise technology uses us.

Industry Examples – Redefining the Problem

Asian Paints (exterior paint longevity): The stated problem: "How to make paint last 15 years?" (chemical processing, layers, weather protection). Asking why reveals that a 15-year lifespan hurts business – customers would repaint less often. The real problem: "How to make paint look fresh for 5 years?" (controlled deterioration). This redefined the R&D direction.
Royal Enfield (women riders): The stated problem: "How to make women riders more comfortable?" (lower seat, lighter weight, less vibration). Asking why reveals that women who choose a Royal Enfield want the bike as it is – they are making a statement. The solution: leave the bike unchanged and let riders graduate to it.

The Three Types of Problem Solvers

The transcript categorises professionals by how deeply they engage with a problem. This is a key framework for understanding the Inspire stage – it shows why why matters.

Type	Approach	Number of problems/day	Relationship with client	Risk
Pharmacist	Treats problem as a transaction. Hands out the requested "medicine" without questioning.	~100	None – easily replaced (e.g., online pharmacies, AI)	Commodity; perfect substitute
Doctor	Distinguishes symptom from root cause. Prescribes treatment, follows up.	~20	Relationship – cares about outcome	Harder to replace
Surgeon	Highest knowledge asymmetry. Client surrenders. Works on the most complex, critical problems.	~5	Complete trust; client does not negotiate	Irreplaceable; premium respected

Key insight: Asking why moves you from pharmacist (how) toward surgeon (why). The more you elevate the problem, the more indispensable and valued you become.

A Hierarchy of Problem-Solving Mindset

flowchart TD
    A["Problem arises"] --> B{"Which question first?"}
    B -->|"How?"| C["Pharmacist: immediate solution, no depth\nEasily replaced by AI"]
    B -->|"Why?"| D["Doctor: symptoms → root cause\nCreates relationship"]
    D --> E["Surgeon: redefines problem at highest level\nHighest value"]
    E --> F["Solution addresses the real need\nOften non-obvious & elegant"]

The core message of the Inspire stage: Before climbing the ladder, make sure it is leaning against the right wall (Stephen Covey). Solving a problem well is useless if the problem itself is not worth solving.

Key takeaways

Inspire is the first design thinking stage – ask why before you empathise or ideate.
The "why" question redefines the problem (e.g., hole → beautiful house; stamping → authentication).
Three types of problem solvers: Pharmacist (transactional), Doctor (relationship), Surgeon (high knowledge asymmetry). Aim to be a surgeon.
AI is good at how, not why – humans must retain the why-question to stay indispensable.
Industry examples (Asian Paints, Royal Enfield, boarding passes) show that redefining the problem can lead to radically different (and better) solutions.

The High Threshold for Design Thinking

The bigger tragedy in design thinking is not failing — it is pursuing a problem that was not worth it. Design thinking should only be applied to audacious goals (e.g., putting a man on the moon), not to everyday, routine problems (e.g., crossing the street). The latter should be tackled with lean thinking, not design thinking. The audacity and grandness of the goal is the qualifying condition.

Exam tip: Never default to design thinking for every problem. Ask: is this problem truly complex and worth the effort? If not, use simpler methods (e.g., lean, agile, or just ignore it).

Bruises vs. Cancer: Two Problem Categories

All problems can be classified into two types based on how they behave with time:

Category	Behaviour with time	Example	Appropriate response
Bruise	Heals by itself or becomes irrelevant	A small cut while cutting vegetables; a pimple on a teen’s face	Leave it alone. Time heals it.
Cancer	Aggravates, spreads, and becomes sinister	Habit of watching Instagram reels before bed (→ sleep loss → work suffers → relationships suffer)	Act immediately. Do not ignore.

Key insight: 80% of problems in life are bruises; only 20% are cancerous. Yet most people waste energy “fixing” bruises — often making them worse.

Exam tip: A bruise problem becomes worse when you try to solve it (e.g., picking a pimple). Learning to ignore is a critical skill.

How to Diagnose: Create Distance

To distinguish a bruise from cancer, create space between you and the problem:

Physical distance — step back, change your environment.
Temporal distance — give it time; “time is a great healer.”
Emotional distance — detach yourself; your personal investment inflates the problem’s importance.

Value is not intrinsic. A Coldplay concert ticket worth ₹3 lakh to one person is irrelevant to millions. A child values a pencil like a treasure; the market values it near zero. Similarly, problems only appear big because of the value you associate with them. Objectivity comes from distance.

Exam tip: The COVID‑19 pandemic initially seemed like cancer — but with time, it healed into a bruise. Many problems, when viewed from a distance, shrink.

Thinking Above Your Pay Grade

Work at your pay grade, but think two levels above your pay grade. When faced with a problem, ask yourself: How would my boss’s boss view this? Would they bother with it, or dismiss it as trivial?

If the boss’s boss would not care, you have three options:

Make them care — frame the problem as more impactful.
Sell the problem — pivot to a more worthy one.
Pivot — drop the problem entirely.

Why this matters: People often solve problems just to justify their salary, even when the problem is not worth solving. Instead, be a man/woman of contemplation first, then a person of action.

Quick Fix vs. Permanent Fix (Perma Fix)

Using the doctor‑patient analogy:

Symptom – e.g., headache, fever (what the patient reports).
Problem – e.g., viral infection (the diagnosis).
Root cause – e.g., weakened immunity, exposure (underlying factor).

A quick fix (band‑aid, jugaad) jumps straight from symptom to solution. It is temporary and often necessary for immediate relief.
A permanent fix (perma fix) goes symptom → problem → root cause → solution. It addresses the underlying cause to prevent recurrence.

Design thinking is a perma fix — it solves complex, high‑impact, high‑frequency problems by deeply understanding the user and the root cause.

flowchart LR
    S[Symptom] -->|Quick fix| Sol1[Solution]
    S -->|Diagnose| P[Problem] --> RC[Root Cause] -->|Perma fix| Sol2[Solution]

When to use design thinking:

The problem has high frequency (repeats) AND high impact (cancerous, complex).
If low frequency or low impact → not worth design thinking.

Key takeaways

Only apply design thinking to audacious, complex problems (cancer), not to bruises (80% of daily problems).
Bruises heal with time; cancers worsen if ignored – learn to distinguish using distance (physical, temporal, emotional).
Think two levels above your pay grade to avoid wasting energy on trivial problems.
Design thinking is a permanent fix – it goes from symptom to root cause, not a quick fix.
No problem has intrinsic value; it is only as big as you make it.

Design Brief

A design brief is a concise statement of intent that sets the direction for the design‑thinking process. It is the starting point for the Inspire stage: it must inspire both yourself and your team to tackle a specific problem. A well‑crafted design brief acts as a sandbox – clear boundaries on the outside, creative freedom on the inside.

Definition
A design brief is a brief statement of intent as to why we are interested in going about this particular problem.

Three Conditions of a Good Design Brief

Condition	What it means	Why it matters
Inspirational (stretch target)	The goal must be ambitious, not linear. It should require creative effort to reach.	Without a stretch, people stay in “productivity” mode and never explore new ideas. E.g., hopping 3 ft is easy; hopping 15 ft forces you to be creative.
Constrained	Clear boundaries – budget, time, materials, etc. – are explicitly stated.	Constraints push you toward innovative solutions. No constraint → no creativity. E.g., Apollo 11 lunar module had to be light enough to take off but carry enough fuel to land – a constraint that drove breakthrough engineering.
Vague	The brief must be vague enough (≈10 000 ft) – not too detailed, not too broad.	Vagueness leaves multiple paths open. Over‑specifying a solution (e.g., “look at compensation”) kills creativity.

Worked example: Employee retention briefs

Brief	Text	Assessment
A	How might we improve employee retention from 80% to 99%?	Stretch ✅, no constraint ❌
B	How might we improve employee retention from 80% to 99% without increasing cost of operations by more than 5%?	Stretch ✅, constraint ✅, vague ✅
C	How might we improve employee retention from 80% to 99% without increasing cost of operations by more than 5% by looking at compensation?	Too directed (not vague) ❌

B is the best brief – it stretches, constrains, and leaves room for multiple approaches.

The Sandbox Metaphor

A design brief is like a children’s sandbox:

The walls are the constraints (clear, non‑negotiable boundaries).
Inside the sand is malleable – you can shape, build, and play freely.
Outside the box there is no playfulness.

Thus the brief must define the conditions of operation (the box), but within those conditions everything is open to exploration.

Powerful Examples from Practice

John F. Kennedy’s Moon Speech (1962)

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

Inspirational: Putting a man on the moon was a staggering stretch (NASA had no idea how in 1962).
Constrained: “Bring him back safely” + “by the end of this decade.”
Vague: No mention of how (private vs. government, collaboration, etc.). This galvanised millions worldwide.

Aravind Eye Hospital (Madurai)

Vision statement: “Eradicate needless blindness” (three words).

Inspirational: Eradicate – not just reduce.
Constrained: Needless – excludes blindness that is natural or incurable; focuses on preventable/curable cases.
Vague: Does not specify methods, technology, or funding.

Tata Indica (India’s first indigenous car)

Ratan Tata’s brief:

“Design an Indian car from scratch with the internal volume of an Ambassador, the size of a Maruti Zen, the ease of entering/exiting (especially rear seat), priced close to a Maruti 800, adding the economy of diesel, all in a contemporary design.”

Stretch: “Design from scratch” – never done before in India.
Constraints: Exact size, price, fuel type, interior space, design style.
Vague: How to achieve all of that simultaneously was left to the engineers.

Other notable metaphors-as-briefs

Google: “Make the web as accessible as flipping through a magazine” – intuitive, fast, one‑thumb navigation.
Mahindra XUV500: “Cheetah” – grille = jaws, door handles = paws, monocoque stance = cheetah stance.
Royal Enfield Himalayan: A complete ground‑up redesign for off‑roading.

Why a Well‑Defined Brief Is Critical

A poorly defined problem cannot be solved because team members have different assumptions.
One of the biggest reasons design‑thinking programs fail is rushing through the definition stage.
The brief should outlive the project – it becomes the north star for all decisions.
The leader’s job is to spend substantial time crafting a clever, well‑drafted brief. Aim for 10 000‑ft altitude – not 30 000 (too vague) nor 20 ft (too detailed).

Exam tip: When evaluating a design brief, always check whether it is inspirational, constrained, and vague. A brief that is too specific (like “by looking at compensation”) kills creative thinking.

Key takeaways

A good design brief has three attributes: stretch, constraint, vagueness.
Constraints drive creativity; no constraints → linear thinking.
Vagueness enables multiple solutions; over‑specification kills possibility.
The sandbox metaphor: rigid boundaries, limitless play inside.
Examples: Kennedy moon mission, Aravind Hospital, Tata Indica, Google, Mahindra XUV500, Royal Enfield Himalayan.
Invest time in defining the problem – poor definition is the #1 cause of design‑thinking failure.

Empathy: Listening and Understanding

Empathy is often defined as "stepping into someone’s shoes." In design thinking, it goes deeper: the ability to listen, feel, and act on another’s perspective. A common trap is to confuse empathy with merely anticipating others’ problems.

Why Listening Beats Giving Answers: The Doctor Example

Doctor A	Doctor B
Rushes, writes prescription without eye contact	Stops writing, maintains eye contact, probes
Gives medicine (common flu) without explaining	Explains the cause, suggests home remedies, no medicine
Patient recovers but feels dismissed	Patient recovers and feels heard

Both doctors cured the patient, but Doctor B earns trust—because he listened. As Oprah Winfrey concluded after 30,000 interviews: “Everybody wants to be understood.” People do not need answers; they need to be heard.

Empathy vs. Expertise

Expertise often comes at the cost of empathy, and empathy at the cost of expertise.
An expert who already knows the answer before you finish asking makes you feel contained, not connected.

True expertise includes the skill of listening. Empathy is not a weakness—it is a competitive advantage. In an age of automation, empathy and creativity are the two abilities machines cannot replace.

Empathy Is Universal Yet Unpractised

Humans are empathetic as a species, but individuals may not be—either because they undervalue it or because they are too absorbed in their own emotional state (especially self-pity, the “why me?” trap).

Courage is not the absence of fear; it is the acknowledgement of fear.
→ Acknowledge your own emotions before you can empathise with others.

Key Takeaways

Empathy is about listening and understanding, not just giving solutions.
Doctor B’s approach (listening + explaining) outperforms Doctor A’s (rushing + prescribing).
Empathy and expertise need to be balanced; listening is itself an expert skill.
Self-pity (“why me?”) blocks empathy; acknowledge emotions to move forward.
After automation, empathy + creativity will distinguish humans from machines.

Daniel Goleman’s Four Levels of Emotional Intelligence

Daniel Goleman’s model of emotional intelligence (EQ) provides a structured path to empathy. The four levels build on each other:

flowchart LR
    A[Self-Awareness] --> B[Self-Management]
    B --> C[Empathy]
    C --> D[Social Skills]

1. Self-Awareness

Recognising your own emotional state—anger, sadness, anxiety, elation—without judgment. The ability to step back and observe “I am angry” rather than being consumed by the anger.

2. Self-Management

Once aware, managing that emotion. Techniques: deep breathing, meditation, taking a break, accepting a loss (e.g., missing a flight → stop amplifying stress → find next options).

3. Empathy

Understanding others’ emotional states. Only after handling your own emotions do you have the mental bandwidth to truly hear someone else.

4. Social Skills

Tailoring your behaviour to others’ emotional states. Example: a teacher explaining the same concept to a 5th grader, a college student, and a senior executive must adapt each time.

IQ gets you into the game; EQ helps you win.

Key Takeaways

EQ hierarchy: self-awareness → self-management → empathy → social skills.
Self-awareness is the base—you cannot manage or empathise without it.
Self-management prevents emotional hijacking (e.g., traffic rage → acceptance).
Social skills are the applied layer: adapting communication to the audience.
EQ often matters more than IQ for long-term success in relationships and leadership.

Three Levels of Empathy

Daniel Goleman distinguishes three progressive levels of empathy, each deeper than the last:

Level	Name	Description	Example
1	Cognitive empathy	Understand the other’s perspective intellectually.	Call centre agent grasps your problem
2	Emotional empathy	Feel the other’s emotion; share the pain.	Friend touches your hand, tears in her eyes
3	Empathic concern	Act on that understanding and feeling to help.	Counsellor listens, feels, then suggests a solution

Why the Highest Level Matters

Without empathic concern, empathy can become fake—endless “I understand” but no action. The other person eventually distrusts you. As a leader, parent, or service provider, you have power to effect change; mere cognitive or emotional empathy is insufficient.

Example – Amazon Prime cancellation: A customer cancelled a recently renewed subscription. Amazon refunded the pro-rated amount without obstruction. They listened, understood (cognitive), felt the user’s inconvenience (emotional), and took immediate action (empathic concern). This is rare and builds deep trust.

Key Takeaways

Cognitive empathy = intellectual understanding; emotional empathy = feeling with the person.
Empathic concern is the highest form: understanding + feeling + doing something to fix it.
Without action, empathy feels hollow and damages trust.
Leaders must practice empathic concern because their position gives them power to improve situations.
Empathic concern prevents empathy fatigue—acting is better than just feeling overwhelmed.

Listening Positions

Listening is the most underrated yet critical skill for empathy. Stephen Covey observed that most people listen with the intent to reply, not to understand — always waiting to put their own words in. Listening positions, introduced by Julian Treasure, are conscious choices about how we listen. Knowing them lets you adapt your style to the situation.

Bill Clinton exemplifies reverse charisma: when you listen intently, the other person feels charismatic and important. The spotlight stays on them.

Active vs. Passive Listening

Active listening: You drive the conversation — probing, asking questions, steering.
Passive listening: You listen intently without interrupting; you let the flow happen.

Situation	Recommended style	Why
Child talking about school	Passive	Child wants to vent uninterrupted.
Exit interview (initial phase)	Passive	Let the person open up; real reasons often emerge later.
Doctor (diagnosis phase)	Passive → then Active	First listen freely, then probe with questions.

Reductive vs. Expansive Listening

Reductive listening: You try to conclude and summarise — “So therefore…”. Premature reduction causes tunnel vision.
Expansive listening: You ask “What else?”, “Can you tell me more?” — you expand possibilities.

Situation	Recommended style	Why
Counsellor (first half)	Expansive + Passive	Explore the person’s story fully.
Counsellor (final phase)	Reductive	Summarise and validate understanding.
Lawyer cross-examining	Expansive (active)	Draw out details.
Judge summing up	Reductive (passive)	Condense the case.

Critical vs. Empathetic Listening

Critical listening: Check for logical consistency, contradictions, coherence.
Empathetic listening: Accept what is said without judging coherence; the goal is to let the other person vent.

Situation	Recommended style	Why
Police interview	Critical	Detect lies, contradictions.
Conversation with an aging parent	Empathetic	Being critical damages the relationship; the objective is connection, not logic.
Learning from this lecture	Active + Expansive + Empathetic	Challenge your own biases; don’t just confirm what you already believe.

Exam tip: A common mistake is using critical listening when empathy is needed (e.g., with family). Always match the position to the relationship and goal.

Key takeaways

Listening is not passive; you can consciously choose active/passive, reductive/expansive, critical/empathetic.
Passive listening = not interrupting; active = driving the conversation.
Reductive closes down; expansive opens up. Both are needed, but timing matters.
Critical is for logic; empathetic is for emotional connection.
Great listeners (like Bill Clinton) use reverse charisma — they make others feel valued.

The RASA Technique

RASA is a four-step listening method from Julian Treasure that builds trust and uncovers real needs.

Step	Meaning	Example
Receive	Be a good receiver: maintain eye contact, suspend judgment, let the person finish.	Don’t interrupt; don’t one-up their story.
Appreciate	Acknowledge the act of speaking, not necessarily the content.	“That’s a great insight, thank you for sharing.”
Summarise	Parrot back what you heard to confirm understanding.	“So you’re saying that A, B, and C are the reasons – am I right?”
Ask	Ask questions that invite openness, not defensiveness.	“What happened?” (vs. “Why are you late?”)

Why RASA Matters

Receive: Insecurity kills receiving. If you always try to one-up (“Even I had that…”), you close the other person down.
Appreciate: The person feels acknowledged and safe to go deeper. Customers initially talk about symptoms; appreciation builds trust to reveal real problems.
Summarise: Builds rapport, plugs information gaps, and corrects misunderstandings.
Ask: A question can be an act of empathy. Compare “Why are you late?” (defensive) vs. “What happened?” (we’re on the same side).

Exam tip: The most common market‑research failure is that customers role‑play — they tell you what you want to hear. RASA helps you get past the symptoms to the real need.

Key takeaways

RASA = Receive, Appreciate, Summarise, Ask — in that order.
Appreciation is about the act, not the content; it opens vulnerability.
Summarising is not just repetition — it confirms and corrects.
The right question (“What happened?” vs. “Why?”) turns defensiveness into dialogue.
RASA, combined with awareness of listening positions, makes you a listener others seek out.

2.3 Three Practical Tips for Cultivating Empathy

Empathy in design thinking is not a passive feeling — it is an active practice. Three concrete habits separate a genuinely empathic designer from someone who merely assumes they understand users. These tips apply directly to observing real environments (e.g., the IIMB staff canteen project) and to engaging with people without bias.

2.3.1 Listen with Intent

Intuition: Most people listen only to reply. Empathic listening listens to understand — not to judge, not to interrupt, and not to prepare a counter-argument. Listening with intent means giving full attention to what is said and why it matters to the speaker.

Do not multitask while listening.
Let the speaker finish before formulating your response.
Seek the meaning behind the words — emotions, needs, unspoken concerns.

Exam tip: This is the first and most fundamental tip. It is often tested as "active listening" in the context of user interviews.

2.3.2 Observe with Purpose

Intuition: Casual observation misses the subtle inefficiencies, frictions, and delights that a trained eye catches. Observing with purpose means watching with a clear goal: identify what could be improved (and also what works well). As a newcomer to a space (like watching a video of the canteen), you will notice things regular users take for granted.

Ask while observing: What is wrong? What is fascinating? What can be improved? What good practice should we embrace?
The first viewing of raw footage is especially powerful — patterns jump out before you become desensitised.

2.3.3 Defer Your Judgment

Intuition: Judging people (or their behaviour) consumes mental energy and distorts your perception. Deferring judgment does not mean ignoring behaviour — it means separating a person’s action in a specific moment from their identity as a whole. Behaviour is highly contingent on the environment, not a permanent label.

Why it matters for empathy:

A user who seems rude or uninterested may be under stress (e.g., a medical emergency).
If you judge the person, you close the door to understanding their true needs.
If you evaluate only the behaviour in context, you remain open and learn more.

Key distinction:

Judging a person ≠ evaluating performance in a specific task.
In a course: evaluate an assignment, not the student's character. In design: evaluate an observed behaviour, not the person's worth.

Exam tip: The professor’s story about the executive who refused to close his laptop illustrates the danger of snap judgment. The student had a legitimate medical urgency. If judged, the relationship would have been lost. The correct response: separate the behaviour from the person.

Example: The transformation of Angulimala Angulimala, a feared robber who wore a garland of fingers, met Gautama Buddha without fear. Buddha did not judge him; he simply understood. That moment transformed Angulimala into a saint. The lesson: anyone can change at any moment — judgment is a fruitless exercise.

Carrying the weight of judgment: Judging others (e.g., comparing courses or faculty) wastes mental capacity. You can always give feedback later; during the learning process, stay open and non-judgmental. This makes you lighter, clearer, and a far better thinker.

flowchart LR
    A[Empathic mindset] --> B[Listen with intent]
    A --> C[Observe with purpose]
    A --> D[Defer judgment]
    B --> E[Understand speakers]
    C --> F[Spot improvement opportunities]
    D --> G[Keep mind open to learning]

Key takeaways

The three practical tips: listen with intent, observe with purpose, defer judgment.
Deferring judgment means evaluating behaviour in context, not labelling the person.
Judgment is a mental burden that blocks understanding; empathy requires a clear, open mind.
Use these tips during the canteen observation project to uncover deep user needs.

Empathy Can Be Engineered

Empathy is not an art you either have or lack — it is a science that can be created, designed, measured, and manipulated. You can develop it at any age. A powerful example: parents become empathetic almost overnight when they hold their newborn, forced to communicate without shared language. This shows everyone has a reserve of empathy that can be called upon. The goal is to use it more maturely, assertively, and regularly.

Exam tip: The “engineerability” of empathy is a foundational claim — expect a question contrasting “empathy as art” vs. “empathy as science”.

Tool 1: Job to Be Done (JTBD)

Clayton Christensen of Harvard Business School introduced the Job to Be Done framework. The core insight: customers do not buy products; they hire products to get a job done. A car is not a product — it is a service that gets the job of transportation from A to B in comfort. A drilling machine is not a product — it is hired to make a hole.

Crucially, you can define the same job narrowly or broadly:

Narrow: “make a ¼‑inch hole”
Broad: “beautify a home”

The broader definition opens up more product and service possibilities. When empathising, always step back to identify the bigger job the customer is trying to accomplish.

Functional vs. Emotional Job

Every job has two components:

Component	What it is	Example (wristwatch)
Functional	The practical task	Telling time
Emotional	The feeling or identity	Adornment, status, aesthetic value

Titan succeeded not just by making accurate watches, but by crafting emotional value — a watch as an adornment on your wrist.

Worked Example: Bisleri

Level	Question	Answer
Need	What do customers need?	Pure water when thirsty
Want	What do they want?	Cold, pure water at a certain temperature
Desire	What do they really desire?	Water instantly available, with no cost burden and no environmental harm (plastic waste)

Bisleri observed the plastic waste problem from single‑use bottles in hotels. By reframing its job from “supply water” to “quench thirst without plastic waste”, it introduced refillable glass bottles and on‑site filling machines — a new service line.

Exam tip: JTBD questions often ask you to differentiate between need, want, and desire. The broader framing unlocks innovation.

Key takeaways – JTBD

Customers hire products to get a job done.
Job can be defined narrowly or broadly; broader definitions open more opportunities.
Every job has a functional and an emotional component — both must be understood.
Move from need → want → desire to uncover the real job.

Identifying the Customer: A Concert of Stakeholders

In practice, there is never one customer. Multiple stakeholders form a concert of customers, each with different jobs to be done.

Example: Baby food (Cerelac)

Stakeholder	Job (what they want)
Baby	Nutrition, taste
Mother	Nutrition
Father	Economy
Grandmother	Tradition
Maid	Convenience
Stockist / pharmacist	Better inventory turnover and margin
Doctor	Prescription value, safety

When applying JTBD, analyse the needs of all stakeholders, not just the end‑user. This becomes the basis for a stakeholder map.

Key takeaways – Multiple customers

The “customer” is never a single person — it is a set of stakeholders.
Each stakeholder has a unique functional and emotional job.
Empathy requires understanding the whole constellation.

Tool 2: Problem Exploration Map

Every problem is actually a symptom of deeper causes. A problem exploration map (a type of mind map) helps you move from the symptom to root causes — the critical lever for permanent (perma‑fix) rather than temporary (quick‑fix) solutions.

Process:

flowchart TD
    A[Symptom] --> B[Problem 1]
    A --> C[Problem 2]
    A --> D[Problem 3]
    B --> E[Root cause 1.1]
    B --> F[Root cause 1.2]
    C --> G[Root cause 2.1]
    D --> H[Root cause 3.1]
    D --> I[Root cause 3.2]

Example: Traffic jam

Treating it as a problem → widen roads, restrict traffic (quick fix).
Treating it as a symptom → investigate root causes (e.g., poor public transport, urban density, work hours) and solve permanently.

Worked Example: Decline in book reading

Symptom	Book‑reading habit is declining
Problems (causes)	— Other sources of education<br>— Lack of attention span<br>— Books don’t give immediate gratification<br>— Difficulty choosing which book to read<br>— Lack of access in local language
Root causes (for “difficulty choosing”)	— No legitimate information on good books<br>— Don’t know where to find reviews<br>— Don’t know which reviews to trust<br>— Hardbound copies are costly<br>— Shipping charges and time<br>— Low resale value

By drilling down to a root cause such as “do not know which book to read”, you can generate a business idea: a service recommending top‑10 books by age and profession. The idea emerged only after breaking the symptom into its constituent causes.

Exam tip: In a design thinking project, your problem exploration map is a key deliverable. Every cause must be genuinely a cause, not a restated symptom.

Key takeaways – Problem Exploration Map

Start by reframing the problem as a symptom.
Decompose the symptom into multiple causes (problems).
For each cause, drill down to root causes — the level where a solution can be permanently effective.
Avoid jumping to solutions before reaching root causes.

Stakeholder Map

A stakeholder is any person or group who is concerned with the problem or with the solution. Many stakeholders are invisible – they include not only direct users but also support teams, managers, regulators, and even people who benefit from the problem remaining unsolved. The stakeholder map reveals the full set of actors and surfaces conflicting demands.

How to build a stakeholder map

Place the core symptom at the centre of a mind map.
Identify 7–9 stakeholders – too few risks bundling distinct perspectives; too many creates confusion.
For each stakeholder, document:
- Positive – benefits they get from the current situation (or from the proposed change).
- Negative – losses, risks, or discomfort they anticipate.

Surprise: Some stakeholders enjoy the problem. Their positive may be another stakeholder’s negative.

Example: Shop floor automation

Problem statement: “How do we transition to a robotic shop floor?”

Stakeholder	Positive (benefit)	Negative (detractor)
Worker	Less physical effort	Loss of job
Supervisor	Greater productivity	Must retrain to manage robots
IT / Tech team	More recognition, involvement	Risk of failure; must learn new tech
Finance	Converts labour cost to tech cost	Heavy capital investment
Labour union	No benefit	Loss of employment for members

Conflict: Supervisor’s gain in productivity is the labour union’s loss (fewer workers needed).

Why it matters

A stakeholder map lets you anticipate friction before rolling out an idea. By understanding motivations and detractors, you can adapt the idea to create a win‑win. The idea is never static – it evolves as you address each stakeholder’s concerns.

Exam tip: An idea wins only when others see value in it. Stakeholder maps force you to ask “what’s in it for them?” – without that, even the best‑laid plans fail.

Key takeaways

A stakeholder is anyone affected by the problem or solution; many are hidden.
Use a mind map with 7–9 stakeholders; for each list positive and negative.
Conflicting demands (one’s gain is another’s loss) are common and must be managed.
The map helps anticipate implementation problems and evolve the idea iteratively.

Customer Journey Map

A customer journey map examines a problem through time. It is useful when the experience unfolds over multiple stages (e.g., travel, purchasing, onboarding). Its goal: identify pain points and opportunities at each step, then redesign or eliminate stages.

How to build a journey map

List the stages in chronological order – from before to after the core experience.
At each stage, record current or potential issues (frictions, delays, confusion).
Optionally, propose solutions or question whether the stage is needed at all.

Example: Airport journey (Bangalore → destination)

Stage	Potential issues
Enter airport, use Digi Yatra	–
Security: put luggage on conveyor	Forgetting to remove laptop/cables; prohibited items (e.g., coconut)
2D scanner checks cabin luggage	Coconut flagged as fire hazard – must be abandoned; causes delay and frustration
Collect luggage, head to boarding gate	–
Board: scan pass, aero bridge, seat	–

Insight: The coconut problem wastes CISF time and upsets passengers (religious value). A 3D scanner that scans from the side would eliminate the need to remove laptops and cables – saving time and inconvenience for both staff and travellers.

When to use which tool

Technique	Best for
Problem exploration map	Problems with multiple root causes (e.g., mobile addiction in children)
Stakeholder map	Problems involving many people with different interests (e.g., low voter turnout)
Customer journey map	Problems that unfold over time (e.g., improving public transport access)

Key takeaways

Journey maps break a time‑based experience into stages and identify pain points.
Use when “time” is a key dimension of the problem.
Challenge whether each stage is necessary – sometimes the best solution is to remove a step.

Empathy Map

An empathy map helps you understand a single user’s emotional state while grappling with a problem. It captures inputs (what they see/hear), internal processing (think/feel), and outputs (do/say), then distils pains and gains.

Structure of an empathy map

flowchart LR
    subgraph Input
        A[Seeing] & B[Hearing]
    end
    subgraph Processing
        C[Thinking] & D[Feeling]
    end
    subgraph Output
        E[Doing] & F[Saying]
    end
    Input --> Processing --> Output
    Output --> G[Pains & Gains]

Example: First‑time college student (living in hostel)

Seeing: Dorms, canteen, new people, unfamiliar rules.
Hearing: Complaints, gossip, commands, parents on phone.
Thinking: “Will I fit in? Is he trustworthy? Should I try new food?”
Feeling: Lost, anxious, socially conscious, bored, depressed, or elated (new freedom).
Doing: Making bed, meeting friends, exploring city, binging on social media.
Saying: Complaining about feeling inadequate, asking for help.

Pains (distilled): Inadequate role models, improper guidance, risk of bad company, homesickness.

Gains (distilled): Developing self‑confidence, exploring capacities, meeting new people.

The pain‑gain equation

At every moment, people subconsciously compare pain and gain. As long as gain > pain, they stay; when pain dominates, they leave.
Example: Fans queue 2 hours in scorching heat for an IPL match (gain of watching match outweighs pain). Same person won’t queue 1 minute at an ATM (pain of waiting > gain of cash).

Exam tip: Empathy maps reveal why a user tolerates (or rejects) a situation. To retain users, amplify gains and reduce pains – never assume your idea wins on its own.

Key takeaways

Empathy map: input (see/hear) → processing (think/feel) → output (do/say) → pains & gains.
Pains and gains are derived from observation, questionnaires, and triangulation.
User behaviour is driven by a continuous pain‑gain calculation; keep gains > pains.

Buyer Persona

A buyer persona (persona = “mask”) is a deep, microscope‑view profile of a target user. It goes beyond demographics to uncover objectives, fears, needs, and influence channels.

Components of a persona

Dimension	Example (electric bike for college student)
Demographics	Age 21, graduate, family income ₹15L/yr
Objectives	Go from A to B independently; easy on pocket; convenient; safe; environmentally friendly
Fears / Anxieties	Range anxiety; high maintenance cost; misuse by friends; poor after‑sales service
Needs	Quick, low‑cost maintenance; endurance for two riders; ample hood space
Influence channels	Social media, campus events, role models, online ads
Sales channels	Online booking, dealership network, direct sales
Usage frequency	Daily commute

Purpose

The persona helps you design and communicate a solution that addresses the real person behind the mask. It combines all previous empathy tools into a single actionable profile.

Key takeaways

Persona = detailed, realistic portrait of a typical user (not a stereotype).
Include demographics, objectives, fears, needs, and channels.
Aligns product/service design with what the user actually values.

Summary: Seven Techniques for Empathy and Problem Definition

The lecture series presented seven interconnected tools:

Jobs to Be Done (covered earlier)
Problem Exploration Map (covered earlier)
Stakeholder Map
Customer Journey Map
Empathy Map
Buyer Persona
(Implicitly, synthesising all to define the problem)

Together they provide a complete understanding of the user, the system, and the emotional landscape – setting the stage for sharply defining the right problem to solve.

Key takeaways

No single tool is enough; combine them based on the nature of the problem (root causes, multiple stakeholders, time dimension, emotional state).
Empathy is a continuous, iterative process – the idea evolves as you learn.
The ultimate goal: define a problem that is real, human‑centred, and actionable.

Define

Define is the stage where you synthesize the vast empathy-gathered data into a focused, actionable problem to solve. After understanding the user’s world, you may feel “there are too many problems.” Define filters out the noise and picks the one problem worth solving — a problem that is both impactful and within your realistic reach.

Formally, this stage enforces bounded empathy — empathy constrained by two practical guardrails.

Bounded Empathy

Empathy without boundaries leads to unrealistic promises. Two boundary conditions contain the problem space:

Boundary	Meaning
Technical Feasibility	Can the solution be built with current (or foreseeable) technology / competence? If you lack the technical capability, do not touch the problem.
Business Viability	Does solving this problem make business sense? If it does not generate value (today or tomorrow), it is a charity, not a design challenge.

Together, these define what you can and should solve — the ambition is bounded, not limitless.

flowchart LR
    A[Customer / Stakeholder Needs] --> B{Bounded Empathy}
    B --> C[Technical Feasibility]
    B --> D[Business Viability]
    C & D --> E[Problem Worth Solving]

Exam tip: “Bounded empathy” is the key term. Any exam question about practical problem selection will hinge on these two constraints. Do not confuse it with boundless empathy.

Pareto Principle (80/20 Rule)

Now, even within the bounded set, not all problems are equal. The Pareto Law states:

80% of the impact comes from only 20% of the problems.

Therefore, solving the right 20% delivers 80% of the customer goodness. Prioritise those high-impact problems and ignore the rest.

How to apply: list all customer/stakeholder demands → identify the subset (≈20%) that causes the biggest pain or unlocks the biggest benefit → focus all effort there.

MECE Framework

To precisely identify that 20%, use the MECE principle (coined by Barbara Minto at McKinsey). MECE stands for:

Mutually Exclusive – Each problem is defined so that it does not overlap with another. There is no double-counting.
Collectively Exhaustive – The set of chosen problems covers the entire problem space. Solving them all fully addresses the original situation.

Example (from lecture): Suppose you have three problems. You must define them so that Problem 1, Problem 2, and Problem 3 are distinct (mutually exclusive), yet together they account for every pain point (collectively exhaustive). This tight definition ensures you don’t waste effort on gaps or overlaps.

Worked Example (Hypothetical)

Problems identified (customer cafeteria)	Can we technically solve it?	Does it make business sense?	Impact (1-10)
Long queue at lunch peak	Yes – add self-service kiosks	Yes – reduces staff cost	9
Unhealthy menu options	Yes – partner with diet supplier	Medium – premium pricing possible	7
No vegan options	Yes – minor menu change	Low – small demand → low ROI	4
Uncomfortable seating	Yes – replace chairs	Marginal – cost > benefit	3

Apply Pareto: The top 20% = “Long queue at lunch peak” (impact 9) and “Unhealthy menu” (impact 7) → two problems out of four = 50% (close to 20% considering weight). The others are dropped because they don’t meet the impact threshold.

Apply MECE: Ensure “Long queue” and “Unhealthy menu” are mutually exclusive – they are separate root causes. Combined, they cover the major pain points (collectively exhaustive for the high-impact set).

Key Takeaways

Bounded empathy = empathy limited by technical feasibility and business viability. You cannot solve everything.
Pareto 80/20 rule directs attention to the few problems that cause the most impact.
MECE (Mutually Exclusive, Collectively Exhaustive) ensures problem definitions are crisp and complete.
Together, these tools transform overwhelming empathy data into a precise, solvable problem statement.
The Define stage is the gateway to ideation – you enter it only after you know which problem to solve and why it matters.

Applying Design Thinking: Staff Canteen Project

The lecture shifts from theory to practice by applying the design thinking framework to a real-world context: the IIM Bangalore staff canteen. The goal is to observe, empathise, and define problems through three structured exercises: a problem exploration map, a stakeholder map, and a customer journey map.

Problem Exploration Map

A mind map that visually captures observed problems and their possible root causes. The exercise explicitly asks for 5–6 problems encountered in the video (either seen directly or discussed by interviewees), each linked to underlying causes.

Purpose: Systematically explore the problem space before jumping to solutions.
Format: Mind map (digital or pen-and-paper).
Focus: Problems → Root causes. No prioritisation yet — that comes after.

Exam tip: The "problem exploration map" is the first step in the Empathise stage. Don't confuse it with a problem statement; it's a divergence tool to surface many issues.

Stakeholder Map

Identify the key stakeholders visible or interviewed in the canteen video, then document their challenges regarding the cafeteria.

Stakeholder (example from video)	Likely challenges (based on transcript)
Cooks / kitchen staff	Workflow bottlenecks, long hours, equipment limitations
Serving staff	High demand during lunch rush, queue management
Customers (employees/students)	Waiting time, food quality, variety
Management	Cost control, hygiene standards, resource allocation
Cleaners / utility staff	High volume of dishes, waste disposal
Delivery / procurement staff	Supply chain timing, freshness

Note: The transcript does not list exact stakeholders; these are reasonable extrapolations from context. Students must re-watch the video to populate their own map.

Purpose: Visualise relationships and pain points for each group.
Format: Node-and-link diagram, with stakeholder names and their challenges.

Customer Journey Map

Create a journey map tracing a typical customer (e.g., a person coming to eat) or a cafeteria employee through the day's process.

Customer journey: Arrive → Queue → Order → Pay → Sit → Eat → Leave → (possible follow-up).
Employee journey: Start shift → Prep food → Serve customers → Clean → Restock → End shift.

Each journey should capture touchpoints, emotions, pain points, and opportunities.

Purpose: Understand the end-to-end experience, not just isolated moments.

Identifying Critical Problems

After creating all three maps, synthesise findings to pick the most critical problems that must be solved first. This aligns with the Define stage of design thinking.

Key takeaways

Three deliverables: problem exploration map (5–6 problems + root causes), stakeholder map (key stakeholders + challenges), journey map (customer or employee experience).
All must be based on careful re-observation of the canteen video — do not invent problems.
The goal is to empathise with multiple perspectives and define the most critical issues before ideating solutions.
Use mind map software or simple pen and paper; format matters less than thoroughness.
The exercise bridges theory (design thinking process) and practice (real canteen context).

Prototype, Test and Scale

The Need for Prototyping

Generating many ideas (quantity yields quality) is only the first step. With potentially 100,000 ideas, you cannot take every one to market. The challenge is to sift through them and identify the gems — not by listening to the loudest voice or testing each exhaustively, but by running small, fast experiments.

Prototyping Mentality

Prototyping is a mindset of trying things out before full market launch — ideally with customers. The goal is to fail cheap and fail early, gathering feedback through low-fidelity setups (rough, inexpensive models of a product or service). This minimizes risk and cost while learning what works.

Three Core Aspects of Module 4

Aspect	Description
What prototypes are	Physical models or service simulations that capture the core idea for testing.
Low-fidelity testing	Presenting unfinished solutions to customers so they can give input before a polished version is built. The key phrase: quick and dirty protos.
Scaling	Only the winning prototypes (those validated by testing) proceed to full-scale implementation.

Creativity vs. Innovation

Creativity – generating novel ideas.
Innovation – scaling those ideas to create real impact.
Scale is the only proof of innovation. Without multiplication, an idea remains in the realm of creativity.

Design Thinking Process (Connection to Previous Modules)

The overall model runs:

flowchart LR
A[Inspiration<br/>how & why] --> B[Empathize<br/>understand pain points]
B --> C[Ideate<br/>generate many ideas]
C --> D[Prototype & Test<br/>validate with low-fidelity]
D --> E[Scale<br/>winning protos go to market]

Module 4 covers the final two steps: validating ideas through prototyping and then scaling.

Real-World Application: The Cafeteria Case

Throughout the design thinking journey, a live test case is used — the staff canteen (or cafeteria). By now, students should have:

Understood current and potential issues.
Developed candidate ideas.
(If in Bangalore) visited the actual cafeteria to observe problems in native context.

The module expects quick and dirty prototypes to solve these complex, real-world problems.

Exam tip: The distinction between creativity and innovation is a high-yield concept. Remember: scale is what turns creativity into innovation. Prototyping is the bridge that allows you to fail cheaply before committing to scale.

Key takeaways

After ideation, use prototyping to filter the best ideas — not all 100,000.
Prototyping mentality: test early, fail cheap, get customer input via low-fidelity setups.
Only winning protos get scaled; scale is the proof of innovation.
Design thinking flow: Inspiration → Empathize → Ideate → Prototype → Scale.
The cafeteria case provides a concrete, live context to apply these concepts.

Idea Shortlisting

When faced with a large pool of ideas (e.g., 500 from a workshop), the goal is to reduce them to a manageable set (e.g., 50) using disciplined mental heuristics. Two complementary rubrics guide this filtering.

Rubric 1: Desirability, Feasibility, Viability (DFV)

At the core of design thinking is the trinity of human desirability, technical feasibility, and business viability. All three must be evaluated simultaneously — not sequentially — to find the global optimum rather than a local one.

Human desirability (not customer centricity): Does this solution address an implicit, future-oriented human need? Classic fallacy: reducing design thinking to customer centricity. The “human” includes sellers, buyers, and all stakeholders — the aim is a solution that humans truly crave, beyond stated wants.
Technical feasibility: Does the necessary technology exist? Can the project be executed within time and budget given current technological base? If not, an otherwise desirable idea must be parked until the technology matures.
Business viability: Does the idea make commercial sense? This is the Achilles’ heel of many startups — customer happiness and technical capability do not guarantee profitability. Example: quick commerce in 2025 – customers are delighted, but companies bleed money.

The three dimensions do not always have equal weight. An organization strict on ROI may double down on viability; a startup focused on traction may double down on desirability. The key is to apply the rubric as a simultaneous filter to distill only ideas that meet all criteria.

Rubric 2: Impact–Time Matrix

Plot every idea on a 2×2 matrix of potential impact vs. time to results (based on prior knowledge). No single “silver bullet” can cure all ailments; an organization needs a portfolio of ideas across four quadrants:

Quadrant	Impact	Time to Results	Term	Purpose
Low impact, quick results	Low–Moderate	Short	Starters	Give instant confidence and rally the team/customers around innovation.
High impact, quick results	High	Short	Stars	Leverage technological leapfrogging (e.g., cloud over on-premise ERPs, SAP over mainframes).
High impact, long time	High	Long	Pipeline	R&D-type ideas that pay off in 2–3 years.
Low impact, long time	Low	Long	Pipe dreams	Candidates to be parked indefinitely.

Exam tip: Do not treat DFV as a weighted average or a sequential checklist. The strength of the rubric comes from simultaneous evaluation. Similarly, the impact–time matrix demands a portfolio view — never chase only stars.

Key takeaways

DFV rubric filters ideas by human desirability (stakeholder-centric), technical feasibility, and business viability — all three at once.
Impact–Time matrix classifies ideas into starters, stars, pipeline, and pipe dreams; build a balanced portfolio.
Human desirability ≠ customer centricity; includes all stakeholders and implicit future needs.
Technological leapfrogging allows late entrants to become stars.
Design thinking brings discipline and method to creative idea selection.

Why Prototyping

A prototype is worth a thousand meetings. Instead of pitching an idea with slides, put a simple prototype on the table – people play with it, discover unexpected uses, and become convinced faster. This section explains why prototyping is essential, what a prototyping mentality means, and how to use different types of prototypes to learn, sell, and improve.

The Prototyping Mentality

Prototyping requires being okay with imperfection. We naturally seek clarity and certainty, but that kills creativity. A prototyping mentality means:

Having a provisional attachment to your ideas – you are willing to change or abandon them.
Being willing to fail publicly – every post, every model is a chance to learn.
Soliciting feedback early and often – it saves wasted effort, time, and reputation, even though it takes courage.

“Learn to kill your darlings.” – Stephen King. If you don’t kill your own pet ideas, they will die with you when the market rejects them.

Key Reasons to Prototype

Reason	What it does	Example
Clarity for yourself	Converts abstract thoughts into tangible form; reveals hidden problems (weight, cost, manufacturability).	IDEO’s steel shopping cart: only when built did the team see it was heavy, bulky, and costly to produce.
Visibility for investors/stakeholders	Shows progress and builds confidence; gives something to interact with instead of waiting for the final product.	A startup shows a wireframe app or paper model to prove money is producing results.
Identify issues early	Accelerates discovery of flaws that planning missed; enables phased implementation rather than a “big bang” launch.	A movie director screens to a small audience to get critique before the global premiere.
Solicit timely feedback	Catch problems when they are cheap to fix; learn from real users.	The speaker’s Instagram videos improved by posting, tracking likes/views, and tweaking – a continuous prototyping cycle.
Soft selling	Creates a vision in the customer’s mind; lowers perceived risk.	An architect’s scale model sells a barren site; a clickable app wireframe sells an idea before coding.

Two Types of Prototypes

Prototypes serve two distinct purposes: functional (works like the final product) and aesthetic (looks like the final product). Both are essential.

Type	Definition	Example
Functional prototype	Works like the final product but may not look like it.	A working watch mechanism without a case – tested for water resistance, shock, temperature.
Aesthetic prototype	Looks like the final product but may not work.	A watch shell with the correct shape and materials – used to get feedback on appearance and features.

Worked Example: Titan Edge Watch

In 1997, Titan wanted to launch the world’s thinnest watch – so thin the case matched the bracelet width, with 50 m water resistance. International experts dismissed it (“only for a museum”).

The team built two prototypes:

Functional prototype – a working movement that could be submerged, frozen, heated, and shaken. It did not look like a watch.
Aesthetic prototype – a beautiful thin case without a working movement. It looked exactly like the planned product.

Both were given to Titan employees to wear. Feedback revealed that customers were willing to give up a second hand (and even a day/date calendar) to have the ultra-thin design. The watch became a runaway success.

Exam tip: The Titan case illustrates how functional and aesthetic prototypes together uncover trade-offs (fewer features vs. slimmer design) that no amount of PowerPoint could reveal.

Key Takeaways

A prototype conveys an idea faster and more honestly than a presentation – “a prototype is worth a thousand meetings.”
Five core purposes: gain clarity, build investor confidence, find issues early, solicit feedback, and soft-sell.
Use both functional (works like it) and aesthetic (looks like it) prototypes to learn different things.
A prototyping mentality means embracing imperfection, failure, and the courage to kill your darlings – your own cherished ideas.

Rules of Prototyping

Three core rules guide effective prototyping in design thinking. Each aims to maximize learning while minimizing wasted time and resources.

1. Do the last experiment first

Test the most difficult, highest-risk hypothesis before anything else. In a chain of assumptions, the one that will break the entire project is the one to validate first.

Intuition: People naturally start with easy tasks to build confidence. Design thinking flips that — tackle the hardest part first, because if it fails, everything else is irrelevant.

Worked example: ATM development
The critical hypothesis for ATMs was: Will consumers trust a machine to give them cash? Not the counting mechanism, security, or connectivity. To test this, Diebold and NCR built a facade ATM with a human behind the wall counting and handing out money. Customers believed it was a machine. Once comfort was validated, all other technical challenges became secondary.

Another example is the privacy concern: customers wanted to be sure nobody watched them enter their PIN. Instead of installing expensive cameras, designers placed a convex reflector (like a rear-view mirror) on the ATM. The reflector gave the user a quick visual check of their surroundings, creating a sense of privacy at near-zero cost.

Worked example: PhD or teaching?
A student wanted a PhD to become a good teacher. The "last experiment" — teaching — was deferred until after the PhD. The advice: teach now. If you discover you don't enjoy teaching, the PhD is wasted. Do the hardest test (do you actually like teaching?) before committing years of effort.

Worked example: Writing a book
Would-be authors often seek a publisher before writing. The last experiment is writing itself. Start writing first; if you can’t produce content, a publisher will not help.

flowchart LR
  A[List all hypotheses] --> B[Identify the most critical / hardest]
  B --> C{Test hardest hypothesis first}
  C -->|Passes| D[Proceed with easier ones]
  C -->|Fails| E[Pivot or stop – no wasted effort]

2. Maximize learning per unit time and dollar

A prototype's real output is not a thing — it is learning. Therefore, design experiments to pack as many tests as possible into a limited budget (e.g., one day, $1,000).

Method: Use quick and dirty prototypes — simple, low-fidelity models made from readily available materials. Do not aim for elegance; aim for speed of insight.

Example: Apple iPhone icon size
Before the iPhone (2007), touch icons did not exist. The team needed to find a single icon size that worked for thumbs of all sizes (American, Japanese, Indian; men, women, children). In a top-secret project (Project Purple), they built a simple game: different-sized icons appeared on screen, and users had to press them as fast as possible. The speed of response determined the optimal size. Result: three square pixels — the standard still used today. This was a quick, dirty, and cheap experiment inside a high-security environment.

Exam tip: "Quick and dirty" does not mean sloppy; it means fast and focused on the essential question. The fidelity of the prototype should match the risk of the hypothesis.

3. Fail faster to succeed sooner

Accelerate the learning cycle by embracing failure as data. Each failure is a prototype that taught you what doesn't work. The faster you fail, the sooner you converge on a solution.

Example: James Dyson’s bagless vacuum cleaner
Dyson ran over 5,000 prototypes before perfecting the cyclone-based design. He did not see failures — each was a step toward the principle of using a miniature tornado to separate dust (no bag, no suction loss). The same approach gave him the Airblade hand dryer (air jet, not hot air).

Example: Thomas Edison
Edison meticulously documented every failed prototype. He treated failure as a necessary part of the path to success.

The IDEO Tech Box
IDEO, a leading design consultancy, keeps a physical repository of failed prototypes — the tech box. When a new client arrives, the team first raides the tech box: can a previous failure be repurposed for this new context? This cuts learning curves and prevents trashing ideas that may work elsewhere.

Example: Google Glass → Google Lens
Google Glass failed because it invaded privacy and required wearing a device. But the same technology, embedded into a phone camera, became Google Lens — a widely successful app. The failure of one form factor became the success of another.

Key insight: No prototype is a failure; it is a learning event that may find its use later.

Summary of the three rules

Rule	Core idea	Key example	Takeaway
Do the last experiment first	Test the hardest hypothesis before easy ones	ATM human-facade test	Avoid wasting years on assumptions that kill the entire idea
Maximize learning per unit ($, time)	Pack many cheap, fast experiments	Apple iPhone icon game (3 pixels)	Prototype fidelity = cost of learning, not polish
Fail faster to succeed sooner	Treat each failure as data; reuse it	Dyson’s 5,000 prototypes → cyclone; IDEO tech box	Speed of failure = speed of insight

Key takeaways

Prototyping is about learning, not building a finished product.
The most powerful rule: test the riskiest assumption first.
Use quick and dirty prototypes (available materials, simple tests) to generate insight rapidly.
Embrace failure — document it, store it, and reuse it in new contexts.
A failed prototype today may become a successful innovation tomorrow (Google Glass → Google Lens).

Prototyping Methods

Prototypes are low-fidelity, throwaway models that bring an idea to life using whatever materials are available. Their purpose is exploration, not perfection — low fidelity makes it easy to discard and move to the next iteration. This applies equally to physical products and services (experiences, emotions, service processes).

Product Prototyping Methods

Method	How It Works	Why It Works
Paper prototyping	Draw interface screens on Post-it notes; move them in sequence to simulate user flow (e.g., a taxi booking app: screen 1 → tap → screen 2 → fill form, etc.)	Fast, cheap, lets the designer and user rearrange quickly; no coding needed.
Lego and clay prototyping	Use Lego bricks or synthetic clay (Play-Doh) to build 3D representations of the product.	Makes people playful; hands-on manipulation clarifies how the idea will manifest physically. Works even with senior, serious stakeholders.
Quick and dirty prototyping	Construct a physical model using available materials — wood, thermocol, cardboard, etc.	Validates that the idea can be made and brought to life with whatever is at hand.

Exam tip: Paper prototyping is especially powerful for UI/software products because it lets you test user flows before writing any code — and the cost of change is zero.

Service Prototyping Methods

Services are intangible; they unfold over time and involve human interactions. Four methods reveal how the service will be experienced:

Storyboarding

Borrowed from advertising. Draw the service “frame by frame” as a sequence of scenes (e.g., a bank re-designing the account-opening process: first scene – customer enters, second scene – greeter directs, third scene – form filling, etc.).

Skits and Plays

Act out the service in real time. Roles are assigned, physical layout is simulated. Helps identify pain points (e.g., an elderly person withdrawing cash: does the process feel secure?).

Storytelling (SCQA Framework)

Narrate the idea as a coherent story using the SCQA structure:

Situation: The current state (e.g., “300–350 people dine in the staff canteen during lunch in 2 hours.”)
Complication: The problem (e.g., “At 1 pm, long queues form at billing and food counters.”)
Question: The design challenge (e.g., “What technological or people-based solution can reduce queue length and improve convenience?”)
Answer: The proposed idea(s) (e.g., weekly coupons, QR code scanning, punch‑card authentication)

If the listener finds the story coherent, the idea is roughly on the right track — no physical prototype needed.

Scenario Analysis

Test the idea against three possible scenarios:

Scenario	Description	Example (Staff Canteen)
Best-case	Everything goes right	No food wasted; exact quantity prepared and tasty.
Usual-case	Normal variation	Typical waste equivalent to 10–20 extra portions.
Worst-case	Everything goes wrong	Waste doubles the usual amount.

For each scenario, ask: which ideas make sense here? This filters ideas by robustness — the same solution may not suit all situations.

Key takeaways

Product prototypes: paper, Lego/clay, quick and dirty — all low-fidelity and disposable.
Service prototypes rely on storyboarding, skits, storytelling (SCQA), and scenarios.
SCQA narrates the problem → solution story; a coherent story validates direction without building anything.
Scenarios test ideas under best‑, usual‑, and worst‑case conditions, revealing where each idea fits.
Playfulness (Lego, clay) and cheap materials (Post‑its, cardboard) keep iteration fast and psychological attachment low.

Models of Scaling

Traditional design thinking stops at prototyping and testing, leaving a gap: what happens after a validated idea? Scaling addresses that gap by giving structure to the transition from prototype to real-world impact. Two key techniques: the Business Model Canvas and OKR (Objectives and Key Results).

Business Model Canvas (BMC)

The BMC, pioneered by Alexander Osterwalder, provides a one-page framework that forces clarity around how an idea becomes a functioning business. It answers three fundamental questions:

How does the business generate value? (value-creating activities)
How does the business deliver value? (value-delivering activities)
How does the business appropriate value? (profit-making activities)

These map onto three streams: upstream (value generation), midstream (value proposition), and downstream (value delivery and capture).

BMC Components

Stream	Block	Description
Downstream	Value Proposition	The unique offering that differentiates you in the market. Without uniqueness, you are easily copied.
	Target Customer	Defined by demographics, psychographics, geography, need frequency, B2B/B2C, etc.
	Marketing Channel	How you interact with customers and stay top-of-mind.
	Sales Channel	Omnipresent, omnichannel, physical store, virtual, mobile app, franchise – your outreach mechanism.
Midstream	Value Proposition	(Same as above – sits at the centre)
Upstream	Key Resources	Critical assets: e.g., human resources, machinery, material.
	Key Activities	Core operational tasks (e.g., cooking, cleaning, serving, billing in a cafeteria).
	Key Partners	Outsourced activities: suppliers, service providers (e.g., grocery vendors, LPG suppliers, deep-cleaning contractors).
Bottom	Cost Structure	Fixed costs, variable costs, operational costs (salaries, rent, licenses, commissions).
	Revenue Streams	Income from product/service sales, IP licensing, etc.

Exam tip: The BMC reveals gaps you never considered – especially in go-to-market, cost structures, and revenue models. Use it to decide whether to pursue or pivot.

Worked Example: Cafeteria

Resources: cooks, serving staff, machinery, raw material.
Activities: cleaning, cooking, serving, billing.
Partners: grocery suppliers, LPG providers, deep-cleaning services.
Costs: salaries, rent, licenses.
Revenue: product sales.

Once you fill each block, you often discover missing pieces – e.g., no clear sales channel or underestimated fixed costs.

Objectives and Key Results (OKR)

OKR (Andy Grove, Intel; adopted by Google) provides a disciplined way to measure progress and translate ambition into actionable metrics. It contains two parts:

Objective – the what: a qualitative, aspirational goal.
Key Results – the how: quantifiable milestones that define success.

OKR Structure

flowchart LR
    A[Objective: What do you want to achieve?] --> B[Key Result 1: Measurable outcome]
    A --> C[Key Result 2: Measurable outcome]
    A --> D[Key Result 3: Measurable outcome]
    B --> E[Achieving all KRs → Objective met]
    C --> E
    D --> E

Example 1: Design Thinking Course

Objective: Students understand and practice design thinking in life and career.
Key Results:
1. 80% of students participate in live projects.
2. 70% pass the subjective exam.
3. 800 of 1000 students attend live classes and engage in discussions.

Example 2: Weight Loss

Objective: Shed 5 kg in one month and maintain loss for one year.
Key Results:
1. Eat small meals five times a day (tick).
2. Avoid greasy items for one month (tick).
3. Walk 10,000 steps daily (tick).

Exam tip: OKRs make the subjective objective. Peter Drucker said, “What cannot be measured cannot be managed.” Always define 3–5 key results per objective; achieving all KRs guarantees the objective.

Key Takeaways

Scaling requires a structured business model (BMC) and a measurement system (OKR).
BMC covers value generation, delivery, and capture – each block must be filled before scaling.
OKR uses measurable key results to track progress toward a qualitative objective.
Both techniques force discipline and reveal blind spots (e.g., missing channels, unrealistic costs).
Use BMC to validate viability; use OKR to monitor execution and pivot when metrics don’t align.

Applying Design Thinking to Career, Rejection, and Innovation

Design thinking is often misunderstood as a process for designers only—a misconception that limits its application. In reality, design thinking is a systematic model of thinking that applies to anyone, anywhere: homemakers, students, entrepreneurs, government leaders, and individuals solving everyday problems. It is not about designing physical objects; it is about designing your own thinking. The core principles apply across fields, from career planning to product innovation in IT and R&D.

Misconceptions About Design Thinking

“I need to be a designer.” — False. The term “design thinking” originates from design, but its modern application spans problems of any kind.
“It’s only for startups or tech.” — False. It works in large companies, government, NGOs, and even personal life (e.g., exam preparation, household challenges).
“It requires youth.” — False. Age and background are irrelevant. Design thinking is for everyone at any stage.

Exam tip: The most common exam trap is equating design thinking with visual design or engineering. Always remember: the “design” here refers to designing the thinking process, not artifacts.

Career Planning with a Design Thinking Mindset

Career in decades — a fundamental shift from thinking in years to decades. A decade is a vast stretch of time; underestimate what can happen in a year, overestimate what can happen in a decade. Plan life in five-decade blocks: e.g., work in a large company, then dabble in startups, then contribute to society, then explore spirituality.

Own your career — do not delegate career responsibility to parents, HR, or teachers. Most possibilities (e.g., tattoo artist, nail painter) did not exist a generation ago; 50% of future jobs do not exist today. Only you can navigate this landscape.

Focus on what will not change — rather than chasing trends, anchor on enduring fundamentals: education, health, mental and spiritual hygiene. These remain valuable regardless of disruption.

Career Principle	Action
Think in decades	Set decade-wise goals; resist quarterly or yearly myopia
Take ownership	Accept that nobody else knows what is best for you
Focus on the immutable	Invest in education, health, and self-awareness

Handling Rejection: Input, Not Identity

Rejection is inevitable—24 out of 25 PhD applications were rejected for Dr. Pavan Soni; the one acceptance (IIM Bangalore) turned into a blessing in disguise. The key is to treat rejection as input for learning, not as a verdict on worth.

flowchart TD
  A[Rejection] --> B{Am I clear about what I want?}
  B -->|Yes| C[Rejection does not hurt; it redirects]
  B -->|No| D[First clarify – what do I NOT want?]
  D --> E[Rejection then becomes a signal to refine direction]
  C --> F[Develop tenacity: keep trying]
  E --> F

If you are clear about your objectives, rejection strengthens resilience.
It is okay to be confused about what you want, but be very clear about what you don’t want.
Every rejection is an opportunity to learn something new—absorb it, don’t bulldoze through.

Saying No: Zone of Concern, Zone of Influence, Non-Negotiables

Young professionals often say “yes” to impress others, leading to diluted efforts and loss of reputation. The antidote is understanding two zones:

Zone of concern: things that perpetually bother you but are outside your control (e.g., how others perceive you, global events). Shrink this zone.
Zone of influence: things you can actively do something about. Say yes only to items within this zone.

Non-negotiables are personal boundaries that protect reputation and integrity. One mistake can destroy a reputation built over a lifetime. Examples from Dr. Soni: never attending parties with only eating/drinking as the goal, never accepting kickbacks.

Exam tip: “Say no more than you say yes” is a tested concept. Explain why: overcommitting leads to poor delivery, loss of trust, and self-doubt. Say “yes” only if you can do that thing better than anyone else.

Design Thinking in IT: Lessons from India’s Large-Scale Innovations

India’s success with FASTag, Digi Yatra, and UPI demonstrates three principles of applying design thinking at scale:

Human-centric simplicity – technical complexity is masked from the user. Even an illiterate person can use the interface (e.g., facial recognition at airports with minimal instruction).
Indigenous platforms – self-reliance (Atmanirbhar Bharat) reduces dependency on foreign technology (e.g., homegrown GPS, Aadhaar). This ensures adaptability to local contexts.
Technology + human, not technology minus human – human assistance always remains available (e.g., a human at every FASTag boom barrier). Technology augments, not replaces. Evidence: cash circulation in India increased alongside UPI adoption.

Principle	Example	Why It Matters
Human-centric	Digi Yatra interface	Scales across literacy levels
Indigenous	UPI, Aadhaar	Local control, low cost
Tech + human	FASTag + attendant	Builds trust, handles edge cases

Exam tip: The “technology plus human” insight is a common point of discussion. Contrast with the fear that AI displaces labor—in India, technology complements human skills (proven by concurrent growth of UPI and cash usage).

R&D and Sustained Creativity: The Need for Multiple Affiliations

R&D professionals face mental blocks when they focus exclusively on their field. The antidote is multiple affiliations—cultivating hobbies, artistic pursuits, and diverse interests.

Nobel laureates are 20% more likely to have an artistic hobby than their peers (e.g., Richard Feynman played drums, Einstein played violin).
Hobbies provide fresh perspectives and mental dispersion.
Examples from India: Dr. APJ Abdul Kalam was a prolific writer, poet, and lifelong learner; he was reading Stephen Covey when he died while lecturing.

R&D gratification is deferred (years, not quarters). A long-term view, a holistic life, and patience are essential. Avoid rushing; life is long.

Key Takeaways

Design thinking is for everyone, not just designers or startup employees.
Plan your career in decades, own it, and invest in what will not change (education, health).
Rejection is learning input; clarity of purpose neutralizes its sting.
Say no to shrink your zone of concern and protect your reputation; say yes only where you excel.
In IT, build human-centric, indigenous solutions that augment human effort rather than replace it.
For R&D, cultivate multiple affiliations (hobbies, arts) to sustain creativity and avoid burnout; develop a long-term perspective.

What is Design Thinking

What is Design Thinking?

Design thinking is a definition of problem solving — a human-centered, iterative approach to tackling complex, ill-structured challenges. The module establishes its core meaning, explains its recent surge in importance, introduces a process model, contrasts it with traditional problem solving, presents its fundamental tenets, and identifies the custom conditions where it is most effective.

Definition of Problem Solving

Design thinking reframes problem solving as an empathic, creative, and iterative activity. It is not a single tool but a mindset and structured process that puts human needs at the center.

Why Design Thinking Matters Now

The lecture emphasizes that design thinking has assumed significant importance in recent years. This rise reflects a shift toward innovation driven by user insight, rapid experimentation, and cross-disciplinary collaboration — especially in contexts where conventional analytical methods fall short.

Process Model of Design Thinking

A process model (to be detailed in later modules) guides practitioners through stages typically including:

Understanding the problem deeply (empathy, define)
Generating ideas (ideate)
Developing prototypes
Validating solutions with users
Scaling the solution after validation

This model is nonlinear and iterative.

Contrast with Traditional Problem Solving

Design thinking differs from traditional models of problem solving, which are often linear, deductive, and solution-focused from the start. The key distinctions:

Aspect	Traditional Problem Solving	Design Thinking
Starting point	Problem statement (often given)	User empathy and need-finding
Approach	Analytical, deductive	Creative, abductive
Solution path	Fixed steps, converge quickly	Iterate, diverge then converge
Risk tolerance	Low; avoid failure	Embrace failure as learning
Outcome	Optimal known solution	Novel, human-centered solution

Understanding where to use each model is a core learning goal.

Fundamental Tenets (Principles)

The module introduces fundamental tenets that underpin all design thinking practice:

Human-centeredness – Empathy for users drives every decision.
Iteration – Repeated cycles of prototyping and testing refine ideas.
Bias toward action – Make tangible artifacts early, rather than over-analyzing.
Embracing ambiguity – Tolerate uncertainty during divergent phases.
Collaborative diversity – Cross-functional teams generate richer solutions.

Conditions for Using Design Thinking

Design thinking makes huge sense under specific custom conditions:

Problems are ill-defined or complex (no single right answer).
User needs are poorly understood or rapidly evolving.
The context involves high uncertainty (new markets, new technologies).
Creative, breakthrough solutions are required, not incremental improvements.

Exam tip: Be ready to explain when to use design thinking vs. traditional problem solving. The module explicitly targets this distinction so you can "give a rebuttal" if quizzed.

Key takeaways

Design thinking is a human-centered problem-solving definition and approach.
Its recent significance stems from its effectiveness in complex, user-driven innovation.
The process model covers understanding, ideation, prototyping, validation, and scaling.
It contrasts with traditional linear methods; use design thinking for ambiguous, empathy-intensive challenges.
Core tenets: human-centeredness, iteration, action bias, ambiguity tolerance, collaboration.
Most valuable in conditions of uncertainty and unmet user needs.

What is Design Thinking? A Human-Centric, Systematic Model of Problem Solving

Design thinking is a human‑centric, systematic model of problem solving. This definition strips away academic jargon: it means solving problems by deliberately putting people first, following a repeatable method, and focusing on the problem itself — not just the product or outcome.

The Three Pillars of the Definition

1. Human‑centric

Most solutions fail because they prioritise rules, policies, or technology over the human who will use or be affected by the solution.

Regulatory‑centric – e.g., airline safety demo: the crew recites the exit procedure but never checks if the passenger actually understands or can perform it.
Policy‑centric – e.g., reimbursement processes in organisations: designed for audit compliance, not for user convenience.
Product‑centric – e.g., Apple excluding chargers and using proprietary connectors: driven by product strategy, not user needs.

In contrast, human‑centric design respects all human stakeholders, not just the direct customer. Consider Nestlé Cerelac:

Stakeholder	Need
Baby	Good taste
Mother	Nutrition for child
Father	Affordability
Maid	Easy, quick preparation
Grandmother	Healthiness and consistency with traditional feeding
Pharmacist	Stock with good profit margin
Doctor	Prescribes only if it meets medical standards

No single stakeholder is “the customer”; all must be satisfied. Design thinking therefore elevates from customer‑centric to human‑centric, requiring empathy and compassion for every person in the system.

Exam tip: The most common mistake is equating human‑centric with customer‑centric. Human‑centric includes customers, employees, partners, distributors, and even regulators – anyone touched by the solution.

2. Systematic

Creativity without discipline leads to improvisation (“jugaad”) that cannot be replicated or taught. Being systematic means using a method that others can learn, demystify, and improve upon.

Myth: “Discipline kills creativity.”
Truth: The most successful people – e.g., Roger Federer, Magnus Carlsen – are highly disciplined in their methods, which is precisely what enables consistent creative output.
Systematic thinking makes a solution scalable and teachable; it transforms a “magician” into a role model.

3. Problem Solving

Design thinking is not about “designing a better product”; it is about designing your thinking to solve problems better. The solution may take the form of a product, a service, or a process, but the core is problem solving.

Everyday life is full of problems (e.g., managing weekend plans, handling ad‑hoc meetings). Learning a systematic approach enables tackling larger, more complex problems (climate change, leadership credibility, unemployment, inequality).

How the Three Pillars Connect

flowchart LR
    A[Human‑centric] --> D[Design Thinking]
    B[Systematic] --> D
    C[Problem solving] --> D
    D --> E[Repeatable, empathic, effective solutions]

A solution is only powerful when it is (1) grounded in human needs, (2) generated through a disciplined method, and (3) aimed at a genuine problem rather than a predetermined output.

Key Takeaways

Design thinking = human‑centric + systematic + problem solving.
Human‑centric ≠ customer‑centric; include all stakeholders (users, makers, investors, etc.).
Systematic does not kill creativity; it makes creativity reproducible and teachable.
The ultimate goal is better problem solving, not just better products.
Apply empathy and compassion to uncover the real human needs behind every problem.

The Linear (Stage-Gate) Model and Its Pitfalls

The linear model – also called the stage-gate model, waterfall model, or product development lifecycle – is roughly a century old. It proceeds through a fixed sequence of stages, each separated by a gate that decides whether to invest further. The canonical flow:

Idea → Preliminary Investigation → Detailed Investigation → Development → Testing & Validation → Market Launch

Although still widely used, this model systematically undermines innovation. Its core flaws are:

1. Starting with an Idea is a Bad Idea

The model starts with an idea. That locks the team into a single worldview; any challenge feels like an attack on a “baby.” The idea may be a figment of imagination that solves no real problem.

Example: Nikola Tesla’s wireless electricity transmission (Long Island tower) was a brilliant idea but solved a problem nobody had – people were satisfied with wired electricity. The project failed despite massive investment.

2. “Problem” as a Starting Point is Also Flawed

If you begin by asking customers “What is your problem?” they may have none (or can only articulate incremental improvements). Radical innovations often emerge from opportunity, not stated problems.

Example: Before the iPhone, customers using Blackberry phones would not have asked for a buttonless phone. They might request better battery or lighter weight, but not a complete reinvention. Steve Jobs’ leap of imagination – not customer problem statements – created the category.

3. Too Many Gates Kill Innovation

Multiple gates act as excuses to reject ideas early. They increase type II errors in innovation – missed innovation – where good ideas are eliminated prematurely.

Type I vs. Type II errors in innovation:

Error	Statistical name	Innovation equivalent	Example
Type I error (false positive)	Reject null when true	Failed innovation – attempted but failed	Google Plus (social media attempt)
Type II error (false negative)	Fail to reject null when false	Missed innovation – never tried	Microsoft missing Android

Cost comparison: Missed innovation is far more dangerous because it not only loses revenue but hands the opportunity to competitors. Microsoft’s failure to acquire Android is a classic type II error; Google’s failure with Google+ is a type I error.

Gates systematically kill more ideas than they approve, making type II errors likely.

4. Testing & Validation Come Too Late

Testing and validation appear at the very end of the sequence. The team spends time, energy, and money developing a product without ever showing it to the customer. When finally unveiled, the customer may say “What is this? I didn’t ask for this.” The linear model assumes you can surprise the market; in reality, you mismatch customer expectations.

5. The Model is Linear and Non-Recursive

Once a stage is passed, you cannot go back. You cannot skip a stage. This rigidity prevents iteration and learning. The result: 95% of new product launches fail – not from lack of effort, funding, or intent, but from a fundamental mismatch between what the customer needs and what is delivered.

Key takeaways

The linear stage-gate model starts with an idea, which may be irrelevant to real user needs.
Even “problem-first” approaches can miss radical opportunities because customers can’t articulate paradigm shifts.
Multiple gates increase type II errors (missed innovations), which are costlier than type I errors (failed innovations).
Late-stage testing guarantees that most resources are spent before any customer feedback.
The non-recursive, sequential structure prevents adaptation and is a major cause of the 95% product launch failure rate.

Understanding the Design Thinking Model

Design thinking is the antidote to the traditional problem-solving model. Where the traditional model fixates on the idea (or the problem) first, design thinking re-orients the entire process around inspiration, empathy, and iterative prototyping. The model is parsimonious and applicable to service design, product development, process improvement, and personal problems.

1. Inspire – The “Why” Before the “How”

Most people instinctively ask “how to solve” a problem. Design thinking insists on first answering “why to solve” – the inspiration behind the effort. Two drivers power inspiration:

Driver	Description	Example
Aspiration	A desire to do something better, to reach a higher state	Disney theme parks, Netflix’s revolution of streaming, Mahindra XUV500 (create a world-class SUV from India)
Desperation	A pressing need to overcome crisis or threat	NASA’s moon landing (Kennedy), DARPA’s Arpanet (predecessor of the internet), ISRO’s space program in a resource-starved India

Inspiration galvanises people. A leader who cannot articulate “why we are here” fails to rally the team. Examples of clear inspiration: Anand Mahindra’s vision for the XUV500, Vikram Sarabhai’s aspiration for India’s space age.

Exam tip: Never start with an idea or a problem – start with inspiration. This is the first major departure from traditional models.

2. Empathize & Define – Bounded Empathy

Empathy is the ability to proactively understand what people think and feel. It is not sympathy (reactive) or apathy (ignoring). In design thinking, empathy is the sine qua non – but it must be bounded.

Bounded empathy means empathy is constrained by two practical limits:

Technical feasibility – Can I do it? (Do I have the technology, skills, time, budget?)

Business viability – Does it make economic sense? (Will it save or make money?)

An unbounded empathy leads to promising customers everything, pleasing them but destroying business viability – a common startup failure. For example, customers desire a fully solar-powered car, but it is not technically feasible today. Quick commerce delights customers but most companies do not break even; customers would simply switch apps if one fails.

Empathize and define are collapsed into one stage: you must understand customer needs while also defining the boundary conditions from your own (business) perspective. This is the box within which ideas will later be generated.

3. Ideate – Quantity Leads to Quality

Ideas come only after inspiration and bounded empathy. The goal is not to jump to a few “great” ideas. Instead:

Generate a large quantity of ideas.
From that pool, filter to the top quality subset.

Worked example: In a workshop with 50 doctors at IIM Bangalore, 300 ideas were generated in 30 minutes. Reducing 300 → 30 produced far superior 30 ideas than starting with just 30.

Analogy: Ideas are Lego blocks. One block is useless; 10 blocks allow some creativity; 100 blocks unlock colossal combinations.

Thus the principle: quantity of ideas → quality of ideas. When ideating, allow ample time, resources, and latitude.

4. Prototype & Test

Prototyping is building a model of how the final idea would look and/or function. It gives confidence and reveals unknowns early. Two major types:

Prototype Type	Purpose	Example (Titan Edge)
Aesthetic	Focus on look, feel, form	Welding safari crystal to steel; water resistance testing
Functional	Focus on internal mechanism, performance	Ultra-thin module with long battery life, airtight seal

The prototyping mentality is to provisionally attach to an idea, not commit. Testing is done with actual customers. You start with the customer (empathy) and end with the customer (prototyping and test).

Exam tip: Emphasise that prototyping is iterative. James Dyson made 5,000+ prototypes of his bagless vacuum cleaner. Thomas Edison’s genius was perspiration, not just inspiration – “1% inspiration, 99% perspiration”. The Indian context often lacks prototyping mindset; revision and retakes are essential (like a recording with many takes).

5. Scale – The Litmus Test of Innovation

Once the prototype passes customer test, you must scale to the market. Without scale, you are only being creative, not innovative.

Pablo Picasso made one painting every day from age 8 to his 90s – 15,000+ paintings, thousands of potteries. His ability to scale (both volume and commercial value) made him one of the greatest artists.

Thus the full design thinking process:

flowchart LR
    A[Inspire] --> B[Empathize & Define]
    B --> C[Ideate]
    C --> D[Prototype & Test]
    D --> E[Scale]
    E -.->|Iterate| A

The loop from prototype back to inspiration is implied – each test feeds new understanding.

Key takeaways

Design thinking flips the traditional model: start with inspiration (why), not the idea.
Bounded empathy constrains customer understanding by technical feasibility and business viability.
Ideation prioritises quantity first; quality emerges from filtering a large pool.
Prototyping separates aesthetic and functional aspects; test with real customers.
Scale proves innovation – creativity alone is insufficient.
The model is used by great innovators (Edison, Dyson, Picasso) and even Mahatma Gandhi (unbeknownst).

The Double Diamond Model of Design Thinking

Design thinking proceeds through an alternating pattern of divergent and convergent phases — two cycles that form a Double Diamond Model.

Divergent phases: open up possibilities — explore broadly, gather many perspectives, generate quantity.
Convergent phases: narrow down — decide which problem to solve, which idea to pursue, what works.

flowchart LR
  subgraph Diamond_1[First Diamond]
    A[Inspire & Empathize<br>DIVERGE] --> B[Define<br>CONVERGE]
  end
  subgraph Diamond_2[Second Diamond]
    B --> C[Ideate<br>DIVERGE] --> D[Prototype & Test<br>CONVERGE]
  end

The five stages mapped to divergence and convergence

Stage	Mode	What happens
Inspire	—	Establish the why — the core motivation and purpose of the project.
Empathize	Diverge	Talk to many stakeholders (customers, support, back-end, front-line) to understand their experiences.
Define	Converge	Rapidly narrow to a problem worth solving — clarify scope and priority.
Ideate	Diverge	Generate a high quantity and variety of ideas; suspend judgment to maximise options.
Prototype & Test	Converge	Validate ideas through tangible prototypes and real feedback; converge on what actually works.

After validation, the solution can be scaled.

Gandhi as a case study: design thinking in practice

Mohandas Karamchand Gandhi’s life illustrates the same diverge–converge pattern, decades before the term “design thinking” existed.

1. Inspire (the “why”) — a turning point

1888: Gandhi, a young barrister in South Africa, is thrown out of a first-class train compartment because of his skin colour.
This event sparked his inspiration: millions of Indians (in South Africa and in India) are treated as second-class citizens in their own country. The purpose became clear — dignity and independence.

2. Empathize (diverge)

Between 1888 and 1915, Gandhi immersed himself in the lives of ordinary Indians.
He adopted khadi (simple, hand-spun clothing) to become indistinguishable from the common person — “be the customer you want to serve.”
Key principle: Empathy means not just understanding others but living as they live. Gandhi’s empathy was concrete: dress, diet, and daily struggles.

3. Define (converge)

Many approaches to independence existed simultaneously: violent uprising (1857), revolutionary violence (Bhagat Singh), political negotiation (Nehru, Congress).
Gandhi defined the path: non-violence (Ahimsa) combined with truth-force (Satyagraha).
This was a deliberate convergence — a single, coherent strategy.

4. Ideate (diverge)

Non-violence itself was not new (rooted in Gautam Buddha, 2500 years earlier), but the specific concept of Ahimsa + Satyagraha as a mass political tool was novel.
Gandhi generated many ideas for campaigns; the Dandi March became the focal prototype.

5. Prototype & Test (converge) — the Dandi March

Prototype: Gandhi chose a simple, relatable issue — British tax on salt (Indian salt made from Indian sun, water, labour, yet taxed by the Empire).
He walked from his ashram to the sea at Dandi, picking up a handful of salt to symbolically break the law.
Test: Three waves of volunteers advanced toward the salt pans; police brutally beat each wave. No one retaliated. After the third wave, the British gave up.
Gandhi went to jail, calling on all Indians to fill the jails non-violently, deflating the spirit of the British Empire.

6. Scale

The validated method (non-violent civil disobedience) was scaled nationwide.
Outcome: India’s independence in 1947.

Key takeaways

Design thinking follows a double diamond pattern: diverge → converge → diverge → converge.
The stages are: Inspire → Empathize → Define → Ideate → Prototype & Test → Scale.
Empathy means “be the customer you want to serve” — Gandhi wore khadi to merge with his people.
Define is the crucial convergent step: selecting one problem from many.
Prototyping (e.g., Dandi March) tests the core idea under real conditions; validation builds confidence to scale.
Historical figures like Gandhi unknowingly used design thinking — studying their lives (e.g., Lincoln, Kalam, Steve Jobs) reveals the same process.

Exam tip: Be able to map any stage of the Double Diamond to a real-world example (Gandhi is the classic). The key test is distinguishing divergent (broadening) from convergent (narrowing) actions.

Why Design Thinking Now

Design thinking as a philosophy is nearly a century old (Herbert Simon, 1940s; IDEO’s David & Thomas Kelley; Apple’s first mouse; Stanford d.school, 2004). Yet its urgency in India is recent (last ~15 years). Two major drivers explain the surge.

1. Products & Services Blurred into Experiences

No company can claim to be purely a product or a service company. Every offering is a product–service bundle that delivers an experience. The aftertaste of a purchase, not its features, determines loyalty.

Recency effect (psychology): people remember the last touchpoint most vividly. A great checkout can redeem a mediocre stay; a bad checkout erases all earlier goodwill.
Moment of truth: a high-stakes touchpoint where the customer’s overall impression is formed or shattered.

FMCG Example: Four Moments of Truth

Moment of Truth	Description	Critical factor
1. Shelf	Package placement on store shelf	Placed at ~45° to baseline for visual grab
2. Purchase	Buying decision at checkout	Long queues may cause abandonment
3. Opening	Unboxing experience	Intuitive, thoughtful packaging (e.g., Apple)
4. Disposal	Discarding the product	Complexity of disposal (e.g., batteries)

Winning products think end-to-end

Market leaders do not necessarily have the most features or the lowest price. They design the entire customer journey from pre-purchase to disposal.

Maruti Suzuki dominates Indian roads not because its cars are best, but because it ensures a great experience across buying, owning, and reselling at true value.

Key takeaways

Differentiation now hinges on experience, not product or service alone.
The recency effect means the last touchpoint (e.g., checkout, disposal) often defines memory.
Four moments of truth (shelf → purchase → opening → disposal) must be designed holistically.
High disposable income and aspiration in India push organizations to invest in experience management.

2. Multifaceted Problems (Wicked Problems)

Modern challenges are wicked problems: “hairy”, with many moving parts, impossible to solve with single interventions. Design thinking is purpose-built for these.

Comparison: Tax evasion (relatively straightforward cause) vs. low election turnout (complex interplay of trust, accessibility, civic duty) – election is the more wicked problem.
Examples of wicked problems today – geopolitical instability, erosion of trust in capitalism, abandonment of formal education, decline of organised religion.

Complex ≠ Complicated

Simple	Complex	Complicated
Few parts, clear cause–effect	Many interdependent parts, emergent behaviour	Many parts but with known rules and predictable outcomes
e.g., making tea	e.g., designing a city traffic system	e.g., assembling a car engine

Wicked problems are complex. They require complex thinking but simple solutions. Complex thinking is not the same as complicated thinking.

Systems Thinking (Synonym for Design Thinking)

Systems thinking looks at system-level performance instead of local optimisation.

Example – Bangalore’s Silk Board flyover: A 10–11 km flyover was built to speed traffic from Electronic City to Silk Board junction. But the bottleneck simply shifted; overall throughput did not improve. This is local optimisation – improving one component while the system remains constrained elsewhere.
Root cause of local optimisation: Division of labour leads to division of attention. Nobody in a modern assembly line (e.g., Toyota) knows how to make a whole car. Each worker optimises their station, but the overall product may still fail (Toyota recalls).

Design Thinking’s Prescription

Slow down – counterintuitive, but fast thinking is just pattern recognition. Slowing down allows pattern creation and pattern breaking.
Develop deep empathy – by seeing the problem from all stakeholders’ perspectives.
Take a big-picture view – distance yourself from the problem to avoid piecemeal fixes.

Exam tip: The distinction between complex and complicated is a high-yield concept. Design thinking is for complex (wicked) problems, not just complicated ones.

Key takeaways

Wicked problems are multidimensional and resist simple fixes; design thinking addresses them.
Systems thinking > local optimisation; the whole must improve, not just one part.
Division of labour creates silos of attention – a key barrier to systems thinking.
Slowing down and building empathy are central design thinking practices.
Almost all companies now face B2C dynamics, making user-centred systems thinking essential.

Why Design Thinking Now

Design thinking has surged in importance because the business landscape has shifted. Companies can no longer rely on a simple product-push or a clear B2B/B2C distinction. Instead, they must focus on the human who ultimately uses the product — regardless of who buys it. Three major trends drive this shift: the erosion of the B2B/B2C boundary, large-scale digitization that hides complexity, and the rise of knowledgeable, restless customers who demand co-creation.

Shift from B2B/B2C to B2H (Business to Human)

Intuition: The old classification of companies as “business-to-business” (B2B) or “business-to-consumer” (B2C) is now misleading. Every organisation’s success depends on the end-user’s experience, not just the purchaser’s decision. If the user loves the product, the buyer will keep buying; if the user is ignored, the buyer will switch.

Volvo (bus example): Volvo’s customer is the government transport department (B2B), yet the company obsesses over passenger comfort — seat recline, window size, suspension, storage. The government buys Volvo precisely because passengers prefer the experience. Volvo treats itself as a B2H company.
Ford vs. Kia in India: Ford insisted on placing the indicator lever on the left (suiting left-hand-drive markets), forcing Indian drivers to change habits. Kia, entering later, tailored features (sunroofs) to local desires. Kia succeeded; Ford exited India. Lesson: modify the product to suit the consumer habit, not the other way around.
SUV trend in India: Despite cramped roads, Indians prefer large SUVs over hatchbacks. The consumer’s perspective (status, ground clearance, comfort in traffic) overrides the “practical” product logic. Companies that ignore this consumer-centric view lose.

Exam tip: The “B2H” label is the key takeaway — remember that design thinking forces a shift from product-centred engineering to human-centred experience.

Key takeaways

The B2B vs. B2C distinction is obsolete; all companies are B2H (Business to Human).
User experience drives repeat purchases and brand loyalty, even in “B2B” transactions.
Products must adapt to user habits, not force users to adapt to the product.
Understanding and anticipating consumer needs (e.g., sunroofs, SUV comfort) is a competitive necessity.

Digitization of Engagements: Masking Complexity

Intuition: Digital services succeed when they present a radically simple interface while hiding enormous backend complexity. Design thinking makes this possible by focusing on the user’s pain points and removing friction — even when underlying technology is highly complex.

Service	What it replaces	Key design-thinking feature
DigiYatra	Physical ID checks at airports	Face as identity; seamless walk-through
UPI / QR codes	Cash, card machines, net banking	Passive QR print → auto-fill merchant number
FASTag	Toll booth cash payments	Passive, tamper-proof sticker readable at any height

DigiYatra – Face recognition happens in seconds, credentials verified without user intervention. Complexity (facial mapping, data security) is invisible.
UPI – Over 40 crore daily transactions with near-zero errors. A QR code (passive print) eliminates manual entry. The user simply scans and pays.
FASTag – Works for both a truck (tag at 3.5 ft) and a sedan (tag at 1 ft). No battery, no human intervention. The same experience for all.
The wristwatch analogy: A watch shows only two hands (simple frontend); the gears and springs are hidden (complex backend). Design thinking applies the same principle: standardised at the backend, customised at the frontend.

flowchart LR
    A[User] --> B[Simple Interface<br/>(QR, face, sticker)]
    B --> C[Complex Backend<br/>(databases, algorithms, security)]
    C --> D[Seamless Result<br/>(payment, entry, toll pass)]

Exam tip: The phrase “mask the complexity” is a core design thinking principle. Expect questions that ask how DigiYatra, UPI, or FASTag exemplify this.

Key takeaways

Digitisation succeeds when it hides complexity from the user.
Design thinking prioritises ease of use and low threshold for engagement.
Passive elements (QR code, RFID sticker) eliminate human intervention and error.
The wristwatch analogy: complex backend, simple frontend — the hallmark of well-designed digital solutions.

Knowledgeable and Restless Customers

Intuition: Customers today are informed and impatient. They research products (reviews, social media, YouTube) and trust peer opinions over company claims. The power asymmetry between buyer and seller has shrunk. Companies can no longer dictate narratives; they must co-create with customers.

Pre-internet era: Customers relied on company advertisements and warranties. Today they triangulate information from multiple sources before buying.
Restlessness: Customers want solutions now. This “need for speed” can be turned into an advantage — invite customers to co-discover the problem and co-create the solution (e.g., homemakers testing new recipes for food brands).
Amazon reviews: Even a 4.7-star author cannot remove a single 1-star review. The wisdom of the crowd holds power; organisations must live up to their claims.
Democratisation of knowledge: Stock market trading no longer requires proximity to exchanges; anyone connected can participate. Tools for content creation are widely available. Knowledge is diffused, not concentrated.

What this means for design thinking: Rapid iteration, prototyping, and customer feedback loops become essential. You cannot spend years perfecting a product in a lab; you must iterate with the user.

Exam tip: The shift from “solving for the customer” to “solving with the customer” is a classic design thinking mantra. Remember the distinction: traditional division of labour (customer = problem, company = solution) is dead.

Key takeaways

Customers are knowledgeable (research-driven, skeptical of company claims) and restless (want immediate solutions).
The information asymmetry that favoured sellers is gone — reputation is crowdsourced.
Companies must co-create with customers: involve them in problem discovery and solution prototyping.
Design thinking enables rapid iteration, essential in a market where customers punish slow, unresponsive products.

The Democratization of Experimentation

Cheap, widely accessible technology has leveled the playing field. A high-quality video can now be shot on a smartphone; the barrier of owning a studio is gone. This shift means small players ("David") can challenge incumbents ("Goliath") who previously held the monopoly on expensive tools.

Key insight: When experimentation is cheap and fast, the power to innovate shifts from large institutions to individuals and small teams.

AI and Learning Through Iteration

Systems like ChatGPT exemplify how massive processing power — once reserved for Microsoft, IBM, or CERN — is now available at negligible cost. The key mechanism is iteration: a user asks a question, receives an imperfect answer, refines the query, and slowly approaches the desired result.

flowchart LR
  A[User query] --> B[AI responds]
  B --> C{Satisfied?}
  C -->|No| A
  C -->|Yes| D[Refined answer]

The computer learns rapidly from the user’s feedback — in minutes, not millennia.
This self‑learning capability lets the system predict and adapt to user needs.

Exaptation: Consumers as Innovators

Exaptation = an unintended application of a technology. When tools spread widely, consumers invent novel uses that the original designers never imagined.

Original technology	Intended use	Unintended (exapted) use
Google Glass	Information access	Homework help (Google Lens)
Instagram	Photo sharing	Branding and cause‑based engagement
TEDx	Local events	Global platform for unknown talent

Consumers today are ruthless — attention span is often 3 seconds.
Mistakes are tolerated; content can be imperfect yet still gain traction if the core idea is compelling.

The Shift from Product Competition to Business Model Competition

Products no longer compete against products; business models compete against business models. Even an inferior product can win if wrapped in a superior business model.

A business model consists of three components:

flowchart LR
  A[Value Generation] --> B[Value Delivery] --> C[Value Appropriation]
  A --> D[Profit]

Value generation – sourcing, manufacturing, processing.
Value delivery – sales, marketing, distribution.
Value appropriation – capturing profit from the value created.

This framework is central to design thinking, which demands a systems view rather than a narrow product focus.

Exam tip: Memorise the three components of a business model (generate, deliver, appropriate). They are the standard lens for analysing disruptive business models.

Case Studies in Business Model Innovation

Netflix — Three Pivots

Phase	Business model	Key shift
1997–2007	Ship DVDs/Blu‑rays by mail	Survived shipping test; replaced VHS tapes
2007–2012	Stream content over the internet	Killed Blockbuster; no physical inventory
2013–present	Produce original content + data‑driven recommendation	Uses analytics to optimise binge‑watching

Netflix’s market capitalisation now exceeds Disney + Marvel + 21st Century Fox + Star Network + Pixar combined — not because its movies are better, but because its business model is stronger.

Tesla — Solving Range Anxiety

Electric cars existed for 150 years.
Tesla’s innovation: free charging for life and battery swapping — embedding the full cost of ownership upfront.
Removes the customer’s fear of charging infrastructure.

Uber / Ola — No Inventory Required

Largest fleet operators without owning a single taxi.
They connect drivers and passengers; the asset (car) belongs to others.

Airbnb — Breaking the Room Barrier

Competed with Marriott / Four Seasons without owning any rooms.
Inventory is knowledge: “where the inventory is”.

Cameras vs. Phones

A dedicated camera can only take snaps.
A smartphone can send, edit, post, make reels — functions that a camera cannot do.
Result: cameras are becoming obsolete despite having superior image quality.

Why Design Thinking Matters Now

Because business models are constantly disrupted and consumers dictate new use cases, organisations must:

Open up their talent value chain — hire freelancers, tap gig communities.
Shift from R&D (Research & Develop) to C&D (Connect & Develop).
Embrace iteration and consumer experimentation as a source of innovation.

Design thinking provides the systems view needed to see beyond a single product and to design a resilient business model.

Key takeaways

Widespread access to experimentation tools empowers consumers and small players to challenge incumbents.
AI systems learn rapidly from user iteration, making prediction and adaptation cheap.
Exaptation — unintended use of technology — is a major source of innovation.
Competition has moved from products to business models (value generation → delivery → appropriation).
Netflix, Tesla, Uber, Airbnb, and the camera/phone battle are classic examples of business model disruption.
Design thinking forces a holistic, systems‑level perspective essential for navigating this new landscape.

Why Design Thinking? Market Shocks and Unpredictability

Markets are inherently unpredictable. Even dominant, near‑monopoly firms can be blindsided by sudden shifts in consumer behavior, technology, or culture. These economic shocks arise from nowhere – shaved heads, beards, home‑based pickle businesses, SUVs, remote work. A company’s survival depends on its reaction: dismiss the trend as temporary, or listen, learn, and adapt. Design thinking provides the mindset to do the latter – defer judgment, empathize, and generate ideas aligned with the new reality.

Illustrative market shocks

Company / Industry	The Shock	Why It Mattered
Gillette (razors)	Bald heads became trendy; beards became a status symbol (e.g., Virat Kohli).	A century‑old shaving monopoly faced a market that no longer wanted to shave. No brand ambassador could reverse the trend.
Hindustan Unilever (HUL)	Patanjali, a domestic brand, grew rapidly with “back‑to‑nature” products.	A giant was shaken by a competitor offering a completely different value proposition – not technological advancement but tradition.
Bajaj (scooters)	In early 2000s, Bajaj decided scooters had no future; disbanded the product line.	Honda’s Activa entered and sold >2 crore units – a unisex, low‑mileage scooter became a hit. Bajaj had misread the market.
Workplaces during COVID‑19	Remote work became feasible and preferred.	Many organizations struggle to bring employees back; the old assumption that “office is required” was shattered.

Two possible reactions to a shock

flowchart LR
  S[Market shock] --> R{How to react?}
  R -->|A – Dismiss| D[“Temporary blip – hold steady to core competence.”]
  R -->|B – Embrace| E[“Train ears and eyes to understand the shift.”]
  D --> O[Risk of being left behind]
  E --> I[Opportunity to innovate]

Reaction A (Dismiss): Assume the trend will pass. Stick to existing products and strengths. Often leads to obsolescence.
Reaction B (Embrace): Suspend judgment, observe deeply, and pivot or adapt. This is where design thinking becomes critical.

Exam tip: The Gillette and Bajaj cases are classic examples of companies that could have dismissed the shock. Gillette still sells razors but missed the beard boom; Bajaj actually abandoned scooters, creating space for Activa. The lecture uses these to show why a design‑thinking mindset is not optional.

Why design thinking fits

Design thinking equips organisations to:

Defer judgment – do not label a trend as “temporary” before exploring it.
Empathize – understand why users are adopting the new behaviour (e.g., why people prefer beards or Activa despite low mileage).
Generate ideas – create products, services, or business models that align with the changed market.
Take a broad canvas – look beyond core competence to see the whole ecosystem.

The pandemic is the most recent proof: remote work was previously seen as inefficient. Companies that embraced it (Reaction B) thrived; those that tried to force a return to the office lost talent.

Key insight: No market cares about a company’s past technology or loyalty. Both customer and employee loyalty are “thin of the past” when the ground shifts. Design thinking is the tool to stay in sync.

Key takeaways

Market shocks are unpredictable – they can come from culture (beards/baldness), new competitors (Patanjali), or technology (UPI, remote work).
Two reactions: dismiss (risky) or embrace (opportunity). Design thinking enables the second.
Gillette, HUL, Bajaj, and the pandemic are real‑world examples of shocks that forced companies to rethink.
Core design thinking practices – defer judgment, empathize, generate ideas – directly counter the “temporary blip” trap.
Loyalty is fragile – markets and employees will move on; constant adaptation is necessary.

Why Design Thinking Now — The Sweet Spot

Design thinking is not a universal replacement for all problem-solving models. Its strength is best understood by contrasting it with three other thinking styles, each suited to a different combination of problem and solution clarity.

The Problem–Solution Matrix

Problems and solutions each fall into one of two categories:

Known problem: The symptom and its root cause are understood (e.g., parking shortage because more cars than spots).
Unknown problem: The cause is unclear; high ambiguity (e.g., why people avoid public transport — reasons vary by city).
Known solution: A ready repertoire of solutions exists; the task is to pick the best one (e.g., dispensing cash at an ATM).
Unknown solution: No off‑the‑shelf solution works; a novel approach is required.

The interaction of these two dimensions defines the appropriate thinking style:

Problem \ Solution	Known Solution	Unknown Solution
Known Problem	Lean Thinking	Lateral Thinking
Unknown Problem	Critical Thinking	Design Thinking

Lean Thinking (Known Problem + Known Solution)

Intuition: When you know exactly what the problem is and exactly what works, the goal is to execute faster and eliminate waste. Lean thinking encompasses methods like Six Sigma, Agile, and Scrum — all aimed at speeding up a perfected process.

Automatable and repetitive (e.g., ATM machines handling cash withdrawals).
Value addition is finite because the task is routine.

Exam tip: Lean thinking only works when ambiguity is minimal. You cannot “cut waste” on a process you haven’t figured out yet.

Critical Thinking (Unknown Problem + Known Solution)

Intuition: You know the solution “menu” exists, but you need to diagnose which exact problem you are facing. Critical thinking drills down from symptoms to root cause.

Tools include Ishikawa diagram, 5 Whys, 5W2H.
Analogy: A doctor does not create a new cure — she maps your unique symptoms to a known disease, then prescribes an existing medication.
Similarly, a teacher uses critical thinking to understand the real intent behind a student’s question.

Exam tip: Be a critical thinker, not a critical person — avoid cynicism or judgment of people.

Lateral Thinking (Known Problem + Unknown Solution)

Intuition: The problem is clear, but no conventional solution works. Lateral thinking (“sideways” thinking) jumps to a non‑obvious, creative approach.

Coined by Edward De Bono.
Resource constraints often force lateral thinking (e.g., Apollo 13).
Worked Example – Maruti Suzuki Factory (1981):
- Problem: Place a 1‑ton machine into a cemented pit without a crane, rollers, or pulleys strong enough.
- Lateral solution: Fill the pit with ice, slide the machine onto the ice, and let it melt overnight — the machine settles perfectly.
- Why it works: The ice provides a low‑friction surface and then disappears, requiring no heavy lifting.

Design Thinking (Unknown Problem + Unknown Solution)

Intuition: When both the problem and the solution are unclear (“wicked problems”), you need a discovery‑heavy approach. Design thinking is like a sledgehammer — used only for highly complex, ambiguous challenges.

Worked Example – The Piano Stairs (Stockholm):
- Problem: People ignored a beautiful staircase in favor of escalators/lifts due to laziness.
- Unknown solution: Make each stair play a musical note when stepped on, turning the staircase into a giant piano.
- Result: People used the stairs voluntarily — a classic nudge (from Richard Thaler’s Nudge).
Design thinking is not the “latest” or “best” model; it is one tool among many (including TRIZ, TOC, Six Thinking Hats, SCAMPER, Blue Ocean Strategy, Inside‑the‑Box Thinking).

The Ambiguity Diagonal

flowchart LR
    A[Lean Thinking] -->|Increasing ambiguity| B[Critical Thinking]
    B -->|Increasing ambiguity| C[Lateral Thinking]
    C -->|Increasing ambiguity| D[Design Thinking]

As problem complexity and discovery demands rise, you shift from lean thinking (lowest ambiguity) through critical and lateral to design thinking (highest ambiguity). A skilled problem‑solver knows all four methods and picks the right one.

Key Takeaways

Lean thinking: known problem + known solution → speed and waste reduction.
Critical thinking: unknown problem + known solution → root‑cause diagnosis.
Lateral thinking: known problem + unknown solution → creative leaps under constraints.
Design thinking: unknown problem + unknown solution → discovery and nudge‑based innovation.
Design thinking is not superior to other models; it is the best choice only for wicked, high‑ambiguity problems.

When to Adopt Design Thinking

Design thinking is costly — it demands time, iteration, and customer access. It is not a universal tool. Apollo 13’s astronauts, for example, could not use it because they had no time; they relied on rehearsed procedures. Design thinking is appropriate only when five conditions hold simultaneously.

The Five Conditions

Condition	Core Idea	Why It Matters
Audacity of goal	The goal must be large and ambitious, warranting the investment.	Small goals (e.g., “make a hole in the wall”) are solved with lean thinking. Elevating the goal (e.g., “make the wall beautiful”) opens up creative possibilities.
Ambiguity of context	The problem space is uncertain, with no obvious solution.	Design thinking is front‑loaded — heavy discovery upfront. If context is clear, there is nothing to discover. Example: getting people in tier‑2/3 cities to wear seatbelts is ambiguous because social norms conflict with safety.
Availability of time	Enough time to explore multiple ideas, dead ends, and about‑turns.	Without time, teams lock onto the first obvious idea. Quality ideas emerge only after 3–4 iterations. Jeff Bezos: senior leaders should focus on 1–2 problems a day.
Access to customers	Direct, continuous validation with the end user at every stage.	Customers define the problem, validate it, and test solutions (“show and tell”). In business, “no surprise is a good surprise” — surprises are rarely welcome.
Diversity of team	Beyond gender: temperamental, generational, ethnic, educational, and perspective diversity.	Diversity leads to slower consensus but richer solutions. Leaders must tolerate difference rather than gravitate toward “relevant experience” teams that produce little creativity.

The Three Lenses of a Winning Idea

Design thinking succeeds when it balances three overlapping criteria:

%%{init: {'theme':'neutral'}}%%
venn diagram
   Human Desirability
   Technical Feasibility
   Business Viability

Human desirability — what people (customers, employees, suppliers) truly desire, often unstated or future‑oriented.
Technical feasibility — what can be delivered within time and budget using available technology.
Business viability — whether the solution makes long‑term business sense (e.g., profitable, sustainable).

A winning idea sits at the intersection. Many rapid‑delivery startups (10‑minute promises) satisfy desirability and feasibility but fail on business viability, leading to failure.

Exam tip: Memorise the five conditions as a checklist: Audacity, Ambiguity, Availability, Access, Diversity. In exam questions, be ready to argue why a given scenario does or does not warrant design thinking — especially if time is scarce or the goal is trivial.

Key takeaways

Design thinking is not a default method; it is high‑cost and only justified when all five conditions are met.
Elevating a problem (e.g., from “hole in wall” to “beautiful wall”) reveals audacious goals and unlocks more solutions.
Ambiguity and time are essential for genuine discovery; without them, lean thinking suffices.
Customers must co‑create at every step — surprises are unwelcome in business.
Team diversity (beyond gender) fuels creativity but requires deliberate leadership to tolerate slower convergence.
A great solution must satisfy human desirability, technical feasibility, and business viability simultaneously.

Key Tenets of Design Thinking – Part I

Design thinking rests on a set of core principles. This section covers the first three of fourteen tenets.

1. Human-centricity: Bring the human to the centre, not the product

Intuition: Most organisations are product‑centric, profit‑centric, or regulator‑centric. Human‑centricity means designing for the actual people who will use the solution — including children, the elderly, and people with disabilities — not for a policy or a quarterly target.

Examples of missing human‑centricity:

Airline safety demonstrations – The crew rattles off emergency‑exit instructions in under a minute; passengers nod without truly understanding. The behaviour is driven by regulatory compliance, not by making sure a passenger can actually open the exit under stress.

Examples of human‑centricity:

Singapore’s public transport – Designed for all users: children, the elderly, wheelchair users, non‑English speakers. The system is so intuitive and connected that even a first‑time visitor can navigate it easily, leading to one of the highest public‑transport adoption rates in the world.
Children using public transport in Japan – Five‑year‑olds travel alone by subway or bullet train because the system is built around their needs. A genuine test of human‑centricity: give the product or service to a child. If a child can use it without a manual, it is truly human‑centred.

2. Design thinking is about thinking, not design

Intuition: The term “design thinking” is a misnomer. It does not mean “thinking about what to design”; it means designing your own thinking. Yet no school subject ever taught us how to think systematically — we were just expected to pick it up. Thinking without a model leads to overthinking, not better thinking.

Example – Tata Nano:

Genesis: Ratan Tata saw a family of four struggling on a motorbike in the rain and wanted to give them a safe, affordable car. The project aimed for a ₹1‑lakh car.
Outcome: The car was built, but nobody bought it.
Root cause: The team focused on designing the cheapest car possible (product focus) instead of thinking about the customer’s real priorities. The starting point was sympathy (“they need a car”) rather than empathy (“what do they actually need?”). Possible priorities: parking space, daughter’s marriage, children’s education, a bigger house. A car may come later — and certainly not a car perceived as “cheap.” The product promise (affordability) clashed with product aspiration (pride of ownership).

Exam tip: The Tata Nano case is a classic trap: a technically brilliant product fails because the designers skipped empathy and built from sympathy. Design thinking demands that you first think about the human — not just design a thing.

3. Focus on the subject, not the object

Intuition: This tenet is closely related to human‑centricity. Instead of obsessing over the artefact (the object), focus on the person who needs it (the subject) and their underlying need.

Example – Baby incubator vs. Embrace Baby Warmer:

The problem: Many underweight newborns die in the first 24 hours. Incubators save lives, but the ones donated to Indian government hospitals are often unused.
Why? They require continuous electricity, oxygen, air‑conditioning, trained staff, and specialised maintenance. They are over‑engineered for the Western context and unsuitable for rural India.
The human‑centred shift: Ask not “How do we make a cheaper incubator?” but “What does the baby actually need?” The answer is warmth — and warmth doesn’t require an incubator. The Embrace Baby Warmer (developed at Stanford’s d.school) is a simple, low‑cost quilt that maintains temperature without electricity, allows the mother to hold the baby skin‑to‑skin, and is easy to clean and reuse. The solution reframes the problem from the object (incubator) to the subject (baby).

Key takeaways

Human‑centricity means designing for actual people, not for regulations, profits, or products. The ultimate test: can a child use it without instruction?
Design thinking is about thinking, not designing. It is a systematic way to improve how you think — moving from sympathy to empathy.
Focus on the subject, not the object. Ask what the human truly needs (e.g., warmth, not an incubator) and work backward from that need.
The three tenets are interconnected: all demand that the human being remains at the centre of every decision.

1. Solve Problems With the Customer (Not For Them)

Traditional problem solving: solve for the customer — the expert delivers a finished solution.
Design Thinking: solve with the customer — collaborate throughout, even with a half-baked product. This requires courage and humility from both sides: the designer admits “I don’t have all the answers” and the customer admits “I may not fully understand my problem.”

Work with lead users — advanced customers who understand the problem and can co-create the solution.

Example: The Mirror Box (V.S. Ramachandran)
Phantom limb pain: amputees feel excruciating pain in a missing limb. Traditional route: brain surgery (risky, complex). Ramachandran’s solution: a $10 mirror box. The patient places the intact limb in one compartment and the phantom limb in the other. The mirror reflection “fools” the brain into seeing the missing limb move. Coordinated movement of both limbs relieves the pain permanently. This is solving with the patient (in neurosurgery patients are awake and talking) — radical, low-cost, and unprecedented.

Key takeaway: Collaborating with the customer, not just delivering to them, unlocks elegant, low-cost solutions that surgery or conventional methods cannot match.

2. Think Beyond the Product

Products are not ends in themselves. Successful companies think from the customer backward — what else does the customer need to complete their journey?

Company	Beyond the core product	Full experience offered
Royal Enfield	Motorcycle	Helmets, guards, kneecaps, gloves, riding gear – a lifestyle ownership
Asian Paints	Paint	Certified applicators, colour counselling, interior design services – a home-making company

Key takeaway: “Make a better mousetrap and the world will beat a path to your door” rarely works. Think of the whole ecosystem around your product.

3. Balance Desirability, Feasibility, and Viability

Every innovation must satisfy three overlapping criteria:

Desirability – What do humans need?
Feasibility – Is it technically possible?
Viability – Does it make business sense?

Examples of companies that nailed all three:

BigBasket – Desirability: choose exact delivery slot, no secondary packaging, private label (Royal), fresh produce. Feasibility: deep analytics, gradual city expansion. Viability: profitable throughout, acquired by Tata.
DMart – Desirability: narrow range, deep discounts. Feasibility: own land (no rental cost), disciplined vendor payments. Viability: profitable for 24 years, only profitable brick‑and‑mortar retailer in India.
IndiGo – Desirability: low fares, punctuality. Feasibility: tight operations, single aircraft type. Viability: profitable every quarter except pandemic – unlike Deccan, Kingfisher, Jet Airways who lost balance on one dimension.

flowchart LR
    A[Desirability] -- Human need --> B[Innovation]
    C[Feasibility] -- Technical possibility --> B
    D[Viability] -- Business sense --> B

Key takeaway: If any one dimension is missing, the innovation fails. Startups in Bangalore (BigBasket) and disciplined retailers (DMart, IndiGo) show that tight alignment produces sustained profitability.

4. Diverge Before Converge

Divergent thinking ≠ convergent thinking.

Divergent: generate many answers (creativity).
Convergent: select the right answer (intelligence).

Most people jump from one problem to one solution (pattern mapping). Design Thinking demands: quantity over quality first, then narrow down.

Divergent	Convergent
Goal: increase options	Goal: reduce options
Defer judgement	Evaluate and select
Combines unrelated ideas	Tests feasibility

Example: Paper + glue = ordinary; combine them → Post‑it Note. Plastic + glue = ordinary; combine → Cello tape. Innovation comes from recombining ideas from different domains.

Exercise: “Give 20 ways to empty a glass of water without breaking it.” Generating 20 is harder than choosing the best from a list. Hence divergent thinking is the rarer skill.

Key takeaway: Always diverge first (generate many ideas, defer judgment), converge later (choose the best). Do not skip to the solution.

5. Compartmentalize Thinking: Explore, Generate, Validate

Separate the process into three spatially, mentally, and temporarily distinct compartments:

Problem Exploration – Spend time with the problem. Do not generate solutions. Defer judgment. Go deeper into what the problem really is.
Solution Generation – Generate multiple ideas (individual and group). Do not evaluate any idea during this stage; build a “bookie” of ideas. Avoid shooting down ideas (“yes, and” instead of “yes, but”).
Idea Validation – Pick ideas one by one and test them against reality.

flowchart LR
    A[Problem Exploration] --> B[Solution Generation]
    B --> C[Idea Validation]
    style A fill:#e1f5fe,stroke:#01579b
    style B fill:#fff9c4,stroke:#fbc02d
    style C fill:#c8e6c9,stroke:#2e7d32

Exam tip: The most common mistake is to evaluate and generate simultaneously. Resist. Keep compartments separate – especially during brainstorming sessions.

Key takeaway: Three sequential steps – explore the problem, generate many solutions, then validate. Never jump straight to solution.

6. From Symptoms → Problems → Root Causes

What appears to be the problem is usually only a symptom. A good designer (like a good doctor) digs deeper.

Symptom – Surface‑level manifestation (e.g., Bangalore traffic, headache, fever).
Problem – The underlying condition (e.g., poor urban planning, diabetes).
Root cause(s) – The fundamental drivers (e.g., lifestyle, genetics, infection – often multiple, not one).

Example: Diabetes

Symptoms: constant thirst, frequent urination, sore feet, vision loss, hunger.
Problem: diabetes.
Root causes: lifestyle, food allergies, renal infection, genetics – determined via diagnostics (blood sugar tests, history).

Application in design: When faced with a user issue, do not stop at the symptom. Use interviews, observations, and data to uncover the true root causes. Only then generate solutions.

Key takeaway: “Symptoms → problems → root causes” is a funnel. Stay at the symptom level and you will solve the wrong thing. Always push to root causes.

Overall Key Takeaways – Part II & III

Solve with the customer, not for them – requires courage and humility.
Think beyond the product to the full customer experience.
Every innovation must balance desirability, feasibility, and viability.
Diverge first (quantity over quality), then converge – separate idea generation from evaluation.
Compartmentalize: explore problems, generate ideas, validate – never mix.
Always dig from symptoms to problems to root causes; surface‑level fixes are temporary.

1. Minimalism: Emphasize “What Less”, Not “What Else”

Intuition: Engineers tend to add features; design thinking strips away complexity. The goal is not to ask “what else can I add?” but “what can I remove?”. This is the essence of minimalism (Steve Jobs’ approach).

The FAB Model

To distinguish between features and real value, use the FAB model:

Features: All the technical capabilities of a product (e.g., hundreds of buttons on a VCR remote).
Advantages: How the product is superior to competitors or alternatives.
Benefits: The actual value the consumer derives.

More features do not automatically lead to more benefits. Products with fewer features can be more robust and deliver greater benefits.

Examples from the lecture:

Product	Features	Outcome
VCR remote	Hundreds of buttons (over-engineered)	Customer confusion
Amazon Fire TV stick remote	Only 7–8 buttons (minimal)	Every button used, simple experience
Pencil	One function – writing	Unchanged for centuries, still in every household
Safety pin	One function – fastening	Design unchanged for over 100 years

Exam tip: The pencil and safety pin are classic examples of products that do one thing extremely well – a core design thinking principle. Memorise them for essays.

Quote from Lao Tzu: “To gain knowledge, add something daily. To gain wisdom, remove something daily.”

Key takeaways

Design thinking is about subtraction, not addition.
FAB model: Features ≠ Benefits; less can be more.
Classic examples: VCR remote (bad) vs. Fire TV remote / pencil / safety pin (good).
Practice minimalism in life and design: ask “what can I remove?”

2. Think with Your Hands

The human hand and brain co-evolved. The opposable thumb (an evolutionary accident) enables grasping and tool use. To make your mind work effectively, use your hands. Avoid only talking about a problem (“Indians think with mouth,” per the lecture); instead, get your hands dirty.

Activities that engage the hands:

Cooking, gardening, painting, moulding, sculpturing, sketching, playing a musical instrument.

Playing an instrument uses both hands simultaneously (ambidexterity), which strengthens the corpus callosum – the bridge between the left and right brain hemispheres.

Example: Albert Einstein’s brain had a thicker corpus callosum than average, attributed to his daily violin practice (2 hours). He said, “If I was not a physicist, I would have been a musician.”

Key takeaways

Hands-on activity drives clearer thinking.
Bimanual tasks (e.g., playing instruments) enhance brain connectivity.
Practice thinking with your hands: take up a hobby that involves fine motor skills.

3. Sell the Problem Before the Solution

A presentation gets hijacked when the problem doesn’t feel urgent. If the problem isn’t important, the solution can never be. Therefore, first sell the problem with powerful storytelling.

The SCQA Framework (Barbara Minto, McKinsey)

Letter	Meaning	Description
S	Situation	The stable background fact.
C	Complication	Why the situation now demands attention – a disruption, gap, or tension.
Q	Question	The central question that emerges from the complication.
A	Answer	The proposed solution or recommendation.

Worked example – Getting employees back to office:

Situation: After the pandemic, companies allowed work-from-home, and many continued.
Complication: Lack of cultural integrity, creativity, collaboration, and performance slack.
Question: How to bring employees back without dampening morale?
Answer: (1) Roster teams for specific office days; (2) Offer facilities (good food, creche); (3) Incentivise regular attendance.

Exam tip: The SCQA structure is a powerful storytelling tool for any business case. Practice framing a problem using the four steps in under 2 minutes.

Key takeaways

Always make the problem feel important before pitching your solution.
SCQA = Situation → Complication → Question → Answer.
Use storytelling; stories stick better than concepts.

4. Visual Thinking – Draw Your Ideas

Design thinking workshops are highly visual: colours, sketchpens, stickies, doodles, Play-Doh, Lego. This is visual thinking – externalising ideas openly for scrutiny.

Comparing three ways of ideation:

Mode	Characteristics
Speaking	Cheap, leads to argument
Writing	Requires some thought, but still shallow
Drawing	Forces detail, clarity for self and others, evolves the idea, invites collaboration

Verdict: Drawing (sketching) is the most powerful because it forces precision, makes the idea tangible, and encourages real-time iteration with the team.

Key takeaways

Think out loud by putting your ideas on paper – don’t keep them private.
Sketching > writing > speaking for clarity and collaboration.
Use visual materials (colours, sticky notes) to externalise thinking.

5. Fail Often to Succeed Sooner

Six Sigma aims for “right first time”. Design thinking aims for “wrong first time, wrong second time, wrong third time, maybe right fourth time.” Innovation inevitably involves failure.

Examples from the lecture:

Saturn V rocket (Apollo 11) had a 40% failure rate.
SpaceX: First three launches failed; only the fourth succeeded with limited resources.

Why failure is okay:

People’s memory is short – they forget both success and failure.
Regret comes from things not tried, not from failed attempts.
The best teacher is personal experience.

Rapid iterative model: Maximise the number of tryouts per dollar and per hour to increase learning.

Nature’s analogy – evolution through mutation: Most mutations fail; those that fit the environment survive. 99.99% of all species have gone extinct. The human species survives because we keep evolving through trial and error.

flowchart LR
    Try --> Fail
    Fail --> Learn
    Learn --> Try
    Try --> Succeed

Key takeaways

Design thinking embraces failure as a learning tool.
Fail often and fast to succeed sooner.
Maximise experiments per unit of time or money (“learning per dollar”).
Failure is not final; it’s a step towards fitness (like natural selection).