Most transformation programs do not fail in execution.
They fail in selection.
Long before the first milestone is missed, the trajectory is already set by one decision that is often treated as routine. The choice of the project manager.
For a sponsor, this is not a staffing decision. It is a control decision. The project manager defines how information flows, how problems are surfaced, how decisions are prepared, and how reality is translated for the executive layer. If that translation is weak, delayed, or distorted, you are no longer managing the project. You are reacting to it.
And yet, this decision is frequently delegated, rushed, or reduced to a checklist.
Experience is the first filter, but it is often misunderstood.
It is not about years. It is about pattern recognition under comparable conditions. A project manager who has navigated a full ERP implementation across multiple countries understands escalation paths, stakeholder resistance, data migration issues, and the sheer operational load in a way that cannot be simulated. Someone who has only managed isolated or smaller initiatives will learn these lessons on your project.
That learning curve is expensive.
Relevance matters just as much as depth. Industry context, comparable scope, similar complexity. Rolling out a system in one market is not the same as coordinating twelve. Managing a clean greenfield implementation is not the same as untangling legacy processes and fragmented data landscapes. The closer the past experience is to your reality, the less your project becomes an experiment.
Track record is where most sponsors become too forgiving.
Projects are complex, and not every failure can be attributed to the project manager. That is true. But patterns still exist. You are not looking for perfection. You are looking for evidence that this person has brought difficult programs to a controlled outcome, with stakeholders who would work with them again. References are not a formality. They are one of the few ways to understand what actually happened behind the official narrative.
Then comes leadership.
A project manager does not just coordinate tasks. They shape behavior. They decide when to escalate, when to push, when to absorb pressure, and when to expose it. Communication is not about clarity of status reports. It is about whether the organization sees reality early enough to act.
Weak project managers report progress until the moment they cannot.
Strong ones surface problems while they are still manageable.
You will not fully see this in an interview. But you will see traces of it in how they describe past situations, how they structure problems, and how others describe working with them.
Problem understanding is the next layer, and it is where many candidates fall apart.
Transformation programs are not a sequence of known tasks. They are a sequence of emerging issues. The ability to quickly understand a problem, cut through noise, and frame a workable path forward is not optional. It is the core of the role.
The simplest way to test this is to make it real.
Bring your actual problems into the conversation. Watch how the candidate approaches them. Do they ask the right questions? Do they structure the issue? Do they jump to solutions without understanding the context? You are not testing for the perfect answer. You are testing for how they think under pressure.
Team dynamics are often underestimated, but they are not secondary.
A project manager operates through influence, not hierarchy. If they cannot build trust with your team, align different stakeholders, and manage tension without creating unnecessary friction, the project slows down. Decisions get revisited. Conflicts linger. Energy is lost in coordination instead of progress.
This is not about cultural fit in a superficial sense. It is about whether this person can operate effectively in your specific environment.
And then there is intuition.
Most sponsors try to ignore it in favor of “objective” criteria. That is a mistake.
If everything looks good on paper but something feels off, you are likely picking up on signals that are not easy to articulate. Pay attention to that. At the same time, intuition should not override clear gaps in experience or capability. It is a final filter, not a substitute for judgment.
The uncomfortable truth is that there are very few truly strong project managers for large-scale transformations.
Certifications do not change that.
They indicate familiarity with frameworks, terminology, and methodologies. They do not indicate the ability to lead a complex program through ambiguity, resistance, and pressure. Treat them as baseline knowledge, nothing more.
If you get this decision wrong, the consequences compound.
Issues surface late. Risks are understated. Teams lose direction. And as a sponsor, you find yourself increasingly involved in operational firefighting instead of steering the program.
If you get it right, many of these problems never reach you in the first place.
In simple terms: selecting a project manager is not about filling a role.
It is about choosing the person who will define how much of the project you actually get to see.