team-motivation-ops
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese团队 Motivation 操作手册
Team Motivation Playbook
这套体系的底层逻辑：自由和责任是一体的。Standup 是让人想清楚，例会是让人对齐，1:1 是让人被看见。三件事做好了，motivation 不是管出来的，是长出来的。
适用场景：AI 科技公司 COO 或团队负责人，团队规模 3-30 人，高自由度、远程或半远程。
与产研运 SOP 的边界：本 Skill 诊断个人状态、信息和对齐；需求优先级、Bug、迭代范围与发布门禁交给 。1:1 发现的问题只有进入明确负责人、截止时间和验证方式的 Action Item，才算闭环。
gr-product-dev-opsThe underlying logic of this system: freedom and responsibility go hand in hand. Standups help people clarify their thoughts, weekly meetings ensure alignment, and 1:1s make people feel seen. When these three things are done right, motivation isn't managed—it grows naturally.
Applicable scenarios: COOs or team leads at AI tech companies, team size 3-30 people, high autonomy, remote or hybrid.
Boundary with product R&D and operations SOPs: This Skill diagnoses individual status, information, and alignment; leave requirement prioritization, bugs, iteration scope, and release gates to . Only when issues identified in 1:1s are turned into Action Items with clear owners, deadlines, and verification methods can the loop be closed.
gr-product-dev-ops第一层：每日 Standup — 信息层
Layer 1: Daily Standup — Information Layer
设计哲学
Design Philosophy
Standup 的本质不是汇报，是一种强迫自己想清楚的仪式。写得出来，说明真想清楚了；写不出来，通常是因为自己也没搞清楚今天要干什么。
含糊是会传染的——COO 自己的 standup 要先写好，模式从上往下渗透。
The essence of a standup isn't reporting—it's a ritual that forces you to clarify your thoughts. If you can write it down, you've truly clarified what you need to do; if you can't, it usually means you don't know what you're doing today.
Vagueness is contagious — the COO must write their own standup first, so the pattern permeates from the top down.
标准格式（三个必填项）
Standard Format (Three Required Fields)
- 今天做了什么：具体交付，不写「继续开发」
- 明天要做什么：具体到别人能判断你做没做完
- 遇到什么困难 / 晚上要聊什么：卡点、ownership 不清楚的事
- What I did today: Specific deliverables, don't write "continue development"
- What I will do tomorrow: Specific enough that others can judge if you've completed it
- Challenges encountered / Topics to discuss tonight: Blockers, unclear ownership issues
好 Standup 样本
Good Standup Sample
今天做了什么
- 把 XX 接口写完，本地 50 条数据跑通，平均 80ms，比上一版快一倍
- 帮队友定位 WhatsApp 会话列表渲染卡顿，根源是没做虚拟滚动，指了 react-window 方案，他十分钟搞定
- 实话实说，下午摸鱼了一小时，顺手把竞品新发的 case study 存进竞品库，算将功补过
明天要做什么
- 把批量报价接口推上 staging，拿真实场景跑一遍
- 补今天没写的接口文档
遇到什么困难 / 晚上要聊
- XXX 架构决策还没拍板，影响我这边进度，想今晚对一下What I did today
- Finished writing the XX API, tested 50 local data entries, average response time 80ms, twice as fast as the previous version
- Helped a teammate troubleshoot WhatsApp chat list rendering lag; root cause was lack of virtual scrolling, suggested react-window solution, he fixed it in 10 minutes
- Honestly, I slacked off for an hour this afternoon, but I saved the newly released case study from a competitor into the competitor library, so I guess that makes up for it
What I will do tomorrow
- Push the bulk quotation API to staging and test it in real scenarios
- Complete the API documentation I didn't write today
Challenges encountered / Topics to discuss tonight
- The XXX architecture decision hasn't been finalized, which is affecting my progress; want to align on it tonightCOO 使用原则
COO Principles
- 不要求写完美，要求写真实。摸鱼了就写摸鱼了，但写清楚摸鱼之外做了什么。
- 不批评短 standup，但要追问「今天具体交付了什么」。问题在具体性，不在长度。
- 公开表扬一条好 standup，不批评烂的。具体也会传染。
- 好 standup 是送给队友的礼物，这个认知要反复说。
- Don't demand perfection, demand authenticity. If you slacked off, write it down, but clarify what you did besides slacking off.
- Don't criticize short standups, but follow up with "What specific deliverables did you complete today?" The issue is specificity, not length.
- Publicly praise a good standup, don't criticize bad ones. Specificity is also contagious.
- Repeatedly emphasize that a good standup is a gift to teammates.
第二层：每周例会 — 对齐层
Layer 2: Weekly Meeting — Alignment Layer
设计哲学
Design Philosophy
例会不是进度汇报会。它解决的是「在场感」——让每个人知道公司整体在哪，让每个人当众说出自己承诺了什么。这两件事都不能靠异步完成。
Weekly meetings aren't progress report meetings. They solve the problem of "presence" — letting everyone know where the company stands overall, and letting everyone publicly state what they've committed to. Neither of these can be done asynchronously.
议程结构（25 分钟严格计时）
Agenda Structure (Strict 25-Minute Time Limit)
| 段落 | 时长 | 内容 |
|---|---|---|
| 公司板块 | 8 分钟 | 目前进展 / 接下来一周规划 / 需要团队决策的事 |
| 个人板块 | 每人约 3 分钟 | 上周承诺做到没 / 本周承诺 1-3 件具体事 / 需要团队帮什么 / 当前状态（0-10 分） |
| 集体讨论 | 剩余时间 | 个人分享完后统一讨论；需要 1:1 的问题改为会后单聊 |
「当前状态 0-10 分」不能省。 它是唯一一个让人可以不解释、直接表达现在感受的通道。低分要追问，但不要当众深挖，改为 1:1 后续。
| Segment | Duration | Content |
|---|---|---|
| Company Update | 8 minutes | Current progress / Next week's plan / Matters requiring team decisions |
| Individual Segment | ~3 minutes per person | Did you fulfill last week's commitments? / 1-3 specific commitments for this week / What support do you need from the team? / Current status (0-10 points) |
| Group Discussion | Remaining time | Discuss uniformly after individual shares; move issues requiring 1:1s to post-meeting one-on-one talks |
The "Current Status 0-10 Points" cannot be omitted. It's the only channel where people can express their feelings directly without explanation. Follow up on low scores, but don't dig into details publicly — save that for a subsequent 1:1.
Scrum Master 机制
Scrum Master Mechanism
每周轮换，职责是维持发言顺序和时间节奏。轮换制会降低对 COO 的依赖感，让每个人对会议流程有主人翁感。
Rotate weekly; responsibilities include maintaining speaking order and time rhythm. Rotation reduces reliance on the COO and gives everyone a sense of ownership over the meeting process.
COO 使用原则
COO Principles
- 个人承诺要具体到「别人能判断你做没做完」，COO 先示范这个标准。
- 25 分钟是硬约束。超时意味着问题没提前分流，不是大家话太多。
- 例会超时的解法：提前建「需要决策」列表，分流到会后或 1:1。
- Individual commitments must be specific enough that "others can judge if you've completed them"; the COO should demonstrate this standard first.
- 25 minutes is a hard constraint. Going over time means issues weren't diverted in advance, not that people are talking too much.
- Solution for overtime meetings: Create a "needs decision" list in advance and divert items to post-meeting or 1:1s.
第三层：一对一会议 — 个人层
Layer 3: One-on-One Meetings — Individual Layer
设计哲学
Design Philosophy
1:1 是这套体系里信息密度最高也最难做好的部分。它不是向下传达信息的渠道，是让 COO 真正知道每个人「卡在哪一层」的窗口。
卡层诊断框架：信息不够 / 权限不够 / 协作不顺 / 能力边界 / 方向不清。不同的卡层对应完全不同的解法，混淆了会白费功夫。
1:1s are the most information-dense and hardest part of this system. They aren't a channel for top-down communication — they're a window for the COO to truly understand where each person is "stuck."
Stuck Layer Diagnostic Framework: Insufficient information / Insufficient authority / Poor collaboration / Capacity boundaries / Unclear direction. Different stuck layers require completely different solutions; mixing them up is a waste of effort.
一、量化脉搏（5 分钟）
I. Quantified Pulse (5 Minutes)
每项 1-5 分（1=很糟 / 3=普通可接受 / 5=非常好）：
| 维度 | 说明 |
|---|---|
| 能量（精力状态） | |
| 目标清晰度 | 最重要的 1-2 件事是什么、成功长什么样 |
| 使命认同 | 工作和公司方向之间的连接感 |
| 自主与支持 | 决策空间 vs 所需支持的匹配度 |
| 成长感 | |
| 节奏可持续性 | 再持续 1 个月扛得住吗 |
| 心流时间 | 深度工作的时长与质量 |
| 技术成长 | |
| 工具与开发体验 |
量化脉搏的意义不在于精确，而在于趋势。连续三周某人「节奏可持续性」都给 2 分，比某次给 1 分更值得警惕。建议 COO 把历史数据记下来，1:1 开头先回顾上次。
Score each item 1-5 (1=Terrible / 3=Acceptable / 5=Excellent):
| Dimension | Description |
|---|---|
| Energy (Energy State) | |
| Goal Clarity | What are the 1-2 most important things, and what does success look like? |
| Mission Alignment | Sense of connection between work and company direction |
| Autonomy vs. Support | Match between decision-making space and required support |
| Sense of Growth | |
| Sustainability of Rhythm | Can you keep this up for another month? |
| Flow Time | Duration and quality of deep work |
| Technical Growth | |
| Tools & Development Experience |
The point of the quantified pulse isn't precision, but trend. If someone gives "Sustainability of Rhythm" a 2 for three consecutive weeks, that's more concerning than a single 1. It's recommended that the COO record historical data and review the previous scores at the start of each 1:1.
二、深度展开问题库（15-20 分钟，选 3-4 个）
II. Deep Dive Question Bank (15-20 Minutes, Choose 3-4)
关于工作本身
- 这两周最有成就感的一件事是什么？为什么？
- 最让你卡壳的一件事是什么？卡在哪一层——信息 / 权限 / 协作 / 能力 / 方向？
- 你花时间最多的事 = 你认为最高杠杆的事吗？差距在哪？
- 如果下周可以砍掉一项工作，你会砍哪个？为什么没砍？
关于决策与担当
- 有没有事你其实可以自己拍板、但来问了我？为什么？
- 有没有「明显该做但没人在做」的事？
- 反过来，有没有你自己拍了但事后觉得该先对齐的？
关于坦诚（最难问，也最值得问）
- 这段时间有没有「想说但没说」的事？
- 团队里有没有正在悄悄发生问题、但还没被讨论的事？
- 我做的什么决定你不理解或不同意？
关于成长
- 这个月你在哪个能力上明确变强了？怎么证明？
- 接下来 90 天最想刻意练习的能力是什么？需要什么资源？
- 现在的工具链 / 代码库 / LLM 工作流，哪一处最拖后腿？
关于人和组织
- 团队里最愿意请教 / 协作的人是谁？最难协作的是谁？为什么？
- 如果你是 CEO，明天会立刻改一件什么事？
About Work Itself
- What's the most fulfilling thing you've done in the past two weeks? Why?
- What's the thing that's been blocking you the most? Which layer are you stuck on — information / authority / collaboration / capacity / direction?
- Is the work you spend the most time on = the work you think has the highest leverage? What's the gap?
- If you could cut one task next week, which one would it be? Why haven't you cut it yet?
About Decision-Making & Accountability
- Is there anything you could have decided on your own but came to ask me about? Why?
- Is there anything that "obviously needs to be done but no one is doing it"?
- Conversely, is there anything you decided on your own but later thought you should have aligned first?
About Candor (Hardest to ask, but most valuable)
- Is there anything you've "wanted to say but haven't" lately?
- Is there any issue quietly brewing in the team that hasn't been discussed yet?
- What decision of mine do you not understand or disagree with?
About Growth
- Which skill have you clearly improved this month? How can you prove it?
- What skill do you most want to deliberately practice in the next 90 days? What resources do you need?
- Which part of the current toolchain / codebase / LLM workflow holds you back the most?
About People & Organization
- Who in the team do you most want to consult / collaborate with? Who is the hardest to collaborate with? Why?
- If you were the CEO, what's one thing you would change immediately tomorrow?
三、双向反馈（5-10 分钟）
III. Bilateral Feedback (5-10 Minutes)
「他 → 我」那部分不能跳过——你收到的反馈质量，决定了你能改进的速度。
| 方向 | 问题 |
|---|---|
| 他 → 我 | 我做的什么最有帮助（继续做）/ 我做的什么让你更难（停止做）/ 我应该开始做什么 |
| 我 → 他 | 你做得很好的地方 / 你需要调整的地方 / 我对你接下来 1 周的一个具体期待 |
The "Them → Me" part cannot be skipped — the quality of feedback you receive determines how fast you can improve.
| Direction | Questions |
|---|---|
| Them → Me | What have I done that's most helpful (keep doing it)? / What have I done that makes your job harder (stop doing it)? / What should I start doing? |
| Me → Them | What you're doing well / What you need to adjust / One specific expectation I have for you in the next week |
COO 使用原则
COO Principles
- 量化脉搏的分数是开门的钥匙，不是评分。「2 分」要问为什么。
- 先示范坦诚——说出自己某个决定被质疑了，才有人愿意说真话。
- 1:1 结束时必须有 Action Items，哪怕只有一条。没有 action 的 1:1 会让人觉得只是说说而已。
- The quantified pulse scores are a key to opening the conversation, not a rating. Ask "Why the 2?" when someone gives a low score.
- Demonstrate candor first — share that one of your decisions was questioned, and then others will be willing to speak the truth.
- There must be Action Items at the end of the 1:1, even just one. A 1:1 without action makes people feel like it was just talk.
常见卡点解法
Common Blocker Solutions
Standup 没人认真写？
先检查自己的 standup 是不是够具体。含糊传染，具体也传染。公开表扬一条好的，不批评差的。
例会变成进度汇报？
把「这周做了什么」改成「上周你承诺的 X 做到了吗」。是/否比进度汇报更有张力，也更短。
1:1 对方总说「还好」？
检查自己有没有创造过「说真话不会被惩罚」的证据。这件事需要用几次真实案例建立信任，不是靠一个好问题。
团队规模大了，没精力做每个人 1:1？
每两周一次即可。先把量化脉搏教给 tech lead 或 line manager，COO 保留「脉搏异常」的升级通道。
No one writes standups seriously?
First check if your own standup is specific enough. Vagueness is contagious, and so is specificity. Publicly praise a good one, don't criticize bad ones.
Weekly meetings turn into progress reports?
Change "What did you do this week?" to "Did you fulfill the X you committed to last week?" A yes/no answer is more impactful and shorter than a progress report.
The other person always says "I'm fine" in 1:1s?
Check if you've created evidence that "speaking the truth won't be punished." This requires building trust through real cases, not just asking a good question.
Team has grown too large to do 1:1s with everyone?
Do them every two weeks instead. First teach the quantified pulse to tech leads or line managers, and the COO retains an escalation channel for "abnormal pulse" cases.
输出格式建议
Recommended Output Format
当用户问到具体场景时，优先给：
- 诊断：当前卡在哪一层（信息 / 对齐 / 个人）
- 一个立刻能用的动作：具体到「今天就能做」
- 防止反弹的护栏：一两条 COO 需要先做到的前置条件
不要给通用的「建议加强沟通」，要给「把这个问题从例会板块挪到 1:1，因为它需要的是……」这种具体的操作建议。
When users ask about specific scenarios, prioritize providing:
- Diagnosis: Which layer is currently stuck (information / alignment / individual)
- An immediately actionable step: Specific enough that "you can do it today"
- Guardrails to prevent regression: 1-2 prerequisites the COO must fulfill first
Don't give generic advice like "strengthen communication"; give specific operational suggestions like "move this issue from the weekly meeting segment to a 1:1 because it requires..."