Laws of Software Engineering · Principle
Principle
Hackman's Five Conditions for Effective Teams
Teams perform when they are real teams, with compelling direction, enabling structures, supportive context, and expert coaching.
How to use it. Use the five as a diagnostic before launching a team. Most teams fail on the first two conditions. Either they are not really teams (membership unclear, dependencies tangled), or the direction is muddy.
How it gets misused. Treated as a checklist. Hackman's work is about the combination of conditions and the time they take to develop. Teams take months to develop. Ticking the boxes early and assuming the team is ready is a common failure mode.
Related
-
Pattern
Team Topologies
Four kinds of team (working on a stream of value, building a platform, helping others, or owning something complicated). Three ways teams can interact (working together, providing a service, or helping someone learn).
- Principle Psychological Safety The shared belief that you can speak up, ask questions, admit mistakes, and disagree without being punished or humiliated.
- Pattern Dynamic Reteaming Teams change shape over time. People join, leave, split, and merge. Treat reteaming as a normal practice.
Clusters
- The Team Design cluster - How to organise people for software work.