Most organizations house workforce strategy and transformation strategy in different functions, often reporting to different executives with different priorities. That separation is administratively convenient. It is also a frequent, underappreciated cause of failed execution.
Every transformation is a workforce transformation
Whatever the stated goal of a transformation, whether it is a new technology platform, a restructured operating model, or an entry into a new market, the actual mechanism of change runs through people: what they are asked to do differently, what skills that requires, and whether the organization has those skills or a credible plan to build them.
When workforce planning happens separately from transformation planning, it happens too late and with too little integration. Skills gaps are discovered after the technology has been selected. Role redesign becomes a post-launch scramble instead of a pre-launch design decision. The transformation proceeds on a workforce plan that was never actually built for it.
What integration actually looks like
Organizations that get this right build workforce implications into the transformation business case from the beginning, not as a downstream HR concern but as a core design constraint alongside budget and timeline. That means identifying skills gaps before selecting a solution, redesigning roles and incentives alongside new processes rather than after them, and giving the workforce strategy owner a seat in the same governance structure as the technology and operations leads.
One strategy, not two
The organizations I have seen sustain transformation most successfully stopped treating human capital strategy as a support function to execution strategy and started treating it as execution strategy, full stop. That reframe, more than any specific program, is what closes the gap between a well-designed initiative and one that actually changes how people work.
Why the org chart separation causes real problems
Most organizations house workforce strategy and transformation strategy in different functions, often reporting to different executives with different incentives and different definitions of success. That separation is administratively convenient. It is also a frequent, underappreciated cause of failed execution, because the actual mechanism of any transformation runs through people: what they are asked to do differently, what skills that requires, and whether the organization has those skills or a credible, funded plan to build them in time.
What happens when workforce planning arrives too late
When workforce planning happens separately from transformation planning, it typically happens too late and with too little real integration. Skills gaps get discovered only after a technology platform has already been selected and purchased. Role redesign becomes a post-launch scramble rather than a pre-launch design decision made alongside everything else. The transformation proceeds on a workforce plan that was never actually built with it in mind from the start.
What genuine integration looks like in practice
Organizations that get this right build workforce implications into the transformation business case from the very beginning, treating it as a core design constraint alongside budget and timeline rather than a downstream HR concern to address later. That means identifying skills gaps before a solution is selected, redesigning roles and incentives alongside new processes rather than after them, and giving the workforce strategy owner an actual seat in the same governance structure as the technology and operations leads, not a separate advisory track.
Bring this thinking to your organization.
Dakhalfani speaks on human capital & technology for executive audiences, conferences, and leadership programs.