Working with Cross-Functional Partners
How to communicate with PMs, designers, data, sales, and support in English (用英文跟 PM、设计、数据、销售、客服合作)
Engineers Speak One Language; Everyone Else Speaks Differently (工程师说一种话;其他人说另一种)
The engineer who only knows how to talk to other engineers caps out at mid-level. Senior+ work requires fluently translating between engineering, product, design, data, sales, support, and leadership. Each function has its own vocabulary, priorities, and unwritten rules.
只会和工程师说话的工程师卡在中级。资深以上的工作需要在工程、产品、设计、数据、销售、客服、领导层之间流畅翻译。每个职能有自己的词汇、优先级、潜规则。
The principle 原则: Speak in their metric, not yours. Sales cares about deals; PMs care about user value; engineers care about systems. Translate.
用对方的指标说话,不是你的。销售在意 deal;PM 在意用户价值;工程师在意系统。翻译。
Working With PMs (产品经理) (与 PM 合作)
What they care about (他们在意什么)
- User value, business impact, dates, scope, dependencies.
- 用户价值、商业影响、日期、范围、依赖。
- They are usually under pressure from leadership for predictability.
- 他们通常被领导层施压要可预测性。
Useful phrases (实用短语)
- "What's the user problem we're solving?" — 我们在解决什么用户问题?
- "What does success look like for this — what metric moves?" — 这个成功的样子是什么——哪个指标会动?
- "What's the must-have vs. nice-to-have here?" — 这里什么是必须,什么是锦上添花?
- "If I had to cut something to ship on time, what would you cut?" — 要按时发布得砍点什么,你会砍什么?
- "I can hit Friday with X, or Wednesday after with X+Y. Which serves the user better?" — 周五前我能做 X,再加一周能做 X+Y。哪个对用户更好?
Pushback that lands (有效的反推)
❌ "That's not how the system works." — PM 听不懂。 ✅ "That'll require us to rebuild [component] — adds 3 weeks. Worth it for the user value, or should we explore a smaller approach?" — 转换成时间和价值。
❌ "We can't do that." — 直接拒绝。 ✅ "We can do A in 2 weeks, B in 6 weeks, or C in 1 quarter. Which problem is most important?" — 把"不"变成选项。
Giving estimates without committing prematurely (不过早承诺地给估算)
- "Rough estimate: 2-4 weeks. I'll have a confident number after I've spiked on the storage piece." — 粗略估计 2-4 周。在 spike 完存储部分后给确定数字。(spike = 调研性原型)
- "Order of magnitude: weeks, not days, not months." — 数量级:周,不是天也不是月。
- "I want to give you a real answer, not a fake one — give me 2 days." — 我想给你真答案,不是假答案——给我 2 天。
Working With Designers (与设计师合作)
What they care about (他们在意什么)
- User experience, visual consistency, brand, accessibility, edge cases of state (loading, error, empty).
- 用户体验、视觉一致、品牌、可访问性、状态边界(加载、错误、空状态)。
- Their work is highly visible and easy to critique — many of them are sensitive about feedback.
- 他们的工作高度可见、容易被评论——很多人对反馈敏感。
Useful phrases (实用短语)
- "Walk me through the flow once more." — 再带我过一遍流程。
- "What about [edge case] — loading, error, no data?" — [边界情况] 怎么处理——加载、错误、无数据?
- "On the technical side, [X] is expensive — would [alternative interaction] still solve the user problem?" — 技术上 [X] 成本高——[替代交互] 是否还能解决用户问题?
- "Can we ship a simpler v1 and iterate on this animation later?" — 能先发简单的 v1,动画后续迭代吗?
Giving design feedback without stepping on toes (不冒犯地给设计反馈)
❌ "This looks bad." — 不专业。 ❌ "Why isn't it [different design]?" — 听起来在重设计。
✅ "From an implementation standpoint, [X] is straightforward — [Y] is significantly more expensive. Would the simpler version still work for the user?" — 从实现角度说…… ✅ "Just thinking about engineering tradeoffs — would you be open to [alternative]?" — 想着工程取舍…… ✅ "Beautiful design. One concern: [edge case]. How should it behave?" — 先肯定再提具体问题。
When you spot a UX issue (发现 UX 问题时)
- "User question: when X happens, what does the user see?" — 用户问题:X 发生时用户看到什么?
- "I might be missing context — is this flow accessible for [edge case users]?" — 我可能缺背景——这个流程对 [边缘用户] 是否可访问?
- "From an engineering view, [Z] would be much simpler. From a UX view — what do you think?" — 工程视角 [Z] 简单得多。UX 视角——你怎么看?
Working With Data Scientists / Data Analysts (与数据科学家/分析师合作)
What they care about (他们在意什么)
- Statistical rigor, sample size, confidence intervals, instrumentation correctness.
- 统计严谨性、样本量、置信区间、埋点正确性。
- They get frustrated when engineers ship features without metrics, or use averages where medians matter.
- 他们对工程师不带指标发功能、或者乱用平均数感到无奈。
Useful phrases (实用短语)
- "What metric would tell us this is working?" — 什么指标能告诉我们这有效?
- "Can you help me figure out what to instrument?" — 能帮我想想要埋什么点吗?
- "What's the right experimental setup here — A/B, holdout, gradual rollout?" — 这里合适的实验方式是什么——A/B、holdout、渐进推出?
- "Is the sample size big enough to draw conclusions?" — 样本量够下结论吗?
- "What's the baseline we're comparing against?" — 我们对比的 baseline 是什么?
When asking for analysis (请求分析时)
❌ "Can you pull some numbers on X?" — 太模糊。 ✅ "Decision I'm trying to make: should we keep feature X. Question for the data: what % of users use X weekly, and do they retain better than non-users? Need by Wednesday for the review." — 把决策、问题、deadline 都说清楚。
Reading their results (理解他们的结果)
- "Help me translate — is this a real effect or noise?" — 帮我翻译——这是真效应还是噪声?
- "What's the confidence interval?" — 置信区间是多少?
- "What's the practical significance, not just statistical?" — 实际意义是什么,不只是统计意义?
- "What would change your mind about this?" — 什么会让你改变看法?
Working With Sales (与销售合作)
What they care about (他们在意什么)
- Closing deals, quarterly numbers, customer-specific commitments, demos.
- 关 deal、季度数字、客户特定承诺、演示。
- They will sometimes promise things to customers without checking with engineering. Manage this.
- 有时不问工程就向客户承诺。要管理。
Useful phrases (实用短语)
- "What's the deal worth, and what's the customer's must-have?" — deal 多大?客户的 must-have 是什么?
- "What's the timeline pressure on your side?" — 你那边时间压力是什么?
- "I want to help you close this — let's figure out what's possible." — 我想帮你关单——我们看看什么可行。
- "Before you commit X to the customer, can you check with us?" — 你向客户承诺 X 之前能跟我们确认一下吗?
When sales over-promised (销售承诺过头时)
- "That was committed without engineering review. Let's figure out what's actually deliverable and how to land it with the customer." — 这是没有工程评审就承诺的。我们看实际能交付什么,并想想怎么和客户说。
- "We can deliver 80% of what was promised by the date. The remaining 20% will take an extra month. How should we frame this with the customer?" — 我们能按时交付 80%。剩下 20% 多一个月。如何向客户表达?
Joining a sales call (加入销售电话)
Sales sometimes asks engineers to join customer calls for credibility.
销售有时让工程师加入客户电话来增加可信度。
- "Quick check — what's the customer's biggest concern? What do you want me to drive home?" — 快速确认——客户最大的顾虑是什么?你想让我重点强调什么?
- "What's a green/yellow/red flag I should listen for?" — 我应该注意什么绿/黄/红信号?
- "How direct can I be about technical limitations?" — 关于技术限制我可以多直接?
Working With Support / Customer Success (与客服/客户成功合作)
What they care about (他们在意什么)
- Reducing ticket volume, fast resolution, clear customer-facing explanations.
- 降低工单量、快速解决、清晰的对客户解释。
- They are the front line and often see issues engineering doesn't.
- 他们是一线,经常看到工程看不到的问题。
Useful phrases (实用短语)
- "What are you hearing from customers?" — 你从客户那里听到什么?
- "What's your top ticket category right now?" — 你现在最多的工单类别是什么?
- "Can you give me 3 real examples of customers hitting this?" — 能给我 3 个真实客户碰到这个的例子吗?
- "What would make your job easier on this?" — 这件事上什么能让你的工作轻松点?
Closing the loop after a fix (修复后闭环)
- "FYI — fix shipped for [issue]. Customer-facing message: [draft]. Let me know if you want to tweak." — 知会一下——[问题] 修复已发。给客户的话术:[草稿]。需要调整告诉我。
- "Want me to write the customer comms, or do you want to draft and I'll review?" — 要我写给客户的消息,还是你起草我看?
Working With Legal / Compliance / Security (与法务/合规/安全合作)
What they care about (他们在意什么)
- Risk, exposure, audit trail, regulatory compliance, contractual obligations.
- 风险、暴露面、审计记录、合规、合同义务。
- They block things. Their job is to block things until risk is acceptable.
- 他们会阻塞。他们的工作就是阻塞,直到风险可接受。
Useful phrases (实用短语)
- "What's the risk threshold here?" — 风险阈值是什么?
- "What would make this acceptable to you?" — 怎样才能让你接受?
- "Is this a hard no, or a 'no until we add X'?" — 这是硬"不",还是"加上 X 才行"?
- "Help me understand the regulation — what specifically does it require?" — 帮我理解法规——具体要求什么?
Don't surprise them (不要让他们吃惊)
The fastest way to get blocked: surprise legal/security at launch time. Loop them in early.
最快被阻塞的方式:发布时让法务/安全吃惊。早点拉他们进来。
- "Wanted to loop you in on something we're scoping. Could touch on [PII / GDPR / SOC2]. Worth a 30-min review now or later?" — 想把你拉进来。可能涉及 [PII/GDPR/SOC2]。30 分钟评审现在还是以后?
Working With Recruiters / HR (与 recruiter / HR 合作)
What they care about (他们在意什么)
- Hiring funnel velocity, candidate experience, headcount targets, retention metrics.
- 招聘漏斗速度、候选人体验、招聘指标、留存率。
Useful phrases (实用短语)
- "What's your priority hire right now?" — 你现在最优先招的角色是什么?
- "What's your time-to-fill target?" — 你 time-to-fill 的目标是?
- "Quick favor — can you push back on my interview load this week?" — 麻烦——这周能帮我减少面试量吗?
Working With Executives / Leadership (与高管/领导层合作)
See the dedicated Managing Up page for depth. Quick guidance:
详见 Managing Up 单独页面。快速指引:
- Lead with the answer. Execs read the first sentence; the rest is appendix.
- **答案先行。**高管只读第一句;其他是附录。
- Use their language: revenue, risk, headcount, time, customer impact. Not "we refactored the auth service."
- **用他们的语言:收入、风险、人员、时间、客户影响。**不要说"我们重构了认证服务"。
- Be calibrated. Confident, not certain. Specific, not vague.
- 校准。自信但不绝对。具体不模糊。
Translating Between Functions (跨职能翻译)
The senior+ skill: translate the same fact for different audiences.
资深以上的技能:翻译同一事实给不同受众。
| Fact | To engineers | To PM | To exec |
|---|---|---|---|
| API outage caused 30-min downtime | "Auth service 500'd due to memory leak." | "Login was broken for ~15% of users for 30 min." | "30-min auth incident; ~$X revenue impact; postmortem in flight." |
| Refactor in progress | "Splitting the monolith into 3 services." | "We're investing 4 weeks now to make future features ship 2x faster." | "Q3 platform investment; payback in Q4 via 2x velocity." |
| Found a bug | "Off-by-one in the pagination cursor." | "Some users were missing items 50, 100, 150 in their feed." | "Minor data integrity issue affecting under 1% of feeds; fixed; monitoring." |
Phrases to Avoid (要避免的表达)
| ❌ Avoid (避免) | Why (原因) | ✅ Better (更好) |
|---|---|---|
| Heavy engineering jargon with non-engineers | 让对方觉得你 condescending 或自顾自 | "In simpler terms..." or pre-translate. |
| "That's a product question." (in response to a tech question) | 推卸 | "Let me bring in [PM] — but here's my engineering view first." |
| "They don't understand." | 你的工作就是让他们理解 | "Let me try a different framing." |
| Treating PMs as adversaries | 一致是常态,对抗是少数 | "We both want this to ship well — let's figure out scope." |
| "Sales is going to make us regret this." | 团队内攻击 | Talk with sales, not about them. |
Cultural Notes (文化提示)
Each function has its own status game (每个职能有自己的地位博弈)
In some companies engineering is king; in others product is. In sales-led orgs, sales is. Read the org's power structure and don't assume your function's power transfers.
有的公司工程为王;有的产品为王。销售导向的组织里销售为王。读懂组织的权力结构,不要以为你职能的权力可以迁移。
Build allies in every function (每个职能都建盟友)
Senior+ engineers are known by name to PMs, designers, and even sales/finance leads. Build those relationships before you need favors.
资深以上的工程师在 PM、设计、甚至销售/财务 leads 那都有名。在需要帮忙之前就建立这些关系。
Translate, don't condescend (翻译,但不要俯视)
Translating is not "dumbing it down." It's framing the same idea in their world. PMs and execs are often very smart — they just have different metrics in their head.
翻译不是"降智"。是用他们的世界框定同一个想法。PM 和高管经常很聪明——只是脑子里的指标不同。
Don't slag on other functions (不要诋毁其他职能)
"Sales over-promises again." "Designers don't understand constraints." "PMs just push features." These are common venting and career-limiting. Other functions hear it eventually.
"销售又乱承诺。" "设计不懂限制。" "PM 只会催功能。" 这些常见的吐槽会限制职业。其他职能最终会听到。
Tips (小贴士)
- Learn each function's metrics — What do they actually get measured on? 学每个职能的考核指标。
- Spend 1 day shadowing other functions in your first 6 months — 30 min with sales, support, design. ROI is huge. 影子跟踪。
- Write for your audience — Same content, different framing. 同内容不同包装。
- Don't be the engineer who only talks to engineers — Senior+ requires range. 不要只会跟工程师说话。
- Assume good intent, always — Other functions aren't obstacles, they're partners. 假设善意。