Project Delivery Capacity
Why adding more projects can create disproportionate coordination overhead.
BoRo Studio · Part of BoRo's work on operational architecture for Solar + BESS project delivery.
The ceiling nobody planned for
A delivery company usually plans capacity in people and equipment: engineers, project managers, crews. On that view, twice the projects needs roughly twice the resources.
What appears instead is a ceiling that resources do not lift. The company hires, and delivery does not speed up in proportion. New project managers take a long time to become effective. The senior ones are busier than before. The limiting factor was not headcount.
Why coordination grows faster than project count
A single project is coordinated internally: its engineering, its procurement, its site. Concurrent projects share things. They share the engineering team, the procurement function, key suppliers, crews and commissioning specialists.
Every shared resource is a place where one project's change becomes another project's problem. The number of those interactions rises faster than the number of projects. If each interaction is resolved by a person carrying context, the coordination work grows faster than the company does.
How the ceiling shows up
More projects require disproportionately more meetings. Senior people become the bottleneck for decisions that used to be routine. The same coordination failure is resolved repeatedly, project after project, because the resolution lived in a conversation and not in the operating model.
From the outside it can look like a hiring or performance problem. From the inside it feels like everyone is working hard and the organization is getting slower.
Capacity is a property of the operating model
The number of projects a company can run concurrently is set less by its headcount than by how much coordination each additional project costs. That cost is determined by the operating model: whether handoffs are defined, whether changes have a path, whether there is one agreed state.
Where those exist, a new project plugs into a structure and adds mostly its own work. Where they do not, every new project is integrated by hand, and the hands are finite.
Raising it
Start with the coordination failures that recur across projects, not with the ones that were dramatic once. A failure that repeats is a missing piece of architecture. Fixing it once at the level of the operating model removes it from every future project.
In practice that means defining lifecycle states and their owners, the handoffs between phases, the propagation path for changes and the record for each fact. Some of that will call for systems. The sequence matters: the operating model first, then the systems it requires.