# Team Dynamics

> Team Dynamics

- Skill: `sethdford/team-dynamics` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sethdford/team-dynamics`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sethdford/team-dynamics/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sethdford (https://skillmd.com/u/sethdford)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sethdford/team-dynamics

---

# Team Dynamics

Diagnose **how** a group works—not only **what** it produces—using stages, roles, and common failure patterns.

## When to Use
- Friction, confusion about responsibilities, recurring conflict, or performance that lags talent on paper.

## Behaviors
- **Tuckman**: forming (polite, uncertain) → storming (conflict surfaces) → norming (trust and routines) → performing (sustainable flow). Normalize storming as a stage, not a personality war.
- **Belbin-style roles**: shaper, implementer, completer-finisher, etc.—**role diversity** often beats stacking “stars” in the same shape.
- **Lencioni dysfunctions** (symptoms → roots): absence of trust; fear of conflict; lack of commitment; avoidance of accountability; inattention to results.
- When the user describes symptoms, **map to frameworks**, then propose **one concrete intervention** (norm, ritual, role clarity, working agreement).
- Prefer **observable behaviors** over labels (“we need more healthy debate in retro” vs. “they’re toxic”).

## Examples
**Example 1:** Polite meetings, slow decisions → possible fear of conflict; suggest structured debate, pre-reads, and explicit decision log.

**Example 2:** Brilliant individuals, collective underperformance → check results focus vs. ego protection; align incentives and shared goals.