What Is Product Thinking? A Product Manager’s Insight

Product sense (Product Thinking) matters more than ever in Silicon Valley. It isn’t a specific skill like prototyping or writing specs; it’s a way of viewing the world.

Just as learning photography teaches you to observe light, composition, and moments, product thinking teaches you to observe users, understand contexts, and spot opportunities.

One product manager habitually watches restaurant staff take orders, customers wait, and kitchen workflows, then sketches flowcharts at home to train his systems thinking.

The core of product thinking is to start from user value, work backwards to understand the whole system, and only then define concrete features. Many reverse the order—designing features first, then trying to find a user need—resulting in products that only impress the creators, not the market.

Because product managers make countless daily decisions—what to build, what to drop, how to allocate resources—lacking product thinking is like driving without a GPS, relying on gut feeling alone.

Focusing on trivial details (button placement, font size) without asking what problem the feature solves leads to wasted effort.

A classic example: Steve Jobs insisted the original iPhone have only one Home button despite team opposition. He argued users need simplicity, not more buttons—an illustration of strong product thinking.

Today, many companies hire product managers not for Axure proficiency but for the ability to articulate why a product is built, for whom, and what change it brings.

How to cultivate product thinking:

Use good products critically—ask what pain point each design solves and how you would improve it.

Keep a notebook of product “aha” moments (e.g., first ride‑hailing experience, first food‑delivery order) to capture authentic feedback.

Chat informally with users; listen to how they describe their lives and frustrations, even if they can’t articulate needs directly.

Spend time observing people in everyday settings (e.g., coffee shops) to see how they interact with devices; such observations often outweigh formal research reports.

Read broadly—psychology, sociology, economics—to understand human behavior, social dynamics, and economic principles that underpin product decisions.

Practice deliberately: treat product learning like swimming—watching tutorials isn’t enough; you must dive in, make mistakes, reflect, and build personal feel.

While structured workshops can provide systematic training, the most effective growth comes from continuous real‑world practice and curiosity about why things are designed the way they are.