Adding consultants to a late project usually makes it even later. What is missing is rarely hands. It is judgment, at the right time.
When an SAP program or an Oracle rollout starts slipping, the most common reaction is to ask for more people: more consultants, more hours, more pressure on the integrator. It is an intuitive response and, often, the one that finishes complicating the project.
Fred Brooks wrote it down in 1975, drawing on his experience leading the development of IBM’s operating system: adding manpower to a late software project makes it later. Half a century on, the observation still holds in ERP projects.
Why adding people subtracts speed
There are two mechanisms. The first is ramp-up. Every new person needs someone to explain the design, the decisions already made and the open issues. That someone is almost always the person who knows the project best, who stops moving it forward in order to teach.
The second is coordination. Communication channels grow faster than the team. A team of 10 has 45 possible pairs of conversation. With 15 people there are 105. Every extra channel is one more meeting, email or misunderstanding.
The context makes it harder
Finding the right person is not easy either. According to ManpowerGroup’s talent shortage survey this year, 74% of employers worldwide struggle to fill the roles they need, double the level of 2014. Portugal is among the countries with the greatest difficulty, at 84%.
In the SAP world the pressure is even higher. Standard maintenance for SAP ECC ends in 2027, and many companies in Spain and Portugal are planning their migration in the same window. They all compete for the same people with real S/4HANA experience, and traditional hiring processes take months the project does not have.
What adding judgment means
The alternative is not to add fewer people but to add something different. A profile who has already led a migration, already closed a procure-to-pay cycle in SAP or already stabilized a troubled go-live does not need the map explained. They read it on their own, and within a few weeks they find where the real bottleneck is.
In practice, one or two well-chosen senior profiles, brought in at the right moment, tend to move a project more than an enlarged team. The difference is who comes in and when, not how many.
When more hands are needed
Not every delay is solved with judgment. If the problem is volume, such as data loads, test execution or documentation, adding people with clear guidance does speed things up. And if the problem is scope or sponsorship, no profile solves it: it takes a leadership decision. That is why it pays to diagnose before reinforcing.
How we approach it at Aunergia
Through our strategic profiles practice we bring in SAP, Oracle and JD Edwards specialists, senior project managers and fractional C-levels, all with more than ten years of experience. Before proposing anyone, we understand where the project is stuck. Then we bring in the profile who has already solved that problem elsewhere, within weeks and without expanding the client’s fixed structure.
Will your next reinforcement add speed, or add coordination?
Sources: Frederick P. Brooks, The Mythical Man-Month (1975); ManpowerGroup, Talent Shortage 2025; SAP, maintenance timeline for SAP Business Suite 7.
Comentarios recientes