team-dynamics
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTeam Dynamics & Leadership Skill
团队动态与领导力技能
Purpose
目的
Provide engineering managers with actionable frameworks, templates, and guidance for building high-performing teams, running effective 1-on-1s, delegating effectively, and developing psychological safety.
为工程经理提供可落地的框架、模板和指导,帮助他们打造高绩效团队、开展有效的一对一沟通、高效委派任务并建立心理安全感。
Primary Bond
核心关联
Agent: team-leadership-agent
Relationship: This skill provides the foundational templates and frameworks that the team-leadership-agent uses to guide managers.
Agent: team-leadership-agent
关联关系: 本技能为team-leadership-agent提供基础模板和框架,用于指导经理开展工作。
Templates
模板
1-on-1 Meeting Template
一对一沟通会议模板
yaml
one_on_one_meeting:
duration: "30-60 min"
frequency: "Weekly recommended"
structure:
opening:
duration: "5 min"
focus:
- "Personal check-in"
- "Energy/mood assessment"
- "Their agenda items"
their_agenda:
duration: "15-20 min"
questions:
- "What's on your mind?"
- "What's blocking you?"
- "What wins to celebrate?"
- "What do you need from me?"
development:
duration: "10 min"
topics:
- "Progress on goals"
- "Skill development"
- "Career conversation"
feedback:
duration: "5-10 min"
bidirectional:
- "Manager to report"
- "Report to manager"
closing:
duration: "5 min"
outputs:
- "Action items documented"
- "Next meeting focus"
- "Support committed"yaml
one_on_one_meeting:
duration: "30-60 min"
frequency: "Weekly recommended"
structure:
opening:
duration: "5 min"
focus:
- "Personal check-in"
- "Energy/mood assessment"
- "Their agenda items"
their_agenda:
duration: "15-20 min"
questions:
- "What's on your mind?"
- "What's blocking you?"
- "What wins to celebrate?"
- "What do you need from me?"
development:
duration: "10 min"
topics:
- "Progress on goals"
- "Skill development"
- "Career conversation"
feedback:
duration: "5-10 min"
bidirectional:
- "Manager to report"
- "Report to manager"
closing:
duration: "5 min"
outputs:
- "Action items documented"
- "Next meeting focus"
- "Support committed"Delegation Framework (RACI)
任务委派框架(RACI)
yaml
delegation_levels:
L1_direct:
authority: "Full decision authority"
support: "Available on request"
check_in: "Weekly"
use_when: "Experienced, proven track record"
L2_coach:
authority: "Decision authority with input"
support: "Proactive guidance"
check_in: "Bi-weekly"
use_when: "Growing, needs development"
L3_supervise:
authority: "Recommendation only"
support: "Active supervision"
check_in: "Daily"
use_when: "New to task, learning"
L4_control:
authority: "Execution only"
support: "Continuous oversight"
check_in: "Real-time"
use_when: "Critical task, new team member"
delegation_handoff_checklist:
- "Define outcome clearly (what done looks like)"
- "Explain context and why"
- "Clarify authority level (L1-L4)"
- "Set check-in schedule"
- "Confirm understanding"
- "Document decision rights"yaml
delegation_levels:
L1_direct:
authority: "Full decision authority"
support: "Available on request"
check_in: "Weekly"
use_when: "Experienced, proven track record"
L2_coach:
authority: "Decision authority with input"
support: "Proactive guidance"
check_in: "Bi-weekly"
use_when: "Growing, needs development"
L3_supervise:
authority: "Recommendation only"
support: "Active supervision"
check_in: "Daily"
use_when: "New to task, learning"
L4_control:
authority: "Execution only"
support: "Continuous oversight"
check_in: "Real-time"
use_when: "Critical task, new team member"
delegation_handoff_checklist:
- "Define outcome clearly (what done looks like)"
- "Explain context and why"
- "Clarify authority level (L1-L4)"
- "Set check-in schedule"
- "Confirm understanding"
- "Document decision rights"Team Health Assessment
团队健康评估
yaml
team_health_pulse:
dimensions:
psychological_safety:
questions:
- "I can speak up without fear"
- "Mistakes are learning opportunities"
- "I can ask 'dumb' questions"
scale: "1-5"
target: ">4.0"
clarity:
questions:
- "I know what's expected of me"
- "Team goals are clear"
- "My role is well-defined"
scale: "1-5"
target: ">4.0"
collaboration:
questions:
- "Team members help each other"
- "Information flows freely"
- "Conflicts are resolved constructively"
scale: "1-5"
target: ">4.0"
engagement:
questions:
- "I feel valued"
- "My work is meaningful"
- "I have growth opportunities"
scale: "1-5"
target: ">4.0"
interpretation:
excellent: ">4.5"
good: "4.0-4.4"
concerning: "3.5-3.9"
critical: "<3.5"
cadence: "Monthly pulse, Quarterly deep-dive"yaml
team_health_pulse:
dimensions:
psychological_safety:
questions:
- "I can speak up without fear"
- "Mistakes are learning opportunities"
- "I can ask 'dumb' questions"
scale: "1-5"
target: ">4.0"
clarity:
questions:
- "I know what's expected of me"
- "Team goals are clear"
- "My role is well-defined"
scale: "1-5"
target: ">4.0"
collaboration:
questions:
- "Team members help each other"
- "Information flows freely"
- "Conflicts are resolved constructively"
scale: "1-5"
target: ">4.0"
engagement:
questions:
- "I feel valued"
- "My work is meaningful"
- "I have growth opportunities"
scale: "1-5"
target: ">4.0"
interpretation:
excellent: ">4.5"
good: "4.0-4.4"
concerning: "3.5-3.9"
critical: "<3.5"
cadence: "Monthly pulse, Quarterly deep-dive"Conflict Resolution Protocol
冲突解决流程
yaml
conflict_resolution:
step_1_assess:
- "Identify conflict type (interpersonal vs task)"
- "Determine urgency and impact"
- "Gather facts (not opinions)"
step_2_individual:
- "Meet with each party separately"
- "Listen without judgment"
- "Understand interests (not positions)"
- "Document key points"
step_3_joint:
- "Facilitate joint session"
- "Establish ground rules"
- "Focus on interests, not positions"
- "Generate options together"
step_4_resolve:
- "Agree on solution"
- "Document commitments"
- "Set follow-up date"
- "Communicate to team if needed"
escalation_triggers:
- "No progress after 2 joint sessions"
- "Policy or legal concerns"
- "Harassment or discrimination"
- "Safety concerns"yaml
conflict_resolution:
step_1_assess:
- "Identify conflict type (interpersonal vs task)"
- "Determine urgency and impact"
- "Gather facts (not opinions)"
step_2_individual:
- "Meet with each party separately"
- "Listen without judgment"
- "Understand interests (not positions)"
- "Document key points"
step_3_joint:
- "Facilitate joint session"
- "Establish ground rules"
- "Focus on interests, not positions"
- "Generate options together"
step_4_resolve:
- "Agree on solution"
- "Document commitments"
- "Set follow-up date"
- "Communicate to team if needed"
escalation_triggers:
- "No progress after 2 joint sessions"
- "Policy or legal concerns"
- "Harassment or discrimination"
- "Safety concerns"Decision Trees
决策树
When to Delegate
何时委派任务
Task arrives
|
+-- Is this strategic/confidential?
| +-- Yes -> Keep it
| +-- No -> Continue
|
+-- Does someone else have better skills?
| +-- Yes -> Delegate to them
| +-- No -> Continue
|
+-- Is this a growth opportunity?
| +-- Yes -> Delegate with L2/L3 support
| +-- No -> Continue
|
+-- Do I have capacity?
+-- Yes -> Consider keeping, but still evaluate delegation
+-- No -> Must delegate, find right person收到任务
|
+-- 是否为战略/机密任务?
| +-- 是 -> 自行处理
| +-- 否 -> 继续
|
+-- 是否有其他人更擅长此项任务?
| +-- 是 -> 委派给该人员
| +-- 否 -> 继续
|
+-- 是否为员工成长机会?
| +-- 是 -> 以L2/L3支持级别委派
| +-- 否 -> 继续
|
+-- 我是否有时间处理?
+-- 是 -> 考虑自行处理,但仍需评估是否委派
+-- 否 -> 必须委派,找到合适人选1-on-1 Frequency Decision
一对一沟通频率决策
Team Member Situation
|
+-- New to role (<3 months)
| +-- Weekly, 45-60 min
|
+-- Struggling or PIP
| +-- Weekly or bi-weekly, 45 min
|
+-- Solid performer
| +-- Bi-weekly, 30 min
|
+-- High performer, autonomous
+-- Bi-weekly or monthly, 30 min
+-- But always available on request团队成员情况
|
+-- 新入职(<3个月)
| +-- 每周一次,45-60分钟
|
+-- 表现不佳或处于绩效改进计划(PIP)中
| +-- 每周或每两周一次,45分钟
|
+-- 表现稳定
| +-- 每两周一次,30分钟
|
+-- 高绩效、自主能力强
+-- 每两周或每月一次,30分钟
+-- 但需始终保持按需沟通的开放态度Anti-Patterns
反模式
yaml
anti_patterns:
micromanagement:
symptoms:
- "Checking in multiple times daily"
- "Redoing delegated work"
- "Requiring approval for small decisions"
remedy:
- "Focus on outcomes, not tasks"
- "Set clear success criteria upfront"
- "Trust and verify, don't hover"
absentee_manager:
symptoms:
- "Skipping 1-on-1s regularly"
- "Not knowing team's blockers"
- "Surprised by performance issues"
remedy:
- "Protect 1-on-1 time as sacred"
- "Weekly team check-ins"
- "Daily async standups"
conflict_avoidance:
symptoms:
- "Letting issues fester"
- "Not giving tough feedback"
- "Hoping problems resolve themselves"
remedy:
- "Address within 48 hours"
- "Use SBI feedback model"
- "Document and follow up"yaml
anti_patterns:
micromanagement:
symptoms:
- "Checking in multiple times daily"
- "Redoing delegated work"
- "Requiring approval for small decisions"
remedy:
- "Focus on outcomes, not tasks"
- "Set clear success criteria upfront"
- "Trust and verify, don't hover"
absentee_manager:
symptoms:
- "Skipping 1-on-1s regularly"
- "Not knowing team's blockers"
- "Surprised by performance issues"
remedy:
- "Protect 1-on-1 time as sacred"
- "Weekly team check-ins"
- "Daily async standups"
conflict_avoidance:
symptoms:
- "Letting issues fester"
- "Not giving tough feedback"
- "Hoping problems resolve themselves"
remedy:
- "Address within 48 hours"
- "Use SBI feedback model"
- "Document and follow up"Quick Reference Cards
快速参考卡
SBI Feedback Model
SBI反馈模型
Situation: "In yesterday's standup..."
Behavior: "When you interrupted Sarah..."
Impact: "It made her hesitant to share ideas..."情境(Situation):"在昨天的站会上..."
行为(Behavior):"当你打断Sarah时..."
影响(Impact):"这让她不敢分享想法..."GROW Coaching Model
GROW教练模型
Goal: "What do you want to achieve?"
Reality: "Where are you now?"
Options: "What could you do?"
Will: "What will you do?"目标(Goal):"你想要达成什么目标?"
现状(Reality):"你目前处于什么状态?"
方案(Options):"你可以采取哪些行动?"
意愿(Will):"你接下来会做什么?"Tuckman's Stages
塔克曼团队发展阶段
Forming -> Storming -> Norming -> Performing -> Adjourning
| | | | |
Polite Conflict Standards High-perf Transition形成期(Forming)-> 动荡期(Storming)-> 规范期(Norming)-> 执行期(Performing)-> 解散期(Adjourning)
| | | | |
礼貌相处 冲突频发 建立标准 高绩效产出 过渡阶段Troubleshooting
问题排查
| Problem | Root Cause | Solution |
|---|---|---|
| 1-on-1s feel awkward | No agenda, manager talks too much | Use template, listen 80% |
| Delegation fails | Unclear expectations | Use handoff checklist |
| Team silent in meetings | Low psychological safety | Leader vulnerability, invite input |
| Constant escalations | Over-delegation to wrong level | Match task to L1-L4 level |
| 问题 | 根本原因 | 解决方案 |
|---|---|---|
| 一对一沟通氛围尴尬 | 无会议议程,经理讲话过多 | 使用模板,80%时间用于倾听 |
| 任务委派失败 | 期望不明确 | 使用交接检查清单 |
| 团队成员在会议中沉默 | 心理安全感低 | 领导者展现脆弱性,主动邀请成员发言 |
| 问题持续升级 | 委派级别与任务不匹配 | 根据L1-L4级别匹配任务 |
Validation Rules
验证规则
yaml
input_validation:
team_size:
type: integer
min: 1
max: 50
required: false
situation:
type: string
min_length: 10
required: true
urgency:
type: enum
values: [low, medium, high, critical]
default: mediumyaml
input_validation:
team_size:
type: integer
min: 1
max: 50
required: false
situation:
type: string
min_length: 10
required: true
urgency:
type: enum
values: [low, medium, high, critical]
default: mediumResources
参考资源
Books:
- The Manager's Path - Camille Fournier
- Radical Candor - Kim Scott
- Turn the Ship Around - David Marquet
- High Output Management - Andy Grove
Research:
- Google's Project Aristotle (psychological safety)
- Gallup Q12 engagement research
书籍:
- The Manager's Path - Camille Fournier
- Radical Candor - Kim Scott
- Turn the Ship Around - David Marquet
- High Output Management - Andy Grove
研究:
- Google's Project Aristotle(心理安全感相关)
- Gallup Q12敬业度研究