Customers rarely describe their deepest needs in neat, survey-ready sentences. They may request a faster app when they actually want reassurance, ask for a cheaper product when status matters just as much as price, or abandon a service without explaining the obstacle. This gap between what people say and what they value is where design thinking becomes useful.
Design thinking is a human-centred approach to solving problems. It begins by understanding people—their circumstances, emotions, habits and constraints—before deciding what to build. It then seeks a balance among three questions: Is the solution desirable to users? Is it feasible to create? Is it viable for the organisation? Starting with desirability prevents teams from polishing an idea that nobody genuinely wants. The approach is especially relevant in India. Language, income, digital confidence, geography and social expectations can transform the same need into very different experiences. An urban professional ordering dinner and a small-town merchant receiving a digital payment may use the same smartphone, yet face entirely different pressures.
Through observation, clear problem definition, collaborative ideation, rapid prototyping and repeated testing, design thinking replaces assumptions with evidence. More importantly, it treats audience understanding not as a one-time research exercise, but as an ongoing conversation.
1. Observe lives, not merely survey answers: Empathy begins where the audience actually makes decisions: homes, shops, stations and phone screens. Interviews reveal stories, while observation reveals workarounds, hesitation and unspoken frustration. Asian Paints’ move beyond selling paint towards colour guidance and end-to-end home-painting services illustrates this principle. A homeowner may not simply need a colour tin; they may need confidence about shades, contractors, disruption and the finished result. Seeing the complete situation reveals a larger opportunity than a product questionnaire can.
2. Listen for emotions behind functional requests: A request often contains an emotional job. The Tata Nano is a valuable cautionary example: affordability and engineering ingenuity did not automatically create aspiration. Its “cheapest car” positioning was widely seen as a possible mismatch with buyers who associated car ownership with dignity and progress. Design thinking asks what a purchase means to people, not only what specifications they accept. This distinction helps brands avoid solving the practical problem while weakening the emotional reward.
3. Turn research into a precise human problem: Teams must synthesise interviews and observations into personas, journey maps and empathy maps. These tools organise what people say, think, do and feel across an experience. For a Swiggy customer, “late delivery” may be too broad a problem. A clearer definition could be: “A parent ordering after work needs dependable timing because the family is hungry, but uncertain updates create stress.” That framing gives designers a specific human outcome to improve: confidence, not simply speed.
4. Include every person who shapes the experience: The audience is rarely limited to the final buyer. A food-delivery experience involves customers, restaurant staff and delivery partners. A Jaipur Rugs product connects artisans, local communities, designers and buyers. Jaipur Rugs’ artisan-centred model demonstrates how understanding makers’ skills and aspirations can create distinctive products as well as livelihoods. Stakeholder mapping prevents a convenient solution for one group from transferring extra effort or risk to another.
5. Replace assumptions with “How might we?” questions: Once the need is clear, an open question invites possibilities without prescribing an answer. Instead of “Add another payment button,” a team might ask, “How might we reassure a shopkeeper immediately that payment has arrived?” That question focuses on the desired outcome and leaves room for visual confirmation, audio alerts or simpler records. Payment soundboxes used by brands such as Paytm and PhonePe illustrate how designing around noisy shops, divided attention and trust can produce a more relevant answer than adding screen features alone.
6. Generate ideas through diverse perspectives: Audience understanding improves when researchers, designers, engineers, sales teams and frontline employees work together. Each notices different constraints. For an IRCTC booking journey, a technologist may focus on system performance, while a traveller may worry about seat availability, payment uncertainty or unfamiliar terminology. Combining perspectives produces ideas grounded in both lived experience and delivery reality. It also helps teams test desirability, feasibility and viability together rather than handing problems between isolated departments.
7. Prototype before investing heavily: A prototype can be a paper screen, a sample service script, a clickable mock-up or a trial in one neighbourhood. Its purpose is learning, not presentation. If Zomato were exploring a clearer group-ordering journey, a simple mock-up could reveal whether people understand invitations, budgets and shared carts before a full release. Early prototypes make disagreement visible, expose confusing assumptions and reduce the cost of changing direction.
8. Test behaviour, not politeness: People often praise an idea in an interview yet struggle to use it. Testing asks participants to complete realistic tasks while the team watches where they pause, backtrack or seek help. Consider a multilingual UPI payment flow: success is not the user saying it looks simple; success is completing a payment confidently and recognising its status. Follow-up questions can uncover confusion, but observed behaviour provides the stronger evidence.
9. Design for India’s diversity, not an imaginary average: Averages hide important barriers. Older adults, first-time internet users, people with disabilities and speakers of regional languages may encounter very different obstacles. Inclusive testing can reveal whether instructions are understandable, touch targets are usable and error recovery is reassuring. Indian apps that offer vernacular interfaces demonstrate the value of meeting people in familiar language. Inclusion is not an optional courtesy; it expands relevance and often improves clarity for everyone.
10. Treat feedback as a loop, not a verdict: Design thinking is iterative: empathise, define, ideate, prototype and test—then return wherever new evidence leads. A failed test does not necessarily mean the idea is useless; it may expose the wrong problem definition. Amul’s long-running topical communication shows the broader value of staying attentive to changing public conversations. Brands remain relevant when they keep listening, learning and adapting instead of treating past audience knowledge as permanent.
Key Takeaways:-
1. Observe real behaviour to uncover needs that customers cannot easily articulate.
2. Balance human desirability with technical feasibility and sustainable business value.
3. Prototype, test and iterate before assumptions become expensive commitments.
Design thinking helps organisations understand audiences by changing the order in which innovation happens. Rather than beginning with technology, a sales target or a favoured idea, it begins with people. Observation and open interviews reveal context; personas and journey maps clarify the problem; collaborative ideation broadens the possibilities; prototypes make ideas testable; and real-world feedback corrects assumptions. Indian examples make one lesson particularly clear: usefulness alone is not enough. A service must account for trust, aspiration, language, family routines, digital confidence and the conditions in which it will be used. The strongest solution is desirable for people, feasible to deliver and viable over time.
This process does more than improve products. It reduces the risk of expensive misjudgements, gives teams a shared view of the customer and builds loyalty by addressing genuine friction. Most importantly, it creates organisational humility. Businesses stop treating the audience as a demographic to persuade and start treating people as partners in discovery. You may never predict every customer preference. But when you observe carefully, frame the right problem and keep testing your understanding, you can build something far more valuable than the next big idea: a solution that earns a place in people’s lives.
