Same Scenario, Different Thinkings

Improving user experience requires more than just good intentions. The trap is to treat problem-solving as a single mode of thought. The actual job is to apply the right kind of thinking at the right time, depending on the problem's nature and context.

This lesson walks through a single scenario — a PM tasked with improving a mobile app's user experience — and shows how different thinking modes shape very different approaches and outcomes.

Creative thinking generates original ideas, but it is only the start

Creative thinking is about coming up with new and original ideas. It is the spark of innovation.

Imagine you are the PM on a new mobile app. You might brainstorm features like gamification, social sharing, or personalized onboarding flows. You are pushing past the obvious, looking for ways to delight users in unexpected ways.

But creative thinking is not just random ideation. It is structured imagination. You consider what has worked elsewhere, what is feasible, and what aligns with your users’ needs.

Creative thinking here is about expanding the solution space. You want to see all the possible avenues before narrowing down.

Lateral thinking reframes problems and finds connections others miss

Lateral thinking means stepping sideways from the obvious path. Instead of improving the existing onboarding flow, you might look at how other apps engage users or how users actually behave.

You might dig into user feedback and discover many abandon the app because they don’t understand the value proposition. Or that users prefer sharing progress with friends to stay motivated.

This mode asks: What if we change the frame? What if we challenge assumptions?

Lateral thinking often involves techniques like looking at analogous problems, reversing assumptions, or combining unrelated ideas. It helps you avoid tunnel vision.

Strategic thinking aligns actions with business goals and constraints

Strategic thinking is about planning and prioritization. Improving UX is not just about features; it’s about impact and resources.

You map out a plan: conduct user research, prototype changes, run A/B tests, and measure results. You align with marketing and engineering to ensure the roadmap supports business objectives.

Strategy asks: What will move the needle? What can we realistically do next quarter?

Without strategy, creative and lateral ideas remain disconnected. Strategy grounds ideas in measurable outcomes and real-world constraints.

Systems thinking sees the app in the context of a larger ecosystem

Systems thinking means understanding the app as part of a broader system — the product portfolio, company goals, user workflows, and technology stack.

You ask: how will changes to onboarding affect retention, support load, or marketing campaigns? What dependencies exist between teams? How does this fit into the overall product roadmap?

This holistic view prevents local optimizations from creating global problems.

Systems thinking also helps you anticipate unintended consequences and plan mitigation.

Problem-solving narrows down issues and generates practical fixes

Problem-solving is about diagnosing specific issues and applying targeted solutions.

You analyze analytics and find users drop off mostly on the payment setup screen. You run usability tests and discover confusion about payment methods.

You decide to redesign the payment UI and add help tooltips. You track if this reduces drop-off.

Problem-solving is tactical and diagnostic. It answers: What exactly is broken? How do we fix it?

Problem-solving is essential but incomplete on its own. You need other thinking styles to decide what problems to solve and how.

Decision-making weighs options and chooses the best path forward

Decision-making involves evaluating alternatives against criteria like cost, impact, feasibility, and risk.

You have five potential UX improvements but limited resources. You score each by expected user impact, engineering effort, and alignment with strategy.

You prioritize the payment UI redesign and simplified onboarding over less urgent features.

Decision-making is about trade-offs and commitment.

Without clear decisions, teams waste time on low-impact work or get stuck in endless debates.

Divergent thinking expands possibilities before narrowing focus

Divergent thinking generates many ideas and options without judgment.

In a brainstorming session, you encourage the team to suggest any and all ideas for improving UX — from radical redesigns to small tweaks.

This floods the solution space with possibilities.

Later, you use convergent thinking to evaluate and select the best ideas.

Convergent thinking evaluates and combines ideas into a coherent plan

Convergent thinking filters and refines ideas.

You weigh the pros and cons of each onboarding improvement. You combine the chatbot guide with a progress bar but defer the referral reward for later.

This leads to a focused, actionable plan.

Convergent thinking brings clarity and focus after divergent exploration.

Field Exercise: Apply different thinking styles to your own product challenge

1. Pick a product or feature you are working on.
2. Use creative thinking to brainstorm at least five new ideas or features without judgment.
3. Apply lateral thinking by reframing the problem or looking at it from a different perspective. What assumptions can you challenge?
4. Develop a strategic plan for what you will build and when, aligned with your business goals.
5. Use systems thinking to map dependencies and impacts beyond your feature.
6. Identify a specific problem to solve using problem-solving techniques.
7. Make a decision on the top priority based on effort and impact.
8. Reflect on moments you used divergent and convergent thinking during this process.

Spend 15–20 minutes writing your responses. This exercise will deepen your understanding of how to apply these thinking styles in practice.

Test yourself: Prioritizing UX improvements at a Series A startup in Bangalore

Where to go next

• If you want to deepen your problem-solving toolkit: Problem Solving Frameworks
• If you want to master user research techniques: User Research Methods
• If you want to learn prioritization frameworks: Prioritization Techniques
• If you want to build strategic thinking skills: Product Vision and Strategy