What Go Can Teach Product Managers: Mastering Skills, Strategy, and Vision

The article likens a product manager’s growth to mastering the board game Go, outlining three progressive stages—technique, method, and philosophy—to illustrate how basic skills, strategic analysis, and a big‑picture mindset together shape effective product development.

JD Retail Technology
JD Retail Technology
JD Retail Technology
What Go Can Teach Product Managers: Mastering Skills, Strategy, and Vision

Introduction

As a product manager who loves the board game Go, the author draws parallels between the two disciplines, arguing that both involve a learning journey that can be divided into three stages: mastering techniques, acquiring methods, and cultivating a philosophical outlook.

Stage 1 – Mastering “Techniques”

Techniques are split into basic terminology and fundamental skills, then advanced skills. In Go, basic terms include “liberty”, “territory”, “eyes”, and basic skills cover life‑and‑death judgment, opening, middle game, and endgame. In product management, basic terms include PRD, persona, conversion rate, etc., and basic skills involve user interviews, requirement analysis, product design, prototyping, and process control. Advanced skills include “reviewing game records” (studying opponents’ games) which corresponds to competitive analysis, and “post‑game review” (re‑examining a finished game) which maps to product retrospectives after launch.

Stage 2 – Acquiring “Methods”

Methods cannot be learned from books alone; they emerge from repeated failures and insights. The author cites Go schools such as the “cosmic style” of Masaki Takemiya and the “floor style”, both demanding strong calculation ability. For product managers, “calculation” means extracting the core value behind a requirement, enabling the design of a Minimum Viable Product (MVP) that validates assumptions while conserving limited resources.

Stage 3 – Cultivating “The Way”

The final stage is about developing a “big‑picture view”. In Go, this means the ability to step back, assess the whole board, and decide whether to fight locally or create new territory. For product managers, it translates to constantly aligning product decisions with market context, resource constraints, technology trends, and competitive landscape, thereby identifying red‑sea versus blue‑sea opportunities.

Conclusion

The author hopes the analogy inspires product managers to follow a similar progression—starting with concrete skills, moving to strategic methods, and ultimately embracing a holistic perspective that guides long‑term product vision.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

product-managementstrategySkill developmentbig picturego analogy
JD Retail Technology
Written by

JD Retail Technology

Official platform of JD Retail Technology, delivering insightful R&D news and a deep look into the lives and work of technologists.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.