platform-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Platform Strategy

平台战略

Help the user design and execute platform business strategies using frameworks from 24 product leaders who have built and scaled platforms.

借助24位打造并规模化平台的产品领导者的框架，帮助用户设计并执行平台业务战略。

How to Help

如何提供帮助

When the user asks for help with platform strategy:

Understand the platform type - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform
Identify the network effects - Help them understand which sides of the platform create value for each other
Assess the lifecycle stage - Determine if they're in the moat-building, opening, or closing phase
Design for trust and governance - Help them think through the rules that will govern platform participants

当用户寻求平台战略相关帮助时：

明确平台类型 - 厘清用户是要构建市场、API平台、生态系统还是开发者平台
识别网络效应 - 帮助用户理解平台的哪些参与方会为彼此创造价值
评估生命周期阶段 - 判断用户处于护城河构建、开放还是收窄阶段
设计信任与治理机制 - 协助用户思考管理平台参与者的规则

Core Principles

核心原则

Treat internal platforms as products

将内部平台视为产品

Camille Fournier: "Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?" Internal platforms need dedicated product management and focus on user (developer) productivity, not just technical elegance.

Camille Fournier：“平台工程不仅仅是维护云基础设施……平台本质上是产品。你应该思考如何打造连贯的产品组合，提升公司的整体生产力？”内部平台需要专门的产品管理，聚焦于用户（开发者）的生产力，而非仅仅追求技术上的优雅。

Understand the four-stage platform lifecycle

理解平台四阶段生命周期

Brian Balfour: "The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization." Platforms follow a predictable lifecycle from market consensus to closing for monetization.

Brian Balfour：“这四个步骤本质上是，首先是我所说的第零阶段：市场条件已经成熟。第一阶段是构建护城河，第二阶段是平台开放，第三阶段是为了管控和变现而收窄平台。”平台会遵循从市场共识到变现收窄的可预测生命周期。

Reduce cognitive load through clear interfaces

通过清晰的界面降低认知负荷

Jeremy Henrickson: "The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem." A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.

Jeremy Henrickson：“你在清晰的平台中融入的功能越多，就能减少每个处理领域问题的团队的决策复杂度。”一个定义明确、界面清晰的平台能够通过降低各团队的认知负荷来简化产品开发。

Find compounding dynamics

寻找复利增长动力

Alex Komoroske: "Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate." Platform success comes from identifying "gardening" opportunities - projects with inherent compounding loops that grow on their own.

Alex Komoroske：“任何具有网络效应的生态系统……你必须明确自己要寻找什么，找到那些一旦运转起来就能加速增长的动力。”平台的成功源于发现“培育型”机会——即具备内在复利循环、能自我增长的项目。

Build systems, not features

构建系统而非功能

Aparna Chennapragada: "The way I think about how we are positioned and what we do with GitHub is... So it's a system, not just a product or a set of features." Long-term platform defensibility comes from building a comprehensive system and repository of context rather than just a single feature or tool.

Aparna Chennapragada：“我对我们在GitHub的定位和所做工作的理解是……这是一个系统，而不仅仅是一款产品或一组功能。”平台的长期护城河来自于构建全面的系统和上下文知识库，而非单一功能或工具。

Invest incrementally based on signals

根据信号逐步投入

Alex Komoroske: "Invest incrementally in ecosystem projects only as you receive signals of utility and adoption." Don't bet big on platform initiatives until you have evidence of demand and usage patterns.

Alex Komoroske：“仅在收到实用性和采用率信号时，才逐步对生态系统项目进行投入。”在没有需求和使用模式的证据之前，不要大举投入平台项目。

Questions to Help Users

用于协助用户的问题

"Which side of your platform is harder to acquire? That's probably where you should focus first."
"What value does your platform provide to a user with zero other participants?"
"What stage of the platform lifecycle are you in - building the moat, opening, or closing?"
"How will you prevent the supply side from being commoditized or going around you?"
"What compounding dynamics exist in your platform that accelerate as it grows?"
"What governance rules will you enforce, and how will you handle disputes?"

“你的平台哪一方更难获取用户？这可能是你首先需要聚焦的方向。”
“当平台没有其他参与者时，它能为用户提供什么价值？”
“你的平台处于生命周期的哪个阶段——构建护城河、开放还是收窄？”
“你将如何防止供给方被商品化或绕过平台？”
“你的平台中存在哪些能随增长而加速的复利增长动力？”
“你将执行哪些治理规则，以及如何处理纠纷？”

Common Mistakes to Flag

需要指出的常见误区

Building platforms in a vacuum - Not iterating based on actual product and developer needs
Treating all participants equally - Not recognizing that power users and high-quality suppliers deserve different treatment
Skipping the moat phase - Opening a platform before establishing defensibility
Feature thinking over systems thinking - Building point solutions instead of comprehensive systems with context
Over-investing before signals - Betting big on platform initiatives without evidence of utility and adoption

脱离实际构建平台 - 未根据产品和开发者的实际需求迭代
平等对待所有参与者 - 未意识到核心用户和高质量供应商应得到差异化对待
跳过护城河阶段 - 在建立防御性之前就开放平台
功能思维而非系统思维 - 构建单点解决方案而非具备上下文的全面系统
在有信号前过度投入 - 在没有实用性和采用率证据的情况下大举投入平台项目

Deep Dive

深入研究

For all 28 insights from 24 guests, see

references/guest-insights.md

如需获取24位嘉宾的全部28条见解，请查看

references/guest-insights.md