Episode transcript The transcript is generated automatically by Podscribe, Sonix, Otter and other electronic transcription services.
Hello everyone, here is Ricardo Varas, and this is the 5 Minutes Podcast. Today I'd like to talk about one of the most famous principles in project management, a principle that was created more than 50 years ago but remains surprisingly relevant today. And I'm talking about Brooks Law. It was introduced by Fred Brooks, one of the pioneers of the software engineering field. And it can be summarized in a simple but very hard-to-understand statement. Adding manpower to a late software project makes it later. At first, this idea sounds completely counterintuitive. If a project is late, wouldn't adding more people help to accelerate the work? That seems like common sense. However, a project reality is a much, much more complicated scenario. Imagine a team of five people that had been working on a project for several months. They understand the requirements, they know the risks, and they have developed an effective way of working together. Now imagine that this project is starting to fall behind schedule. Many managers would immediately decide to add five more people. Okay, so we have five, we add five more, and then we can do much faster because we will have 10 people. The problem is that those new team members do not become productive on day one. They need training, they need context, and they need to understand previous decisions, technical details, and project priorities. And who is providing that training? The most experienced members of the existing team. Remember the five ones that are already delayed? As a result, the people who should be focused on delivering the project now spend part of their time onboarding new team members. But that is the one size of the challenge. Communication also becomes significantly more complex. As teams grow, communication paths increase dramatically. More meetings, more coordination, more dependencies, more opportunities for misunderstanding. And all of this creates overhead that often goes unnoticed. There is also the integration challenge. Even if every new team member delivers useful work, someone still needs to combine all those pieces, resolve conflicts, perform testing, and ensure that everything works together. It's like glue connecting every single piece of the work to make the result, to make the product or the service your project is delivering useful and integrated. And this is why in complex knowledge-based projects, simply adding more resources rarely solves the underlying problem. In many cases, it makes things worse. What is fascinating is that Brooks' law is still relevant in the age of artificial intelligence. Today, many organizations believe the answer is adding more AI tools, more agents, and more automation. But if priorities are unclear, processes are broken, or governance is weak, the technology you're putting in place simply amplifies the existing complexity. The real issue is often not the number of resources available. The real issue is how work is organized and managed. The next time someone suggests you solve a late project by simply adding more people, remember Brooke's law. The solution may not be to increase capacity. It may be removing obstacles, simplifying decisions, and improving coordination. Because in project management, more is not always better. Think about that. I hope you enjoyed this episode, and see you next week with another 5 Minutes Podcast.
