Product Thinking

In a world driven by rapid iteration, customer obsession, and market dynamics, product thinking is emerging as a vital discipline. It’s not just about building what people ask for—it’s about uncovering what truly matters, designing with intention, and scaling with purpose.

What is Product Thinking?

Product thinking is a mindset that centers around solving the right problem in the right way, with a clear focus on delivering value to users and businesses alike. It’s about asking not just “What should we build?” but “Why are we building this?” — and doing so with enough rigor to resist being swept away by the never-ending tide of feature requests.

Great product thinkers operate at the intersection of empathy, strategy, and execution. They balance business needs, user problems, and technical feasibility, always keeping sight of long-term impact.

Enterprise Sales vs. Product-Led Growth: a clash of mindsets

The tension between sales-driven enterprise models and product-led growth (PLG) models highlights the importance of product thinking.

In enterprise sales, the customer often wields enormous influence:

• Large deals can shape product roadmaps.
• Sales cycles are long, and bespoke features are frequently used to close deals.
• Success is often measured in ARR and deal size, even if product complexity increases.

In this world, the product team risks becoming a custom development shop, building features tailored to one customer at the expense of the broader user base.

In PLG, the product is the sales engine:

• Value is delivered upfront, often with a freemium model.
• Features are released based on usage data and validated learning.
• The focus is on scalability, virality, and adoption.

PLG demands a more disciplined approach to prioritization. You can’t afford to say yes to every user request — you must synthesize signals, test hypotheses, and build features that scale.

“Fall in love with the problem, not the solution.” — Uri Levine, co-founder of Waze

Whether PLG or enterprise, this mantra applies universally. True product thinking requires stepping back from individual feature requests and re-centering on the core problem. Why does the user need this? What are they trying to achieve?

The Double Diamond: diverge, then converge

One of the most powerful tools for applying product thinking is the Double Diamond framework from the British Design Council. It describes the creative process in four phases:

• Discover – Understand the problem space deeply. Talk to users. Map their workflows. Identify pain.
• Define – Narrow in on the most important problems to solve.
• Develop – Ideate and prototype possible solutions.
• Deliver – Build, test, and iterate based on feedback.

This process embraces divergent thinking to explore widely, followed by convergent thinking to focus sharply. It encourages curiosity and clarity in equal measure — two hallmarks of great product teams.

The Essence of the Double Diamond - by Mastering UX

Avoiding the feature factory trap

The challenge in both enterprise and PLG environments is the same: how do you avoid being overwhelmed by customer requests?

Here’s where the Lean Startup principles by Eric Ries shine. Rather than over-investing in fully built features upfront, lean thinking encourages:

• Validated learning through MVPs and experiments
• Build-Measure-Learn cycles
• Continuous deployment and usage tracking

Customer input is vital—but it must be contextualized. Instead of blindly acting on feedback, product thinkers ask:

• Is this problem widespread?
• What’s the underlying unmet need?
• How does this align with our product vision?

The pencil and the invisible hand

In his famous lecture, economist Milton Friedman uses the humble pencil to illustrate the power of the free market: no single person knows how to make a pencil, yet the market coordinates vast networks of suppliers, manufacturers, and distributors to produce one.

The Power of the Free Market - The Pencil Lecture by Milton Friedman

Similarly, great products are rarely the result of a single customer’s request. They are born from market insight, user empathy, and strategic synthesis. Like the pencil, a well-designed product draws from countless invisible contributions: support tickets, behavioral data, sales objections, UX research, and technical constraints.

The product thinker doesn’t just collect feedback—they connect the dots.

Product thinking in action

Let’s make it concrete. Imagine you’re a product manager for a B2B video platform. A major client demands a custom workflow for compliance approval. Sales pressures you: “This is a $500K deal — we have to build it.”

A product thinker doesn’t say yes or no outright. Instead, they:

• Investigate whether other customers have similar needs.
• Look for the problem behind the request: is it really about compliance, or about workflow transparency?
• Prototype a generalized solution (e.g., customizable approval flows) that could benefit the entire customer base.
• Prioritize based on strategic fit and expected ROI.

In this approach, you’re falling in love with the problem, not the deal.

Falling in love with the problem by Uri Levine

Closing thoughts

Product thinking is hard because it demands clarity in ambiguity, discipline in chaos, and empathy in business. But it’s also what transforms good products into great ones — and good companies into category leaders.

To thrive as a product thinker:

• Embrace discovery. Don’t skip straight to solutions.
• Balance input with vision. Customers are experts in their problems, not your product.
• Say no, with context. Not every request deserves to be built.
• Design for scale. Build once, benefit many.

The market, like the pencil, rewards those who think beyond the immediate. Because when you truly fall in love with the problem, you begin to create products that the market didn’t even know it needed.

"The Power of the Free Market" by Free to choose "Falling in love with the problem" video by Web Summit.