← Back to Knowledge Hub

Who actually does what in a transformation? HR, change managers, external consultants, and the role confusion that derails change.

One of the most common and least discussed causes of failed transformation is that nobody is clear on who does what. HR assumes the change manager is handling resistance. The change manager assumes line managers are reinforcing new behaviours. Line managers assume someone in the program team is managing stakeholders. The project manager assumes HR is leading the people side. Everyone assumes someone else is doing the critical work, and the gaps only become visible when adoption stalls. This article provides practical clarity on three connected questions: what is HR's actual role in transformation, when should you bring in external change management support, and how do you define new roles without creating the confusion and resistance that undermines everything else.

What is HR's actual role in an organisational transformation?

The question is not whether HR has a role in transformation. It does. The question is what that role actually is, and equally important, what it is not. HR's value in change is enormous when it focuses on what only HR can do: providing organisational intelligence, connecting change to people systems, and ensuring the human consequences of decisions are understood before those decisions are made. HR's value collapses when it tries to own the entire people side of change, because the people side of change belongs to everyone.

Use the tool below to explore who typically owns each key activity in a transformation. Click any activity to see the full RACI breakdown, then expand individual roles for practical guidance.

When should you bring in an external change manager, and when should you not?

The decision to bring in external change management support is one of the most consequential choices in a transformation. Get it right and you accelerate the change with expertise and objectivity your organisation lacks. Get it wrong and you create dependency, erode internal confidence, and spend significant money on capability that walks out the door when the engagement ends. The answer is never a blanket yes or no. It depends on your specific situation. Use the framework below to find your scenario and explore the recommendation.

How to define new roles and responsibilities without creating confusion or resistance

Restructuring roles is one of the highest-stakes activities in any transformation. It touches people's identity, status, expertise, and sense of security simultaneously. The technical act of drawing new boxes on an org chart is straightforward. The human act of helping people navigate what those new boxes mean for them is where most organisations fail. Below are six principles for defining new roles in a way that creates clarity rather than confusion, and ownership rather than resistance.

  • Start with decisions, not job descriptions
  • Name what is being lost, not just what is being created
  • Co-design the boundaries before you announce them
  • Use the first ninety days to test and adjust, not to enforce
  • Invest in the managers who have to explain the changes to their teams
  • Separate structural change from identity change and address both

Role Clarity Self-Check

Use this checklist to assess whether your transformation has the role clarity it needs to succeed. Each item represents a common gap that, left unaddressed, creates confusion, duplication, or accountability vacuums.

0 of 10 complete

This topic is part of Enablement, the third pillar of the TCA Change Model.

Explore the Full Model