Design Thinking and Idea Generation for Product Managers

Design thinking is the foundation of problem-solving in product management. It is the mindset that keeps you focused on the user, the context, and the real pain points — not just the shiny features or the latest tech buzz. The trap is treating design thinking as a checklist or a jargon term. The actual job is to develop empathy and curiosity for your users, so you can discover problems worth solving.

Most aspiring PMs rush to solution mode. They want to build features, wireframes, and prototypes before fully understanding the problem. This leads to wasted effort and products nobody wants. The cleanest way to think about design thinking: it starts with identifying unmet needs and ends with ideas that address those needs in a feasible and impactful way.

Indian product teams often face unique challenges — diverse languages, varying literacy levels, and complex user contexts. Design thinking helps you navigate these complexities by centering your work on real human experiences.

Cultivating a problem-solving mindset

The first step in design thinking is to develop a habit of noticing problems in your daily life and work. This is not about grand ideas. It is about paying attention.

One practical exercise is the Daily Annoyance Diary: every day, write down moments when something frustrates you or a user. It can be as simple as a confusing app flow or a delivery delay. The key is to capture what you were trying to do, why the current solution failed, and what a better solution might look like.

This exercise trains you to see opportunities everywhere and begins the process of shifting from passive user to active problem finder.

Identifying unmet needs with structured research

Once you have a list of annoyances, the next step is to dig deeper into unmet needs. This requires structured research — user interviews, observations, and contextual inquiry.

One method is the Needs Identification Worksheet: document scenarios across different contexts, note what users are trying to achieve, and why existing solutions fall short. This worksheet encourages you to think broadly and avoid jumping to solutions prematurely.

Indian contexts demand special care here. For example, a delivery app user in Mumbai might have different pain points than one in a tier-3 city due to infrastructure, language, or payment preferences. Your research design must capture these nuances.

Ideation: generating ideas with proven techniques

With a clear understanding of unmet needs, you can begin ideation — generating ideas to address those needs. The challenge is to produce a wide range of ideas before narrowing down.

Here are some ideation techniques that work well in practice:

• Mind Mapping: Start with a central problem or theme and branch out related ideas. Use colors and visuals to organize thoughts. This helps you see connections and explore unexpected directions.

• SCAMPER: This acronym stands for Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse. Apply each prompt to your idea to generate variations. For instance, can you substitute a manual process with automation? Can you combine two features into one?

• Rapid Ideation: Set a timer (e.g., 10 minutes) and write down as many ideas as possible without judgment. The goal is quantity, not quality. This breaks mental blocks and surfaces surprising concepts.

• Brainwriting (6-3-5 method): Individually write 3 ideas in 5 minutes, then pass them on for others to build upon. Repeat for 6 rounds. This method encourages collaboration and incremental refinement.

• Why-How Laddering: Alternate between asking “Why?” to understand the purpose behind an idea and “How?” to explore implementation. This deepens your understanding and reveals assumptions to test.

• Starbursting: Focus on generating questions around an idea instead of answers. Who, what, where, when, why, and how questions help identify risks and unknowns early.

These techniques are not theoretical; they are used by product teams in India and globally to unlock creativity and avoid the trap of the “first obvious solution.”

Refining and prioritizing ideas through convergent thinking

After divergent ideation, you must shift to convergent thinking: grouping related ideas, identifying patterns, and selecting the most promising ones.

This step involves evaluating ideas for feasibility, impact, and alignment with business goals. Use criteria such as user value, technical complexity, cost, and strategic fit.

In practice, Indian startups often use collaborative tools like Miro to visualize ideas and enable team discussions. This transparency helps build consensus and surface hidden concerns.

Prototyping and early validation

Design thinking does not end with idea generation. The next phase is to prototype and test your ideas quickly to gather feedback.

Prototypes can be low-fidelity sketches, wireframes, or clickable mockups. The goal is to validate assumptions and learn what works before investing heavily in development.

Indian companies like Razorpay and Swiggy have embraced rapid prototyping to iterate on user flows and payment experiences, reducing time to market and improving adoption.

Design thinking frameworks and tools for PMs

Here is a selection of frameworks and tools that support design thinking in product management:

Inclusive design and diversity considerations

Design thinking must be inclusive. India’s diversity in language, culture, literacy, and ability requires thoughtful design.

Inclusive design means creating products usable by the widest range of people, not just the average user. Accessibility focuses on disabilities, while inclusivity covers broader differences such as language proficiency and cultural norms.

Ask yourself:

• Who might be excluded by this design?
• What assumptions am I making about user capabilities or context?
• How can I test with diverse user groups?

Inclusivity is a critical success factor for products serving India’s vast and varied population.

From the field: How I teach design thinking at Pragmatic Leaders

When I teach design thinking, I start with simple exercises like the Daily Annoyance Diary. Students often realize they have ignored everyday frustrations that could be great problem opportunities.

Next, I introduce ideation techniques like SCAMPER and mind mapping. Many learners find SCAMPER surprisingly powerful — it forces you to look at a problem from multiple angles.

Finally, I emphasize the discipline of convergent thinking and early validation. It is easy to get stuck in endless brainstorming or to jump to solutions without testing. The best PMs know when to say “enough” and start building a prototype.

Field exercise: Practice design thinking in 30 minutes

1. Spend 10 minutes on the Daily Annoyance Diary. Note down 3 frustrations you or people around you experienced today.

2. For each frustration, write down the unmet need behind it. What was the user trying to achieve? Why did the current solution fail?

3. Use the SCAMPER technique on one unmet need. Apply each letter’s prompt to generate at least one new idea.

4. Select the top 2 ideas. For each, sketch a rough concept or user flow on paper or a whiteboard.

5. Reflect: Which idea feels most impactful and feasible? What assumptions will you test first?

Test yourself: Prioritizing ideas in a consumer payments app

Where to go next

• If you want to master user research and discovery: User Research Methods
• If you want to learn how to translate insights into product vision: Product Vision and Strategy
• If you want to practice rapid prototyping and validation: Design Sprints and Prototyping
• If you want to deepen your understanding of inclusive design: Inclusive and Accessible Design
• If you want to build a portfolio of product ideas: Building Your PM Portfolio