cross-functional-collaboration

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cross-functional Collaboration

跨职能协作

Help the user work effectively across functions using frameworks from 57 product leaders who have built high-performing cross-functional teams at companies from Linear to Airbnb.

借助来自Linear到Airbnb等公司、打造过高绩效跨职能团队的57位产品领导者的经验框架，帮助用户跨职能高效开展工作。

How to Help

如何提供帮助

When the user asks for help with cross-functional collaboration:

Diagnose the friction - Identify whether the issue is role clarity, communication patterns, or structural
Clarify expectations - Help define what each function expects from the others
Design the right structure - Recommend team composition and meeting rhythms
Build relationships - Emphasize the human elements that make collaboration work

当用户寻求跨职能协作相关帮助时：

诊断摩擦点 - 明确问题根源是角色定位模糊、沟通模式问题还是组织结构问题
明确预期 - 协助定义各职能团队对彼此的期望
设计合理架构 - 推荐团队构成和会议节奏
搭建协作关系 - 强调让协作奏效的人文因素

Core Principles

核心原则

Share credit generously

慷慨分享功劳

Camille Fournier: "Engineers sometimes think that they don't get the credit for their work because the PM takes all the glory. So making every effort to be credit sharing and inclusive of the engineering team." Let engineers present their own work to executives and customers.

Camille Fournier：“工程师有时会觉得自己的工作成果没有得到认可，因为产品经理独占了所有荣誉。所以要尽一切努力分享功劳，让工程师团队也被纳入其中。”让工程师向高管和客户展示自己的工作成果。

Use 'Yes, and' thinking

采用‘是的，而且’思维

Adam Grenier: "If you approach it with that 'Yes, and,' it's often still true. Both of these things can be true at once. You could have a different goal than I have." Validate different team goals simultaneously rather than creating false dichotomies.

Adam Grenier：“如果你用‘是的，而且’的思路来处理，通常会发现事实确实如此。两件事可以同时成立。你的目标可能和我的不同，但这并不矛盾。”同时认可不同团队的目标，而非制造虚假的二元对立。

Write expectations for each other

书面明确彼此期望

Nikita Miller: "Have PM, Design, Engineering, and Data leaders write down expectations for their counterparts. Create a 'contract' between roles to clarify shared responsibilities." Revisit these definitions every 3-6 months.

Nikita Miller：“让产品经理、设计、工程和数据团队的负责人写下对对应角色的期望。在不同角色间建立一份‘约定’，明确共同职责。”每3-6个月重新审视这些定义。

Include engineers in discovery

让工程师参与发现阶段

Christine Itwaru: "Early on, we started bringing in engineers to customer meetings more and more. When we started doing it, the response from the engineering team was great." Direct customer exposure builds technical empathy.

Christine Itwaru：“早期我们开始越来越多地让工程师参与客户会议。当我们这么做时，工程师团队的反馈非常积极。”直接接触客户能培养技术同理心。

Don't play telephone

不要做传声筒

Camille Fournier: "If you put yourself in this in-between position and you're playing telephone between stakeholders and engineers, that is very annoying and it's a waste of time for everyone." Connect stakeholders directly to engineers when technical depth is needed.

Camille Fournier：“如果你把自己放在中间位置，在干系人和工程师之间做传声筒，这会非常令人厌烦，而且是在浪费所有人的时间。”当需要技术深度沟通时，让干系人与工程师直接对接。

Work directly with engineers daily

每天直接与工程师协作

Marty Cagan: "If you're not working every day with a set of engineers on solving problems, you are not a product manager." Remove intermediaries like 'product owners' who act as mediators.

Marty Cagan：“如果你没有每天和一群工程师一起解决问题，那你就不是一个合格的产品经理。”移除像‘产品负责人’这样的中间协调角色。

Build real relationships

建立真实的人际关系

Ebi Atawodi: "Do you know your engineering manager's birthday? Do you know their work anniversary? Do you know why they're doing the job they're doing?" Strong partnerships are built on personal human connection.

Ebi Atawodi：“你知道你的工程经理的生日吗？知道他们的入职纪念日吗？知道他们从事这份工作的原因吗？”稳固的协作伙伴关系建立在人与人之间的真实联结之上。

Code is the common language

代码是通用语言

Amjad Masad: "The common language that everyone shares is code. What if the language becomes actually working prototypes and working applications?" Use functional prototypes rather than static mocks to reduce handoff friction.

Amjad Masad：“所有人共享的通用语言是代码。如果我们把工作原型和可运行应用作为沟通语言呢？”使用可运行原型而非静态原型来减少工作交接的摩擦。

Embrace the 'product trio'

拥抱‘产品三人组’模式

Teresa Torres: "The trio is the product manager, the designer, and the software engineer. If you've never worked in a well-functioning trio, this breaks people's brains." Resolve disagreements by seeking more data or better options, not by pulling rank.

Teresa Torres：“产品三人组指的是产品经理、设计师和软件工程师。如果你从未在运作良好的三人组中工作过，这种模式会让你大开眼界。”通过寻求更多数据或更优方案来解决分歧，而非靠职级压制。

Questions to Help Users

用于引导用户的问题

"What does each function expect from the others - have you written it down?"
"Are engineers involved in customer discovery or just receiving specs?"
"When there's a conflict, who is the tiebreaker and how quickly do they act?"
"Do you know the personal career goals of your engineering and design partners?"
"Are you acting as a translator or connecting stakeholders directly to engineers?"

“各职能团队对彼此的期望是什么——你们是否将其书面化了？”
“工程师是否参与客户发现环节，还是只接收需求规格？”
“出现冲突时，谁是最终决策者，他们的决策速度如何？”
“你了解你的工程和设计伙伴的个人职业目标吗？”
“你是在做翻译者的角色，还是让干系人与工程师直接对接？”

Common Mistakes to Flag

需要指出的常见误区

Credit hoarding - PMs taking glory for work engineers built
Playing telephone - Acting as an unnecessary intermediary between stakeholders and engineers
Excluding engineers from ideation - Treating them as resources rather than creative partners
Unclear role boundaries - Not defining who owns what leads to everything falling on the PM
Ignoring the human element - Strong collaboration requires knowing your partners as people

独占功劳 - 产品经理将工程师完成的工作成果的荣誉据为己有
做传声筒 - 在干系人和工程师之间充当不必要的中间协调者
将工程师排除在创意环节之外 - 把工程师视为资源而非创意伙伴
角色边界模糊 - 未明确职责归属导致所有工作都落到产品经理身上
忽视人文因素 - 稳固的协作需要将伙伴视为真实的人来了解

Deep Dive

深度拓展

For all 72 insights from 57 guests, see

references/guest-insights.md

如需查看来自57位嘉宾的全部72条见解，请参阅

references/guest-insights.md