A transformation program loses six weeks because a supposedly experienced project manager first has to understand the business logic, decision-making processes, and system landscape. A carve-out comes under pressure because the M&A expert has transaction experience but lacks the operational execution skills. Such situations are rarely a coincidence. The five mistakes made in expert recruitment usually arise before the first candidate is presented—due to unclear requirements, incorrect selection criteria, or decisions that take too long.
For critical projects, external expertise is not a capacity buffer without consequences. The right person provides early direction, accelerates implementation, and relieves pressure on key internal roles. The wrong person costs time, acceptance, and often the opportunity to capitalize on a tight window of opportunity. Therefore, the key is not to review as many profiles as possible, but to precisely define the need and rigorously evaluate candidates.
1. The role is described in terms of capacity needs rather than as a results-oriented assignment
Many requests begin with a job title: ERP Project Manager, Finance Expert, or Interim Manager for Operations. While this is useful as an initial classification, it is not sufficient for a perfectly tailored placement. This is because the same role can require completely different experience depending on the initial situation.
An ERP project might involve system selection, a rollout across multiple countries, stabilizing a problematic go-live, or harmonization following an acquisition. If you’re simply looking for additional capacity, you may find a solid candidate. If you need to close a critical performance gap, you need someone who has already managed exactly this situation and delivered results under comparable pressure.
Therefore, start by defining the assignment, not the job title. What specifically must be achieved in the first 30, 60, or 90 days? Which decision, work package, or milestone absolutely cannot fail? Which internal interfaces need to be activated? These questions narrow down the search and make it possible to compare the quality of different profiles.
The downside: A requirement that’s too narrowly defined can unnecessarily limit the market. Not every experience needs to be an exact match. What matters is which elements are mandatory—such as a specific transformation pattern, a relevant system landscape, or the management of complex stakeholders—and where transferable experience is sufficient.
2. Technical expertise is confused with project success
An excellent specialist is not automatically the right expert for a specific assignment. Technical knowledge is the ticket to entry. Impact is only achieved when the expert can apply this knowledge within the existing environment.
In transformations in particular, three factors are just as important as technical depth: the ability to prioritize when data is incomplete, to commit decision-makers to a clear course of action, and to get teams to implement the plan. A data and AI expert may be technically outstanding yet have little impact if they lack experience in aligning business units, IT, and governance toward a common vision. Conversely, sheer assertiveness is not enough if technical credibility is lacking in a highly specialized environment.
Therefore, don’t just examine what a candidate has done, but also how they have worked. What responsibilities did they actually hold? What obstacles did they face? What results were achieved under their leadership? And what role did they play themselves: analyst, program manager, sparring partner for management, or operational implementer?
References and project histories should answer precisely these questions. General statements such as “experience in digital transformation” or “expertise in supply chain” are of little value. A profile becomes credible when the scope of the project, the initial situation, the candidate’s own contribution, and the results are clearly identifiable.
3. The 5 Mistakes in Expert Selection Often Start with a Lack of Context
Even a very good briefing loses its value if key contextual factors are not disclosed until after the selection process. These factors include not only budget, duration, and workload but also the nature of the assignment, decision-making structure, political environment, team readiness, and the actual urgency of the situation.
An expert capable of leading a restructuring from a technical standpoint may need a different mandate and more backing in a company with high resistance to change than in a fast-decision-making scale-up structure. In a private-equity-driven value-enhancement program, a very short analysis cycle, clear pressure to implement, and direct communication with the operating team are often key. In a corporate group, governance, employee participation, and international coordination can have a greater impact on success.
This context is not a minor detail. It determines whether an expert must act as a catalyst, a program manager, or a temporary executive. Failing to disclose this context increases the risk of selecting someone who is technically qualified but organizationally unsuitable.
A good selection interview therefore tests the reality of the assignment. How does the expert handle conflicting interests? When do they escalate the situation? How do they create transparency in the first two weeks? How do they ensure decisions are made if the steering committee fails to deliver in a timely manner? Concrete answers reveal more than a compelling resume.
4. Speed Is Confused with Hasty Selection
Under intense time pressure, the temptation is great to hire the first available candidate. This can be the right move if the task, environment, and success criteria are clear, and the candidate’s project experience is a clear fit. Often, however, it is only a seemingly quick solution.
Haste isn’t indicated by having suitable candidates available within 24 to 36 hours. It’s indicated by making a decision without a structured review. Even a focused 30- to 45-minute conversation can reveal significant risks: actual availability, willingness to perform operational work, expectations regarding decision-making authority, and a good fit with the leadership and communication culture.
The better alternative is a quick but thorough selection process. Before beginning your search, define three to five non-negotiable criteria and apply them consistently to every profile. For an SAP rollout, these might include, for example, experience with a comparable template, leading international workstreams, knowledge of the relevant modules, responsibility for the go-live, and availability for the planned start date.
Having more profiles does not automatically improve quality. It often prolongs the coordination process and shifts the responsibility onto the decision-maker. A curated shortlist accelerates the process when every profile presented already meets the core requirements and the differences are made transparent.
5. The launch is not treated as a critical project phase
The hiring process is not complete once a candidate accepts the offer. The first few days are particularly crucial in determining whether external expertise will quickly make an impact or get bogged down in coordination. Without a clear mandate, access to relevant information, and a designated internal sponsor, even an experienced expert can only deliver to a limited extent.
An effective start therefore requires a brief, binding framework. This includes a prioritized vision, key points of contact, known risks, decision-making processes, and an initial meeting to review results. The expert should make it clear early on which assumptions they are testing, which decisions are pending, and where support is needed. This creates transparency and prevents the scope of the assignment from creeping out of control.
Especially with complex programs, it’s worthwhile to conduct a joint review after the first two weeks. Is the scope of the project still clearly defined? Are there any skills missing from the team? Have priorities changed? This feedback is not a sign of uncertainty, but rather professional risk management.
What Makes for a Reliable Team of Experts
The best team combines precision with speed. It starts with a results-oriented mandate, takes the actual project environment into account, and verifies project experience beyond what’s on paper. It then requires a decision that is fast enough to meet the timeline and thorough enough to ensure cost-effective deployment.
consultingheads steps in precisely at this intersection: with personally selected experts whose experience matches the specific assignment, and a focused selection process completed within a short timeframe. This reduces coordination loops without compromising on technical depth or implementation strength.
When results are what matter, the key question shouldn’t be who’s currently available. It should be: Who can make a decisive impact in this environment from day one?
