Brooks’s Law

When you're behind on a project, throwing more people at it feels like the solution... but is it?

Fred Brooks warned us decades ago:
"Adding manpower to a late software project makes it later."

Why? Let’s break it down:

1️⃣Onboarding takes time. New people don’t hit the ground running—they need context, tools, and mentorship.

2️⃣Coordination costs skyrocket. More people mean more meetings, more communication overhead, and more chances for things to get lost in translation.

3️⃣Existing workflows are disrupted. Instead of focusing on solving problems, your core team is now training new folks.

What’s the better approach when deadlines loom?

✅ Focus on the core team. Empower them to work smarter, not harder—reduce distractions, prioritize ruthlessly, and streamline processes.
✅ Adjust scope. Can you deliver an MVP (minimum viable product) instead of the full scope?
✅ Plan smarter for the future. Anticipate resource needs earlier and invest in long-term team cohesion.

Brooks’s Law reminds us there’s no quick fix for a late project. More isn’t always better—especially in software development.