What Is Product Thinking? A Product Manager’s Insightful Explanation

Product thinking (or product sense) is not a specific skill such as prototyping or writing requirement documents; it is a way of viewing the world. Like learning photography, where the goal is to understand light, composition, and moments, product thinking teaches you to observe users, grasp contexts, and spot opportunities.

One anecdote describes a product manager who, whenever he dines out, watches how waitstaff take orders, how customers wait, and how the kitchen delivers food, then draws a flowchart at home to sharpen his systems thinking.

The core of product thinking, according to the author, is to start from user value, work backwards to understand the whole system, and finally translate that insight into concrete feature designs. Many people reverse this order—first deciding on a feature, then figuring out how users might use it, and finally searching for a value point—resulting in products that only please the creator, not the market.

Because a product manager’s job is essentially decision‑making—choosing which feature to build, which requirement to drop, how to allocate resources—lacking product thinking is like driving without a navigation system, relying solely on gut feeling.

The author warns against getting stuck in detail debates (button placement, font size) without asking what problem the feature solves for users. Good product thinking lets you rise above such minutiae, seeing the bigger picture as if standing on a hill and viewing the whole city’s traffic flow.

A classic example is Steve Jobs insisting on a single Home button for the iPhone. The team argued for more buttons, but Jobs argued that users wanted simplicity, not more controls—an illustration of strong product thinking.

Modern hiring for product managers no longer focuses on tools like Axure; instead, interviewers care about whether candidates can clearly articulate why a product is built, for whom, and what change it brings.

To cultivate product thinking, the author recommends actively using good products with a critical mindset—always asking what pain point the design addresses and how you would improve it. He keeps a notebook of “flash moments” from experiences such as the first time ordering a ride on DiDi or ordering food on Meituan.

Frequent informal conversations with users, even casual chats, reveal hidden frustrations and unmet needs. Observing people in cafés—how they use phones, interact with friends, solve small problems—provides richer insight than formal research reports.

Beyond product‑specific books, reading psychology, sociology, and economics helps understand human behavior, social mechanisms, and economic principles, which are the true nutrients for product thinking.

Finally, the author stresses that product thinking must be practiced like any skill: swim rather than just watch tutorials, iterate on projects, make mistakes, reflect, and maintain curiosity about why things are the way they are, because each “why” may hide a product opportunity.