Why Engineers Must Adopt Product Thinking—and How to Strengthen It

What Is Product Thinking?

Product thinking is a mindset that uses scientific methodology to continuously capture maximum value, moving beyond vague definitions to concrete, actionable forms. It enables leaders—often managers—to understand both sides of a conflict, propose solutions, and communicate in a way that both parties accept.

Why Technical Staff Should Have Product Thinking

1. Limitations of a Pure Technical Viewpoint

Seeing product requests as meaningless or “chicken‑rib” requirements.

Frustration over constantly changing requirements that lower efficiency.

Believing product ideas are unrealistic or unimplementable.

Criticizing perceived logical gaps in product proposals.

These complaints often stem from a clash between product‑centric and engineering‑centric perspectives rather than from the product’s inherent flaws.

2. Real‑World Example: Box‑In‑Box‑Out in a Fresh‑Food Warehouse

Engineers initially flagged the feature as infeasible because the existing system had no support for nested boxes, the required full‑chain overhaul was large, and edge‑case inventory reconciliation seemed impossible.

1. The scenario did not exist in the current system; feasibility was unknown. 2. Full‑chain adaptation would be extensive and hard to implement. 3. Handling rare edge cases could break the entire workflow.

From the product side, however, the same scenario represented a genuine business need that could drive future capability expansion.

1. Recognize the new capability as a legitimate business requirement. 2. Plan the full‑chain change as an iterative improvement. 3. Treat rare edge cases as low‑probability events that should not block progress.

Adopting product thinking helps engineers articulate technical constraints while acknowledging product value, leading to more balanced decisions.

Benefits of Product Thinking for Engineers

Improved abstraction ability: Engineers can frame problems at a higher level, ask “why” questions, and create future‑proof models (e.g., abstracting a weighing task into a “process” concept).

Broader system perspective: Understanding upstream and downstream dependencies increases readiness for larger responsibilities.

Clearer value awareness: Knowing the why behind a request guides better cost‑benefit analysis.

Enhanced business impact: Engineers can spot optimization opportunities, such as reducing pick‑and‑place cycles, which led to 12%‑14% efficiency gains in real warehouse scenarios.

How to Strengthen Product Ability

1. Mind‑set Shifts

Fundamental thinking: Apply first‑principles, strip away assumptions, and use iterative questioning.

Relative thinking: View strengths and weaknesses as temporary, consider context and time.

Abstract thinking: Move between concrete details and high‑level concepts, focusing on capabilities rather than features.

System thinking: Design feedback loops and recognize that edge cases are low‑probability exceptions.

Evolutionary thinking: Embrace minimalism and modular frameworks that can grow organically.

2. Small Practical Steps

Read widely and build a solid knowledge base.

Summarize learnings and share them to reinforce structured thinking.

Maintain curiosity beyond immediate tasks; explore upstream/downstream processes and related domains.

Practice empathy in PRD reviews, asking what underlying user goals a requirement serves.

When faced with a new request, imagine multiple solution dimensions (e.g., L1 vs. L2 task‑selection capabilities in a scheduling system).

From Traditional Databases to Cloud Databases

With the rise of cloud computing, database deployment has shifted from on‑premise data centers to public, private, hybrid, and even hardware‑agnostic cloud models. Alibaba Cloud’s database services must handle massive spikes—such as a 135‑fold surge during the 2019 Double‑11 shopping festival—requiring high scalability, elasticity, and availability.