One of the most persistent challenges in transformation hiring is defining the balance between technical capability and non-technical delivery skills.
In most programmes, this balance is not clearly fixed at the outset and often becomes more refined only once delivery is underway or hiring conversations begin to expose gaps in expectation.
Transformation roles typically sit at the intersection of business and technology. They are close enough to technical delivery that some level of systems, data or process understanding is required, but equally embedded enough in business functions that stakeholder management, communication and change adoption are critical to success. The difficulty is that these two dimensions are often treated as equally important in the early stages of a brief, when in reality, most roles lean more heavily in one direction than the other.
In practice, the balance is usually determined by where the role sits within the transformation lifecycle. Roles closer to implementation, particularly in systems or data-led programmes, tend to require stronger technical grounding. These individuals are often expected to understand how systems interact, how data flows through an organisation, and how technical decisions impact downstream business processes. Without this grounding, delivery risk increases significantly.
By contrast, roles focused on adoption, change management or operating model design tend to rely far more on non-technical capability. In these cases, success is less about understanding technical architecture and more about influencing behaviour, aligning stakeholders and ensuring that new ways of working are actually embedded across the organisation.
Where challenges arise is when both sides of this requirement are expected at a high level within a single profile. This is particularly common in transformation briefs where the full complexity of the programme is not yet fully understood. On paper, it can feel efficient to combine technical and non-technical requirements into one hire. In reality, the market rarely supports this at senior level in a meaningful way.
What tends to happen in these situations is that candidates naturally fall into distinct categories. Some bring strong technical depth but are less experienced in cross-functional stakeholder environments. Others are highly effective in delivery and change contexts but have limited technical exposure. Very few candidates combine both at an equally strong level, particularly in complex enterprise environments.
This is why clarity around prioritisation becomes so important. The most effective transformation briefs are not those that try to maximise capability across every dimension, but those that are clear about what the role needs to lead on versus what it needs to support. In many cases, technical understanding is essential, but not necessarily the defining factor in success. In others, it is critical and cannot be compromised.
There is also a noticeable shift in the market towards valuing adaptability over pure technical depth in certain transformation roles. As programmes become more interconnected, the ability to move between business and technical conversations, translate requirements accurately and maintain alignment across stakeholders is becoming increasingly important. This is particularly true in environments where delivery is iterative and priorities evolve over time.
The organisations that are most successful in transformation hiring tend to be those that define this early and allow it to shape both their shortlisting and interview process, rather than treating it as a secondary consideration.
If you’re looking for your next position within the transformation space, get in touch!
0117 450 7700
