One lesson I’ve learned over the years is that organizational capacity problems almost never announce themselves as such.

Project managers don’t see overloaded organizations. They see unanswered emails, postponed workshops, delayed decisions and growing frustration between headquarters and local teams. After a few weeks, it becomes easy to conclude that a country is not engaged, that a key user is resisting the project, or that the local leadership simply doesn’t understand its importance. In my experience, those conclusions are often wrong.

Early in my consulting career, I joined a global Oracle ERP program across several countries in Latin America. The global template had already been implemented successfully in Europe, and responsibility for the Americas had been assigned to an experienced ERP Director based in the United States.

He was exactly the kind of project leader every global transformation hopes to have. He understood the technology, knew the business processes in depth, had participated in the design of the global model and, unlike many executives, was deeply involved in the day-to-day decisions of the program. He also believed the European implementation had relied too heavily on a large system integrator and was convinced the Americas rollout could be delivered with a leaner model, relying primarily on his own internal experts and bringing in external specialists only where local expertise was essential.

That was how I became involved in the project.

My role was to support the countries on the local regulatory and business requirements that the global team did not possess, particularly across Finance and Sales. Like every other workstream, we began by collecting information, reviewing existing processes and identifying gaps between local requirements and the global template.

One country, however, began to fall behind almost immediately.

The workstream responsible for Sales could not move forward because the local business lead rarely responded. Emails remained unanswered. Workshops could not be scheduled. Weeks passed without meaningful progress while every other area continued advancing.

The situation became increasingly frustrating for the project director. The project had become a strategic priority for the entire company and it was difficult to understand why someone entrusted with such an important role would appear so disengaged.

After several weeks, he asked me to contact her directly, hoping that speaking Spanish and understanding the local culture might help establish communication. It didn’t.

Eventually, after almost two months with little progress, he looked at me one morning and simply said, “Let’s go to Mexico.”

The following day we arrived at the local office before business hours. The office was still closed when we got there, and after a few minutes a woman arrived with the keys, opened the building and welcomed us inside. We assumed she was the receptionist.

Our first meeting that morning was scheduled with the Sales Manager. Nine o’clock came and went. Then ten. By midday she still hadn’t appeared.

Concerned about the delay, the project director spoke with the local General Manager, who immediately made a phone call to find out where she was. The answer surprised all of us. She was trying to resolve an invoicing issue that had stopped several trucks from leaving the warehouse. Customers were waiting, and she was the only person who knew how to solve it.

Later that day, while we were having lunch, we saw the same woman who had opened the office that morning. Someone casually asked who had been covering reception while she was away. “The Sales Manager,” came the reply.

By late afternoon, when our meeting finally began, we realized that the person we had been waiting for was also the person who had opened the office that morning, covered reception when necessary, solved operational problems, supported warehouse activities and kept the business moving whenever something critical happened.

For weeks, we had interpreted her silence as a lack of commitment, but in reality, she was carrying responsibilities that would have been distributed across several people in a larger organization.

The project director did something that impressed me even more than his decision to fly to Mexico: he apologized. She had never complained. She had never defended herself. She probably never knew how frustrated headquarters had become. Still, he felt it was important to acknowledge that he had misunderstood the situation.

That moment taught me something that has stayed with me throughout my career. Most implementation methodologies pay considerable attention to governance structures, steering committees, project plans and decision matrices. Much less attention is given to a far simpler question: who is going to create the time for the people expected to lead the transformation?

Because those people aren’t sitting around waiting for the project to begin, they’re already running the business.

This is particularly true in many Latin American organizations, where experienced professionals often perform responsibilities that, in larger headquarters, would be shared across multiple roles. Global programs frequently underestimate that reality, assuming every subsidiary has the same organizational depth and the same ability to dedicate key people to transformation activities.

Looking back, I realize how predictable everything that followed became.

Forty years after ERP implementations became commonplace, I continue to see this pattern with surprising frequency. Organizations launch ambitious transformation programs without first asking whether the people responsible for shaping the future have enough capacity to step away from running the present.

Before interpreting silence as resistance, it is worth asking a much simpler question: have you made room for people to participate in the transformation?