🌍
Language:
Chinese |
English |
Japanese |
Korean
Team Motivation Playbook
The 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.
Layer 1: Daily Standup — Information Layer
Design Philosophy
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)
- 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
Good Standup Sample
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 tonight
COO Principles
- 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.
Agenda Structure (Strict 25-Minute Time Limit)
| 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 Mechanism
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 Principles
- 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: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.
I. Quantified Pulse (5 Minutes)
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.
II. Deep Dive Question Bank (15-20 Minutes, Choose 3-4)
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?
III. Bilateral Feedback (5-10 Minutes)
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 Principles
- 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
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
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..."