The fastest way to make a late project later is to invite six helpful strangers into the codebase on a Monday morning and call it ✨ acceleration ✨.

I’ve been the person doing the explaining. I know where some of the bodies are buried. I’ve also been the one who buried a few… unrealistic deadline, tight scope, “we’ll come back and clean this up” (we did not come back).

Yes, this is a Brooks’ Law post. “Adding manpower to a late software project makes it later.” Fred Brooks wrote that in The Mythical Man-Month back in 1975, everyone in software has heard it, and somehow it still needs saying every couple of years. I’m not going to redo the math. The short version is that two people have one line of communication between them and ten people have forty-five, so the coordination piles up way faster than the actual work does. Coda Hale wrote a much better (and much more recent) version in Work Is Work if you want the real numbers… or if you just want to know why your twelve-person standup accomplishes nothing.

But there’s a part of this I don’t hear about as much, and it’s the part that actually bit us.

We had a project to build an AI-powered automation template. Internally we call these PBJs 🍞 (pre-built journeys… and yes, the acronym and emoji use is real). The mandate came down from leadership, fully formed, without much input from the people who’d actually be writing the code. This is how it goes… someone three or four levels up decides it’s a priority and it lands on your sprint board and now it’s your problem.

The issue wasn’t headcount. We had enough engineers. The issue was that everyone needed to write code in the same small part of the codebase at the same time, and the deadline was yesterday.

When people talk about Brooks’ Law it’s usually about the people… ramp-up time, more meetings, more channels. That’s all real, but at least you can see it coming (and maybe even budget for it). What got us was more like density. People per square foot of code, if you will. Ten engineers spread across ten services is mostly fine. Ten engineers crammed into the same three files is a mosh pit, and no amount of onboarding docs is going to fix six open PRs touching the same function.

Pack that many people into that little code with a deadline breathing down their necks and they stop building within the abstractions. Nobody’s reading the existing patterns. Everyone (or their AI IDE) is just throwing spaghetti at the wall. And honestly… of course they are. Nobody gave them time to do it right, and that’s more on the org than on any of the engineers.

Merge conflicts everywhere. Conditionals nesting inside conditionals. Someone accidentally reverts a change from a PR that merged two hours ago because there’s no time to review properly and nobody can keep track of what landed where. You open a PR and it’s 400 lines of diff across files that three other open PRs also touch and you just… stare at it.

And it’s not like Slack helps. Forty-five communication channels turn into forty-five threads, twelve of which are in channels nobody monitors, three of which contain decisions that’ll surprise someone in two weeks, and fifteen backchannel DMs you may or may not be part of, because who needs open communication anyway.

By the time things stabilized, the deadline had passed and everyone was quietly exhausted. The people who’d been pulled onto the project ended up being solid contributors… after the pressure dropped, after they’d had time to actually learn the code. So the ramp-up did work. Just not in time for the deadline we were ramping up for.

I don’t think the lesson is “never add people,” though. Adding people is fine when there’s somewhere for them to stand… early in a project, when the work splits up cleanly, or when they can pick up the stuff around the edges so the core team can focus. It’s piling everyone onto the same hot spot that hurts. So next time someone wants to “add headcount,” maybe skip “how many?” and ask the dumber question first. Where are they all going to be typing?

And sometimes the right move when a project is late is to cut scope and protect the people who can fix it from the people who want to help. That’s a hard sell in a room full of people who think every engineer-hour is interchangeable… or when you truly don’t have a say in the deadline or scope and you’re just set up for failure. Brooks would say you can’t have nine women produce a baby in one month (his metaphor, not mine… and no, it hasn’t aged well). My addendum is less poetic: nine engineers in the same three files won’t ship the PBJ in one month either.