technical-roadmaps

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Technical Roadmaps

技术路线图

Help the user create effective technical roadmaps using frameworks and insights from 1 product leader.

借助一位产品负责人提供的框架和见解，帮助用户创建有效的技术路线图。

How to Help

如何提供帮助

When the user asks for help with technical roadmaps:

Understand the context - Ask about their current technical state, team size, and business constraints
Ensure it's written down - A strategy that isn't documented can't be debugged or aligned around
Apply the Rumelt framework - Structure as Diagnosis (what's the problem), Guiding Policies (principles for decisions), and Actions (what you'll do)
Favor boring strategies - Help them resist the urge to introduce new tools when existing ones would suffice

当用户请求技术路线图相关帮助时：

了解背景信息 - 询问他们当前的技术状态、团队规模和业务约束条件
确保书面化 - 未形成文档的战略无法被调试或达成共识
应用Rumelt框架 - 按照诊断（存在什么问题）、指导原则（决策遵循的准则）和行动（具体要做什么）的结构来构建
优先选择“无趣”的策略 - 帮助他们抵制在现有工具足够用的情况下引入新工具的冲动

Core Principles

核心原则

Write it down

书面化战略

Will Larson: "The first rule of strategy is that if you write it down, then you can improve it. If it's not written down, it's hard to say if this PM is just not a good PM or if they're trying to apply a strategy they've misunderstood." A written strategy provides a baseline that can be critiqued and improved.

Will Larson：“战略的第一条规则是，如果你把它写下来，你就能改进它。如果没有写下来，很难判断这位产品经理是能力不足，还是在尝试应用他们误解的战略。”书面化的战略提供了一个可以被批评和改进的基准。

Boring strategies often win

“无趣”的策略往往更有效

Will Larson: "A common strategy that's really good but very boring is we only use the tools we have today. Engineers want to introduce new programming languages, new databases, new cloud providers. A really good strategy for almost all companies is we just use the standard kit we already have." Focus engineering energy on business-valued problems rather than technical novelty.

Will Larson：“一个非常有效但却很‘无趣’的常见策略是：我们只使用现有的工具。工程师们总想引入新的编程语言、新数据库、新云服务商。对于几乎所有公司来说，一个非常好的战略就是只使用我们已有的标准工具集。”将工程师的精力集中在具有业务价值的问题上，而非技术创新。

Use the Rumelt framework

使用Rumelt框架

Structure technical strategy using Richard Rumelt's framework: Diagnosis (what's the core challenge?), Guiding Policies (what principles will guide decisions?), and Actions (what specific things will you do?).

采用Richard Rumelt的框架构建技术战略：诊断（核心挑战是什么？）、指导原则（决策将遵循哪些准则？）和行动（具体要执行哪些任务？）。

Create a standard kit

制定标准工具集

Define a list of approved tools, languages, and platforms. This limits technical sprawl and allows teams to focus on solving core product problems rather than reinventing infrastructure.

定义一份经批准的工具、语言和平台列表。这可以限制技术蔓延，让团队专注于解决核心产品问题，而非重新构建基础设施。

Questions to Help Users

帮助用户的问题

"Is this technical strategy written down somewhere that anyone can reference?"
"What is the core technical challenge you're trying to solve (the diagnosis)?"
"What principles will guide your technical decisions (the guiding policies)?"
"Are you adding new tools because you need them, or because they're interesting?"
"What does your 'standard kit' of approved technologies look like?"
"How does this technical roadmap connect to business outcomes?"

“这份技术战略是否记录在所有人都可以参考的地方？”
“你试图解决的核心技术挑战是什么（即诊断部分）？”
“你的技术决策将遵循哪些准则（即指导原则）？”
“你引入新工具是因为确实需要，还是因为它们看起来很有趣？”
“你们经批准的技术‘标准工具集’包含哪些内容？”
“这份技术路线图如何与业务成果挂钩？”

Common Mistakes to Flag

需要指出的常见错误

Unwritten strategy - A strategy that only exists in someone's head can't be debugged or aligned around
Tool proliferation - Introducing new technologies when existing ones would work creates maintenance burden
No connection to business value - Technical roadmaps that don't tie to product or business outcomes lack justification
All diagnosis, no action - Good strategy requires specific actions, not just analysis of the problem
Missing guiding policies - Without principles, every technical decision becomes a debate from scratch

未书面化的战略 - 仅存在于某个人头脑中的战略无法被调试或达成共识
工具泛滥 - 在现有工具足够用的情况下引入新技术会增加维护负担
与业务价值脱节 - 未与产品或业务成果挂钩的技术路线图缺乏合理性
只有诊断，没有行动 - 优秀的战略需要具体的行动，而非仅仅是问题分析
缺少指导原则 - 没有准则的话，每一项技术决策都要从头开始争论

Deep Dive

深入探讨

For all 2 insights from 1 guest, see

references/guest-insights.md

如需了解来自1位嘉宾的全部2条见解，请查看

references/guest-insights.md