“Transformation” is one of those concepts that bends under the weight of everything people project onto it. Depending on who’s using it and in what context, it can mean anything from a genuine, disruptive overhaul – when you blow something up and build a better version in its place – to the sort of measured, incremental continuous improvement that’s been a standard business practice since someone mapped out the Toyota Production System decades ago. Both are legitimate and both are necessary, but they are highly dissimilar ways of heading toward an outcome. And HR teams that are already drowning in ambition and desire to “change” or “transform” may, in fact, simply be struggling with how to approach consequential organizational evolution.
So when HR leaders, or pundits on stage at an HR conference, talk about “transformation” … is everyone on the same page?
Improving or Transforming?
The distinction between improvement and transformation matters more than most HR conversations acknowledge. Continuous improvement, rooted in the concept of Kaizen, the Japanese philosophy of small, ongoing change, is the incremental, steady effort to make existing processes better and more efficient by optimizing what’s already there. Low risk by design, it’s cyclical and iterative; when it’s working well, it becomes part of the operational DNA of an organization rather than an initiative that someone needs to announce and everyone else needs to survive.
Transformation is an entirely different proposition. It’s a structural overhaul aimed at changing the base state itself; not refining how things work but replacing what those things fundamentally are. It is, by definition, disruptive, and it requires significant investment, genuine change management, and an organizational willingness to absorb cultural upheaval along the way. The timeline isn’t cyclical; it has a beginning, an execution phase, and a new operational reality on the other side.
Part of the confusion amongst HR and organizational leaders (and there is genuine confusion) stems from a lack of understanding of organizational appetite: an organization’s comfort level with disruption and the pace at which change is expected to happen. Some organizations thrive on the “burn it down and rebuild” approach; others would break out in hives at the mere suggestion. Neither disposition is inherently wrong, but the gap between a leader’s appetite for disruption and an organization’s capacity for it is where transformation initiatives tend to skid off the tracks.
And part of it, honestly, is organizational size, which may get glossed over in a lot of these conversations.
Tales from Two HR Teams
Early in my career, I worked in an HR department of about 25 people, organized along the classic functional lines: I was the Recruiting leader and my peers headed up Benefits, Compensation, Employee Relations, HR Operations, and Learning and Development with all of us reporting to the VPHR. At some point during my time there, the decision was made to move to a new HCM system. What followed was a long parade of vendor demos, a narrowing-down process, a final decision, and then implementation planning in earnest. The whole arc – from the moment someone first had the thought to the day we went live – was mapped out over roughly three years. And it took that long. It was a major undertaking that touched every corner of the HR function and required real coordination, sustained communication, and deliberate attention to training and change management.
Later in my career, when I joined a mid-sized organization to lead our small HR team, I found myself staring at a moderately active recruiting process (3 to 4 open reqs at any given time with a few hundred applicants per requisition), running almost entirely on email, a spreadsheet, and collective goodwill. It was neither sustainable, efficient, or fun to be around for anyone. So I sat through a handful of demos, chose an ATS that both fit our needs and would bring us into the 21st century, and we went live within about a month.
The easy conclusion would be that the second situation wasn’t really “transformation” – that it was too small, too fast, too modest in scope to earn the word. But I’d push back on that assessment and the reason has nothing to do with size.
Go back to the distinction we started with – that transformation changes the base state while improvement optimizes what’s already there. By that test, the ATS rollout qualifies; not because it was big, because it wasn’t, but because it replaced a non-system with a system. There was no real process to refine (remember we operated with email, a spreadsheet, and a lot of hope) and I didn’t set out to make the old way better, but rather to replace what the old way fundamentally was. Had I instead swapped a clunky ATS for a slightly better one or tuned-up the workflows in a platform we already had, that would have been improvement – useful and worth doing, but not transformation.
Which is exactly why the two situations, three years and three weeks apart in effort, belong in the same category. Both changed the base state, both required a genuine shift in how work got done, and both demanded planning, decision-making, stakeholder communication, training, and the kind of steady follow-through that keeps things from quietly reverting to the old way. Both asked the people involved to let go of a familiar process, however inadequate, and adopt a new one. The timelines were different, the organizational footprints were different, and the complexity was different, but the fundamental nature of what was being transformed – and what it asked of the humans doing it – was not.
What gets lost in a lot of transformation conversations is that human element; all those “things” that we require of the human beings doing the work. And I don’t mean this in the feel-good inspirational-poster sense; I mean the specific, measurable reality that people have a finite capacity to absorb change, and that capacity matters whether you’re running a three-year HCM implementation or a four-week ATS rollout.
Scale doesn’t exempt anyone from the obligation to manage it well… and size doesn’t automatically confer the discipline to do so.
The Future Remains Unwritten
Which brings us back to the original question: are you transforming or improving?
For most HR functions, across any given year, the honest answer is some version of both. Continuous improvement keeps the wheels turning and the HR and People Operation healthy; it’s how we refine hiring processes, tighten onboarding logistics, and smooth out the performance feedback cycle. Transformation is warranted when the base state itself no longer works – when the current model isn’t competitive, when new technology demands a structural pivot, or when the gap between how work is designed and how people experience it has grown too wide for one more round of optimization to even close.
The trouble starts when those two get conflated. Many organizations reach for the language of transformation when what they’re describing is improvement, and that mismatch may carry consequences. The investment required, the change management involved, the human capacity needed – all of it calibrates differently depending on which road you’re traveling. Dress up routine improvement as transformation and you raise the stakes for no reason, burn through goodwill, and train people to be skeptical of the next big initiative before it even arrives. Run a genuine transformation as though it were routine improvement, and you’ll inevitably under-resource it, under-communicate it, and watch it stall.
So before you announce that HR is transforming, it’s worth asking a different question first: “are we changing the base state, or are we making the current one better?”
Both are worthy. Both deserve your discipline. They just don’t deserve the same word.
*****
