Tuckman's Stages of Team Development
Bruce Tuckman identified five stages that every team passes through. Understanding where your team is helps you apply the right leadership style and set appropriate expectations.
| Stage | Team Behavior | Leader Role | Duration |
|---|---|---|---|
| Forming | Polite, cautious, testing boundaries | Direct: set expectations, provide structure | 1-2 weeks |
| Storming | Conflict, disagreements, power struggles | Coach: facilitate resolution, normalize conflict | 2-4 weeks |
| Norming | Establishing shared norms, building trust | Support: reinforce good patterns, step back | 2-4 weeks |
| Performing | High productivity, autonomous, collaborative | Delegate: remove obstacles, let team lead | Ongoing |
| Adjourning | Project ending, sadness, reflection | Celebrate: recognize achievements, facilitate transition | 1-2 weeks |
Psychological Safety
Google's Project Aristotle found that psychological safety is the #1 predictor of high-performing teams. It means team members feel safe to take risks, admit mistakes, ask questions, and challenge ideas without fear of punishment or humiliation.
Building Psychological Safety
- Model Vulnerability: As a leader, admit your own mistakes first. "I was wrong about X" opens the door.
- Respond to Mistakes with Curiosity: "What happened?" instead of "Who did this?" creates learning, not blame.
- Encourage Dissent: Actively ask for opposing viewpoints. "Who sees this differently?" or "What could go wrong?"
- Celebrate Learning: Recognize when someone catches a bug, asks a good question, or admits they need help.
- Blameless Post-Mortems: Focus on systems and processes that failed, not individuals.
Conflict Resolution
// Conflict Resolution Framework
interface ConflictResolution {
style: string;
approach: string;
whenToUse: string;
whenToAvoid: string;
}
const conflictStyles: ConflictResolution[] = [
{
style: 'Collaborating (Win-Win)',
approach: 'Work together to find a solution that satisfies all parties',
whenToUse: 'When both concerns are too important to compromise',
whenToAvoid: 'When time pressure makes lengthy discussion impossible'
},
{
style: 'Compromising (Lose-Lose)',
approach: 'Each party gives up something to reach a middle ground',
whenToUse: 'When a quick resolution is needed and both sides have valid points',
whenToAvoid: 'When one side is clearly right (compromising truth is dangerous)'
},
{
style: 'Accommodating (Lose-Win)',
approach: 'Yield to the other party to preserve the relationship',
whenToUse: 'When the issue matters more to the other person',
whenToAvoid: 'When your position is correct and important for the project'
},
{
style: 'Competing (Win-Lose)',
approach: 'Assert your position at the expense of others',
whenToUse: 'Emergency decisions, safety issues, non-negotiable standards',
whenToAvoid: 'Routine disagreements (damages relationships and trust)'
},
{
style: 'Avoiding (Lose-Lose)',
approach: 'Sidestep or postpone the conflict',
whenToUse: 'When emotions are too high, cooling off is needed',
whenToAvoid: 'When the issue will only get worse if ignored'
}
];
// 1:1 Meeting Framework
interface OneOnOneTemplate {
frequency: string;
duration: string;
agenda: {
section: string;
timeMinutes: number;
questions: string[];
}[];
}
const oneOnOneTemplate: OneOnOneTemplate = {
frequency: 'Weekly',
duration: '30 minutes',
agenda: [
{
section: 'Check-In',
timeMinutes: 5,
questions: [
'How are you doing overall? (Not just work)',
'How is your energy/motivation level this week?'
]
},
{
section: 'Their Agenda',
timeMinutes: 10,
questions: [
'What is on your mind?',
'What do you want to discuss today?',
'Any blockers or frustrations?'
]
},
{
section: 'Project/Work Discussion',
timeMinutes: 10,
questions: [
'How is the current sprint going?',
'Is there anything you are stuck on?',
'Do you have the support you need?'
]
},
{
section: 'Growth and Development',
timeMinutes: 5,
questions: [
'What skill do you want to develop this quarter?',
'Is there a project you would like to lead?',
'Any feedback for me on how I can support you better?'
]
}
]
};Motivation Theories for PMs
| Theory | Key Insight | Application for PMs |
|---|---|---|
| Herzberg's Two-Factor | Hygiene factors prevent dissatisfaction; motivators create satisfaction | Good salary prevents complaints; challenging work creates engagement |
| Maslow's Hierarchy | Lower needs (safety, belonging) must be met before higher needs (growth) | Job security and team belonging must exist before expecting innovation |
| McGregor Theory X/Y | Theory X: people need control. Theory Y: people are self-motivated. | Treat engineers as Theory Y — trust, autonomy, purpose |
| Pink's Drive | Intrinsic motivation comes from Autonomy, Mastery, Purpose | Give teams choice in how they work, opportunities to grow, and connect work to meaning |
Servant Leadership in Practice
- Ask, Do Not Tell: "What do you think we should do?" instead of "Do it this way."
- Remove Obstacles: Your job is to make the team's job easier. What is slowing them down?
- Shield the Team: Protect the team from organizational politics, unnecessary meetings, and interruptions.
- Develop People: The measure of a servant leader is whether the people they serve grow.
- Give Credit, Take Blame: When things go well, credit the team. When things go wrong, own it as the leader.