Brooks' Law
Adding manpower to a late software project often makes it even later.
Brooks' Law was formulated by Fred Brooks in his 1975 book "The Mythical Man-Month". The law highlights a classic project management dilemma: adding developers to a late software project often delays it further. This is primarily due to two factors: ramp-up time and communication overhead. New hires require time from existing team members to get up to speed, which temporarily reduces overall productivity. Furthermore, the number of communication channels increases exponentially with each added person following the formula n(n-1)/2. While three people have three communication channels, ten people require 45 channels. Finally, complex tasks are rarely fully partitionable; as Brooks famously noted, "Nine women cannot make a baby in one month, no matter how many you assign to the task."
Imagine a restaurant kitchen running behind on orders. If the head chef pushes five new cooks into the cramped kitchen, the original staff must stop working to explain recipes and ingredient locations. The cooks end up bumping into each other, delaying service even more.
The law challenges our intuitive belief that work behaves like an assembly line in a factory. It highlights how complex knowledge work differs from manual assembly and why communication is often the primary bottleneck in modern projects.
A common misconception is that adding people never helps. The law specifically applies when a project is already late and tasks cannot easily be partitioned.
Identify a task in your daily life or workplace where adding more participants slows down the process instead of speeding it up.
Brooks' Law explains why adding extra resources to a late project often causes more communication overhead than benefit.
Get today's concept by email
Get one short, thought-provoking concept in your inbox each day. Unsubscribe at any time.
By subscribing you agree to our privacy policy. We never sell or share your address.