Key roles in change management for teams

Change management relies on a clear distribution of responsibilities between senior leadership, project managers, managers, support functions and the employees concerned. Not everyone has the same decision-making power, access to information or relationship with the field. When these roles are explicit, the organization can explain the purpose of the change, address difficulties at the right level and help teams turn an intention into new working practices.

Conversely, a project may be technically ready while remaining humanly fragile. A new method, tool or reorganization only becomes real when the people concerned understand what is changing, know what is expected of them and have a space to report what is not working. Change management is therefore not limited to distributing an announcement: it organizes the decisions, conversations, support and feedback that make adoption possible.

Why roles matter as much as the project

In many organizations, change is presented as a collective responsibility. That is true, but insufficient if no one knows precisely who is responsible for what. Saying that “everyone is responsible” can produce the opposite effect: decisions remain pending, messages vary depending on the person delivering them and field concerns do not reach the people able to act.

Good allocation is not about handing out titles. It defines concrete commitments. Who decides when a priority conflicts with an established habit? Who explains the reasons for the project to the teams? Who adapts the procedures? Who listens to objections? Who notices that actual use differs from what was planned? These questions prevent confusion between the person sponsoring the change and the person who monitors it day to day, or between the manager and the sole communication relay.

Role clarity also protects employees. They should not have to guess whether a message expresses a final decision, a working proposal or an instruction to apply. They can identify whom to contact with a question, request a decision and share a difficulty without fearing that they are bypassing the hierarchy. This clarity builds trust, particularly when the change affects work organization, tools or relationships between departments.

The sponsor: setting the direction and owning decisions

The sponsor is the person who publicly supports the change on behalf of the organization. He or she connects the project to a broader intention: responding to a market shift, simplifying an increasingly burdensome process, improving cooperation or dealing with a constraint. The role is not to master every operational detail. It is to make the change legitimate and show that it is a genuine priority.

This legitimacy is measured through actions. The sponsor devotes time to the subject, takes part in key moments, protects the necessary resources and decides when interests diverge. If one department must give up a comfortable habit to enable an overall improvement, the sponsor must be able to explain the choice and accept its consequences. Without this involvement, the project can easily appear to be an isolated initiative that everyone can expect to lose momentum.

The sponsor must also speak consistently. There is no value in promising that the change will require no effort or have no impact: teams quickly recognize this kind of message. A credible message acknowledges the adjustments required, explains what remains open to discussion and specifies what has already been decided. This frankness does not remove concerns, but it provides a stronger framework for addressing them.

A common mistake is to delegate this function entirely to a project team or the communications department. These teams are essential, but they cannot replace the voice of someone with the authority needed to make decisions and maintain the direction. The sponsor must not disappear after launch: support is particularly useful when the first obstacles make the project less abstract.

The change manager: organizing adoption

The change manager turns the ambition supported by the sponsor into a workable approach. He or she analyzes the groups concerned, the habits that need to change, the skills to strengthen and the risks of misunderstanding. This role coordinates the actions that help people move from a familiar way of working to a new one.

The work includes listening to the field. Before preparing messages or training, it is useful to identify what teams actually do, the constraints they face and the benefits they may perceive. A change designed solely by a steering committee may overlook essential day-to-day situations. The change manager therefore creates feedback channels, gathers weak signals and escalates issues that require a decision.

He or she also ensures consistency between actions. Communication that promises autonomy loses credibility if managers have no decision-making latitude. Training may be well designed but have no effect if there is no time to practice. The change manager does not resolve these contradictions alone, but makes them visible and proposes the necessary adjustments.

This role benefits from working closely with the operational project manager. A project may meet its schedule, budget or technical quality targets without teams truly adopting it. Conversely, human support needs concrete information about what is changing, when and for whom. Cooperation between these responsibilities prevents adoption from being treated as a task added at the end.

The project manager: making the transformation achievable

