Team Motivation Operating Manual
The underlying logic of this system: freedom and responsibility are one. Standup is to make people think clearly, the weekly meeting is to align people, and 1:1 is to make people feel seen. If these three things are done well, motivation is not managed into existence; it grows.
Applicable scenarios: COO or team lead at an AI technology company, team size 3-30 people, high autonomy, remote or semi-remote.
Boundary with the product, engineering, and operations SOP: This Skill diagnoses individual status, information, and alignment; requirement prioritization, bugs, iteration scope, and release gates are handed to gr-product-dev-ops. Only issues found in 1:1s that enter Action Items with a clear owner, deadline, and verification method count as closed-loop.
Layer 1: Daily Standup — Information Layer
Design Philosophy
The essence of Standup is not reporting; it is a ritual that forces you to think clearly. If you can write it out, it means you have really thought it through; if you cannot write it out, it is usually because you yourself have not figured out what you are going to do today.
Vagueness is contagious — the COO's own standup must be written well first; the pattern permeates from top to bottom.
Standard Format (three required items)
- What was done today: specific deliverables, do not write "continue development"
- What to do tomorrow: specific enough that others can judge whether you finished it
- What difficulties were encountered / what to talk about tonight: blockers, things with unclear ownership
Good Standup Sample
今天做了什么
- 把 XX 接口写完，本地 50 条数据跑通，平均 80ms，比上一版快一倍
- 帮队友定位 WhatsApp 会话列表渲染卡顿，根源是没做虚拟滚动，指了 react-window 方案，他十分钟搞定
- 实话实说，下午摸鱼了一小时，顺手把竞品新发的 case study 存进竞品库，算将功补过
明天要做什么
- 把批量报价接口推上 staging，拿真实场景跑一遍
- 补今天没写的接口文档
遇到什么困难 / 晚上要聊
- XXX 架构决策还没拍板，影响我这边进度，想今晚对一下
COO Usage Principles
- Do not require perfection; require honesty. If you slacked off, write that you slacked off, but clearly write what you did besides slacking off.
- Do not criticize short standups, but follow up with "what specifically did you deliver today." The problem is specificity, not length.
- Publicly praise a good standup; do not criticize a bad one. Specificity is also contagious.
- A good standup is a gift to teammates; this understanding must be repeated over and over.
Layer 2: Weekly Meeting — Alignment Layer
Design Philosophy
The weekly meeting is not a progress report meeting. What it solves is "presence" — letting everyone know where the company as a whole is, and letting everyone publicly state what they have committed to. Neither of these things can be completed asynchronously.
Agenda Structure (25 minutes, strictly timed)
| Segment | Duration | Content |
|---|---|---|
| Company segment | 8 minutes | Current progress / plan for the coming week / matters requiring team decisions |
| Individual segment | About 3 minutes per person | Whether last week's commitments were met / 1-3 specific commitments for this week / what help is needed from the team / current state (0-10 score) |
| Collective discussion | Remaining time | Discuss collectively after individuals finish sharing; issues that need 1:1 are moved to a separate chat after the meeting |
"Current state 0-10 score" cannot be omitted. It is the only channel that lets a person express how they feel right now without explanation. Follow up on low scores, but do not dig deep publicly; switch to 1:1 follow-up.
Scrum Master Mechanism
Rotate weekly; the responsibility is to maintain speaking order and time pacing. The rotation system reduces dependence on the COO and gives everyone a sense of ownership over the meeting process.
COO Usage Principles
- Personal commitments must be specific enough that "others can judge whether you finished it." The COO should demonstrate this standard first.
- 25 minutes is a hard constraint. Overrunning means the issues were not triaged in advance, not that everyone talked too much.
- The solution to meeting overruns: build a "needs decision" list in advance, and route items to after the meeting or to 1:1s.
Third layer: one-on-one meetings — the individual layer
Design philosophy
1:1s are the part of this system with the highest information density and the hardest to do well. They are not a channel for cascading information downward; they are the window that lets the COO truly know which layer each person is "stuck at."
Stuck-layer diagnostic framework: insufficient information / insufficient authority / poor collaboration / capability boundary / unclear direction. Different stuck layers correspond to completely different solutions; confusing them wastes effort.
1. Quantitative pulse (5 minutes)
Each item is scored 1-5 (1 = very bad / 3 = ordinary, acceptable / 5 = very good):
| Dimension | Description |
|---|---|
| Energy (state of vitality) | |
| Goal clarity | What are the most important 1-2 things, and what does success look like |
| Mission identification | The sense of connection between the work and the company's direction |
| Autonomy and support | The match between decision-making space and the support needed |
| Sense of growth | |
| Pace sustainability | Can you keep this up for another month? |
| Flow time | The duration and quality of deep work |
| Technical growth | |
| Tools and development experience |
The point of the quantitative pulse is not precision, but trend. If someone gives a 2 on "pace sustainability" for three weeks in a row, that is more alarming than a single 1. It is recommended that the COO record historical data and review the last session at the start of the 1:1.
2. Deep-dive question bank (15-20 minutes, choose 3-4)
About the work itself
- What was the most fulfilling thing in the past two weeks? Why?
- What has stumped you the most? Which layer is it stuck at — information / authority / collaboration / capability / direction?
- Is the thing you spend the most time on = the thing you think is highest leverage? Where is the gap?
- If you could cut one piece of work next week, which would you cut? Why hasn't it been cut?
About decisions and ownership
- Is there anything you could actually have decided yourself but came to ask me about? Why?
- Is there anything that "clearly should be done but no one is doing"?
- Conversely, is there anything you decided yourself but afterward felt should have been aligned on first?
About candor(The hardest to ask, and the most worth asking)
- Has there been anything recently that you "wanted to say but didn't"?
- Is there anything in the team where problems are quietly occurring but have not yet been discussed?
- What decisions I made do you not understand or disagree with?
About growth
- In which capability have you clearly become stronger this month? How do you prove it?
- What capability do you most want to deliberately practice in the next 90 days? What resources do you need?
- In the current toolchain / codebase / LLM workflow, which part is the biggest drag?
About people and organization
- Who in the team are you most willing to consult / collaborate with? Who is the hardest to collaborate with? Why?
- If you were CEO, what one thing would you change immediately tomorrow?
III. Two-way feedback (5–10 minutes)
The "him → me" part cannot be skipped—the quality of the feedback you receive determines how fast you can improve.
| Direction | Question |
|---|---|
| Him → Me | What I did that was most helpful (keep doing) / What I did that made things harder for you (stop doing) / What I should start doing |
| Me → Him | What you did well / What you need to adjust / One specific expectation I have for you in the next week |
Principles for COO use
- The quantified pulse score is the key that opens the door, not a rating. For a "2," ask why.
- Model candor first—only after you say that one of your own decisions was questioned will others be willing to tell the truth.
- A 1:1 must end with Action Items, even if there is only one. A 1:1 with no action makes people feel it was just talk.
Solutions to common blockers
No one writes standup seriously? First check whether your own standup is specific enough. Vagueness is contagious, and so is specificity. Publicly praise a good one; don't criticize a bad one.
Does the regular meeting turn into a progress report? Change "what did you do this week" to "did you accomplish X that you committed to last week?" Yes/no has more tension than a progress report, and it's shorter.
Does the other person always say "fine" in 1:1s? Check whether you have ever created evidence that "telling the truth won't be punished." This takes several real cases to build trust, not one good question.
As the team gets bigger, do you not have the energy to do 1:1s with everyone? Once every two weeks is enough. First teach the quantified pulse to the tech lead or line manager, and have the COO keep the escalation channel for "abnormal pulse."
Suggested output format
When the user asks about a specific scenario, prioritize giving:
- Diagnosis: Which layer is currently stuck (information / alignment / individual)
- One action usable immediately: Specific enough to "do today"
- Guardrails to prevent rebound: One or two prerequisites the COO needs to meet first
Don't give generic "strengthen communication" advice; give specific operational advice like "move this issue from the regular meeting section to the 1:1, because what it needs is…"