The conventional positioning of HR in change management is logistical. HR manages the communication cascade. HR coordinates the training programme. HR handles the redundancy process. HR ensures the documentation is compliant. These are all legitimate functions and some of them are genuinely important. None of them is the function that most determines whether the change produces the outcome the organisation needs. That function is architecture: the design of the change process in ways that account for the specific human dynamics that will determine whether the change is adopted, resisted, or transformed into something the organisation did not intend.
When HR is positioned as the administrator of change rather than as its architect, the organisation loses access to the specific expertise that would most improve the quality of the change design. HR practitioners who understand how people navigate transitions, what conditions produce resistance and what conditions produce genuine commitment, how organisational culture shapes the reception of change, and what leadership behaviour is required at each stage of a change process, have knowledge that is directly relevant to whether the change will succeed. When that knowledge is applied at the administration level, it improves the efficiency of the change process. When it is applied at the architecture level, it improves the probability that the change produces the outcome it was designed to produce.
The shift from administrator to architect requires both a different positioning of HR in the strategic conversation and a different quality of HR practice. The positioning shift is the one most commonly discussed, and it is genuinely important: HR cannot function as change architect if it is invited into the change conversation only after the change has been designed and the HR work of implementation has begun. The practice shift is less commonly discussed and equally important: the HR practitioner who aspires to the architect role needs to bring to the strategic conversation a quality of analytical and design capability that administration-focused HR development does not consistently produce.
What the architecture role specifically requires
Change architecture in the sense I am describing here is not a new concept with a new vocabulary. Its intellectual foundations are well-established in the work of Kotter, Bridges, Heifetz, and the broader organisational development tradition. What is new, or at least insufficiently embedded in how most HR functions operate, is the specific integration of this body of knowledge into the design of major change processes from their inception rather than as a supplement applied after the technical design has been completed.
The architect role requires, first, the capacity to distinguish between the technical dimensions of a change, those that require the application of existing expertise and produce predictable outcomes when that expertise is applied well, and the adaptive dimensions, those that require people to change their values, assumptions, and working identities in ways that cannot be mandated or trained and that must be navigated rather than managed. This distinction is both analytically important and practically consequential, because the interventions that work for technical challenges are frequently counterproductive when applied to adaptive ones. HR that can help senior leaders make and sustain this distinction throughout a change process is providing a quality of strategic input that the change is unlikely to receive from any other source.
The architect role requires, second, the specific capacity to assess the change readiness of the organisation with enough precision to inform the pace and sequencing of the change. Change readiness is not primarily a question of whether people understand the rationale for the change and are formally committed to it. It is a question of whether the relational, cultural, and structural conditions that genuine change requires are actually present: the quality of psychological safety in the organisation, the degree of trust in the senior leadership, the health of the informal networks that will determine whether the change message travels honestly or managed, the specific cultural features that will most powerfully shape how the change is received.
The architect role requires, third, the design of the people processes that accompany the change with enough sophistication to support the specific human dynamics of the transition rather than simply managing them. This includes the design of the communication process, which in most change programmes is treated primarily as a messaging challenge and which is actually a trust-building challenge that requires a fundamentally different approach. It includes the design of the leadership development that senior leaders need to navigate the adaptive dimensions of the change they are sponsoring. And it includes the design of the measurement and feedback processes that allow the change to be adapted as it proceeds based on honest evidence about what is and is not working.
The specific failures of administrative HR in change contexts
The specific failures that occur when HR operates in the administrative rather than the architectural mode in change contexts are predictable and consistent across organisations and change types. They are worth naming because they are not primarily failures of HR intent or HR capability but of HR positioning: the same practitioners who would provide genuine architectural input if engaged at the design stage provide only administrative support when engaged after the design is complete.
The most consequential failure is the absence of honest assessment of change readiness at the outset. Most large change programmes begin with a business case that is primarily financial and strategic, and a change management plan that is primarily operational. Neither document contains a rigorous honest assessment of the specific human and cultural conditions that will most significantly affect the change’s success. HR, which has the data, the relationships, and the analytical framework to provide this assessment, is typically not asked to do so at the point when it would most affect the design. By the time the resistance that the readiness assessment would have predicted has materialised, the change design is too far advanced and too politically committed to be substantially revised.
The second failure is the design of communication as broadcast rather than as dialogue. The communication plans that accompany most major change programmes are oriented toward consistent message delivery: ensuring that the key messages are communicated to all relevant audiences with sufficient frequency and through sufficient channels that no one can claim they were not informed. This is a legitimate objective and is worth pursuing well. It is not the same objective as building the quality of honest two-way communication that genuine change requires. The change that is communicated to people rather than developed with them is experienced differently, committed to less genuinely, and resisted more actively than the change that genuinely incorporates the perspectives of those who will be most affected by it.
Building the architect capability in HR
The development of HR practitioners who can operate genuinely in the architect role requires a different kind of professional development than most HR functions currently invest in. It requires deep grounding in the organisational dynamics that determine change outcomes, specifically the psychology of transitions, the sociology of organisational culture change, and the political dynamics of large-scale change in complex organisations. It requires the consultative skills to engage senior leaders in the strategic conversations where change architecture decisions are made, with enough credibility and enough analytic rigour that the HR perspective is genuinely influential rather than professionally present. And it requires the personal courage to bring honest assessments of change readiness and change risk to conversations where there is significant pressure to present the change as more straightforward than it actually is.
This last requirement is the most demanding and the least developed by conventional HR professional development. The HR practitioner who can tell a board that the change they have designed is not ready to be launched, and who can make that case with enough specificity and enough credibility to be heard, is providing a quality of service that is both more valuable and more professionally risky than the administrative support that most change programmes receive from HR. Building the capability and the confidence to provide that service is the most important single development investment available for HR functions that are genuinely serious about the architect role.
The specific risk HR avoids by staying in the administrator role
There is a specific and understandable reason why many HR practitioners resist the architect positioning even when they have the capability to occupy it. The architect role carries accountability for outcomes rather than only for process quality. The HR administrator who manages the change communication effectively and efficiently has delivered what was asked of them, regardless of whether the change produces the intended outcome. The HR architect who has shaped the change design is responsible, in a meaningful sense, for whether the design was adequate for the challenge. This accountability is both more consequential and more professionally risky than the accountability that comes with executing someone else’s design well.
Building the confidence to accept this accountability, alongside the capability to deserve it, is the specific developmental challenge for HR practitioners who want to move genuinely into the architect role rather than simply adopting its language. Organisations that want to benefit from HR architecture in their change processes need to create the conditions that make this accountability acceptable: clear mandate, genuine inclusion in the design process from the outset, and the senior sponsorship that makes it credible for HR to bring honest assessments of change readiness and change risk into conversations where there is significant pressure to accelerate.
HR in change is not most useful when it is managing the logistics of a change that has already been designed. It is most useful when it is shaping the design of a change that has not yet been implemented. The difference between the two is the difference between administering an outcome and producing one.