The project manager handles operational delivery: coordinating contributors, tracking dependencies, resolving problems and preparing deliverables. This role is distinct from that of the change manager, even though the boundaries vary between organizations. While the change manager focuses mainly on the conditions for adoption, the project manager ensures that the solution is ready and usable.

This distinction is valuable when a project has a significant technical dimension. A new platform may be available, but its access rights, usage rules, support materials and assistance processes must match the reality of the teams. The project manager must therefore incorporate their feedback, without assuming that every field request is resistance to be dismissed. Some objections reveal concrete risks or overlooked use cases.

The partnership works when information is shared regularly. The project manager announces changes that will affect users. The change manager shares concerns, explanation needs and adoption difficulties. Together, they can decide whether a solution should be adjusted, whether a message needs clarification or whether a manager needs specific support.

Managers: translating change into real work

Managers hold a decisive position because they give change meaning in the concrete context of their team. Employees do not only ask what the organization has decided. They want to know how this will change their priorities, interactions, tools, objectives and autonomy. The manager is often best placed to provide this translation.

The role is not to repeat an official presentation. Managers must be able to explain the reasons for the change in their own words, identify its specific impact on their team and create a space where questions can be asked. They must also accept that they will not have every answer immediately. An honest answer, accompanied by a commitment to find the information, is better than an uncertain claim.

The manager observes the gaps between the expected process and what actually happens. An employee who bypasses a new tool is not necessarily expressing principled opposition: they may lack time, guidance or training, or they may be facing a technical difficulty. By looking for the cause before reiterating the rule, the manager helps the organization learn from implementation.

It is unfair to expect managers to carry change alone. They need information in advance, time to discuss the change with their teams and easy access to the people who can solve problems. Asking them to communicate decisions they discover at the same time as their team weakens their credibility. Involving them early, on the other hand, enables them to prepare appropriate responses.

Employees: actors in adoption, not mere recipients

Employees apply the change in the most concrete situations. Their role is therefore broader than that of communication recipients or training participants. They experiment with new practices, report inconsistencies, suggest improvements and share useful solutions with colleagues. Their field experience is a resource for making the change viable.

This participation does not mean that every decision must be negotiated indefinitely. An organization may face constraints or have a clear direction. However, it benefits from distinguishing between what has been decided and what can be adapted. Teams can often contribute to implementation methods, the support needed or the identification of specific situations. This room for action encourages engagement without creating a false promise of total consultation.

For feedback to be useful, employees must know whom to send it to and what will be done with it. Asking for opinions without ever explaining the decisions made creates frustration. Conversely, showing that a difficulty has been heard, even if it cannot be resolved immediately, strengthens the quality of the dialogue. Adoption then becomes an active process rather than an instruction.

Change champions: creating listening within teams

Change champions can complement the action of managers, especially when teams are dispersed, diverse or heavily solicited. These people know local practices, test certain solutions, answer nearby questions and report points of friction. They are not there to convince people at all costs, but to facilitate an informed conversation between the project and the people concerned.

Choosing champions requires rigor. It is not enough to appoint the most enthusiastic or available people. A diversity of professions, perspectives and contexts makes it possible to detect more actual difficulties. A champion respected for their knowledge of day-to-day work may be more useful than an ambassador who repeats a message too far removed from the team's concerns.

Champions need a clear mandate. Can they answer questions? Take part in testing? Report warnings? Suggest adaptations? Without explicit limits, they may provide contradictory information or find themselves responsible for decisions that do not belong to them. Their contribution must be recognized and supported, without putting them in an uncomfortable position with their colleagues.

Support functions: making change consistent

Human resources, internal communications, training teams, legal functions and IT teams can play a major role depending on the nature of the change. Their involvement must meet a specific need. Communications helps make messages understandable and regular. Training develops skills. Human resources supports changes in roles, skills or employee relations. IT teams ensure that tools genuinely enable the new practice.

