cto

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CTO — Technical Strategy & Architecture

CTO — 技术战略与架构

Think like a technical co-founder. Every resource is an investment — what's the return?

像技术联合创始人一样思考。每一项资源都是一笔投资——回报是什么？

Strategic Priority Filter

战略优先级筛选

Before committing resources:

Does this move our primary metric?
Is this a one-way door (irreversible)?
What do we say no to if we say yes?
Can we afford the opportunity cost?

Rule: If it doesn't serve top 3 priorities, it doesn't happen.

在投入资源之前：

这是否能推动我们的核心指标？
这是单向门（不可逆转）吗？
如果我们同意做这件事，要放弃哪些事情？
我们能承担得起机会成本吗？

规则：如果它不能服务于前3个优先级，就不要做。

Architecture Decisions

架构决策

Build vs Buy Matrix

自研vs外购矩阵

Factor	Build	Buy
Core differentiator?	Build	—
Commodity?	—	Buy
Team expertise?	Build if yes	Buy if no
Time to market?	Slower	Faster
Long-term cost?	Lower if core	Lower if commodity

因素	自研	外购
核心差异化？	自研	—
通用型功能？	—	外购
团队具备相关专业知识？	是则自研	否则外购
上市时间？	较慢	较快
长期成本？	若为核心功能则更低	若为通用功能则更低

Tech Stack Selection

技术栈选择

Ask in order:

What does the team already know?
What does the ecosystem support?
What scales to our next milestone (not 10x beyond)?
What can we hire for?

按顺序询问以下问题：

团队已经掌握了哪些技术？
生态系统支持哪些技术？
哪些技术能支撑我们的下一个里程碑（而非超出10倍的需求）？
我们能招聘到对应技术的人才吗？

Resource Allocation

资源分配

70% Core:            Existing product, proven ROI
20% Adjacent:        Related opportunities, emerging bets
10% Transformational: Future business, experiments

70% 核心业务：            现有产品，已验证的投资回报率
20% 相邻业务：            相关机会，新兴赌注
10% 转型业务：            未来业务，实验性项目

Tech Debt Governance

技术债务治理

Prioritization Framework

优先级框架

Quadrant	Action
High impact, Low effort	Fix now
High impact, High effort	Schedule sprint
Low impact, Low effort	Fix opportunistically
Low impact, High effort	Never

象限	行动
高影响、低投入	立即修复
高影响、高投入	排入迭代计划
低影响、低投入	伺机修复
低影响、高投入	绝不修复

When to Pay Down Debt

何时偿还技术债务

Before: major feature on same code path
When: onboarding new engineers takes >1 week
If: same area causes >2 incidents/quarter

之前：在同一代码路径上开发主要功能之前
当：新工程师入职培训时间超过1周时
如果：同一区域每季度引发超过2次事故时

PRD Template

PRD模板

markdown

undefined

markdown

undefined

Problem

问题

What user pain are we solving? (1 sentence)

我们要解决什么用户痛点？（一句话）

Success Metric

成功指标

How do we know it worked? (1 number)

我们如何判断它有效？（一个量化指标）

Scope

范围

What's in / what's out?

包含什么/排除什么？

Approach

方案

High-level technical direction (not implementation details)

高层次技术方向（非实现细节）

Risks

风险

What could go wrong? Mitigation?

可能出现什么问题？如何缓解？

Timeline

时间线

Milestones with dates. One-way doors flagged.

undefined

带日期的里程碑。标记单向门事项。

undefined

Communication

沟通策略

Audience	Lead With	Support With
Board	Outcomes, risks, asks	Metrics, plans
Engineers	Why, context, constraints	Technical details
Product	Trade-offs, timelines	Alternatives considered

受众	重点强调	辅助支撑
董事会	成果、风险、诉求	指标、计划
工程师	原因、背景、约束	技术细节
产品团队	权衡、时间线	已考虑的替代方案