The risk is to treat these functions as simple service providers brought in late. When involved from the outset, they can identify constraints, anticipate needs and contribute to a more consistent experience for teams. For example, training designed before usage has stabilized may teach actions that have to be changed soon afterward.

Communication deserves particular attention. Its role is not to embellish a decision or silence concerns. It should help everyone understand what is changing, why, for whom and where to find an answer. The most effective messages are often those that answer a concrete field question rather than simply stating a broad ambition.

Clarifying responsibilities without adding governance burden

A responsibility matrix can be useful, provided it remains easy to understand. For each important action, specify who does the work, who makes the decision, who must be consulted and who must be informed. The goal is not to create a bureaucratic document: it is to avoid gray areas that slow action or cause tensions.

It is also useful to make disagreements open to discussion. Some matters fall under the sponsor, particularly priority decisions. Others can be resolved by the project manager, managers or the teams themselves. When the decision-making level is known, discussions become more effective and employees better understand what can change.

Keeping roles active throughout the transformation

Change management does not end when a solution is deployed. Roles must remain active during adoption. The sponsor continues to support decisions when old habits return. The change manager observes feedback and adjusts support. The project manager corrects operational difficulties. Managers monitor integration into daily work. Employees indicate what helps and what still blocks progress.

Group activities can support this dynamic if they serve a clear purpose. A shared activity replaces neither decisions nor managerial dialogue, but it can help a team experience its ability to cooperate, communicate under constraints or distribute initiatives. In the programs we have organized, the median group size is 32 people: this format highlights the importance of designing discussions in which everyone can find their place, rather than settling for a top-down message.

An urban exploration game can therefore provide a useful debriefing tool when a team has just gone through a change or needs to strengthen its ways of working together. It makes it possible to observe concrete behaviors: sharing information, making decisions, listening to less obvious ideas or managing the unexpected. To connect this experience to a broader approach, discover why your company needs team building.

The debrief is what turns the activity into learning. It can focus on what the team observed about its reflexes, the roles spontaneously taken by each person and the practices it wants to preserve at work. The aim is not to claim that a complex change can be solved in one activity, but to create a shared language and concrete situations from which discussion can become more precise.

Mistakes that weaken role allocation

The first mistake is appointing an absent sponsor. A person may have formal authority without actually performing the role. If they do not support the issue, resolve tensions or give the project visibility, the other stakeholders lose an essential point of reference. It is better to define realistic involvement and maintain it than to display symbolic support.

Another mistake is asking communication to solve a decision-making or resource problem. Messages cannot compensate for an inconsistent organization, unprepared managers or an unsuitable tool. Communication supports change; it does not replace preparation and decision-making.

Objections should also not be treated as automatic opposition. Some reactions express an understandable concern, while others reveal an overlooked impact. Listening does not mean abandoning the transformation. It means distinguishing between a need for explanation, a necessary adaptation, training or a decision that needs to be confirmed.

Finally, an overly complex system can distract from the real work. If employees no longer know whom to contact, if every choice requires distant approval or if meetings multiply without decisions, governance itself becomes an obstacle. Roles should provide clarity and the ability to act, not add another layer of procedures.

Assessing adoption rather than completion alone

A change cannot be considered established because a message has been sent or a tool is available. It is more useful to observe the quality of usage, the questions that remain, workarounds, positive initiatives and the teams' ability to solve problems. These signals provide information about actual adoption.

Managers and champions are particularly well placed to gather these observations, provided they are taken seriously. Regular feedback makes it possible to identify a team that lacks support or a procedure producing unexpected effects. The change manager can then propose a targeted action, and the sponsor can intervene when the obstacle goes beyond the local level.

Success depends less on perfect communication than on responsibility being assumed at every level. The sponsor provides direction and makes decisions. The change manager organizes support. The project manager makes the solution workable. Managers embed it in daily work. Employees and champions provide essential knowledge of the field. When these roles respond to one another, change stops being a distant decision and becomes an evolution that the team can understand, discuss and implement.