A change becomes real when someone has to make a different decision, learn an unfamiliar task or give up a way of working they know well. At that point, the quality of leadership is tested in ordinary interactions: how a concern is received, whose judgement is sought and how much responsibility people are trusted to carry.
The second day of Etimad’s Leading Through Change module focused on mobilising people: understanding resistance, involving the right stakeholders and helping teams stay aligned as work changes. The theme I found most useful was the relationship between trust and commitment. A decision may have formal approval while the people responsible for delivering it remain uncertain about its purpose, its consequences or their place within it. Working through that uncertainty is part of the leader’s responsibility.
Understanding resistance and maintaining alignment
Resistance deserves closer attention than it often receives. An experienced employee who questions a new approach may be worried about losing the competence or independence that made them effective. A manager may support the intended outcome while recognising that the transition adds work to an already stretched team. These concerns require different responses.
Before deciding how to intervene, it helps to ask a more precise question: what is this person trying to protect? The answer could point to a legitimate operational risk, a gap in training, an unclear responsibility or a concern about status. Understanding the issue gives a leader something concrete to address.
Consider, for example, a supervisor asked to take responsibility for a new area of work. Hesitation may reflect uncertainty about the decisions they are authorised to make or the support available if something goes wrong. A conversation about those boundaries can be more useful than another explanation of why the initiative matters. The response should fit the concern.
This also requires honesty. Some changes involve difficult trade-offs, and leaders cannot promise that everyone’s responsibilities will remain the same. Credibility depends on explaining what has been decided, acknowledging what remains unresolved and being specific about the support available. Reassurance becomes useful when people can see what it means in practice.
Maintaining alignment also means explaining what will remain consistent. A team can adapt its methods while keeping its commitment to service, safety or professional standards. Naming those continuities makes the direction easier to understand. It also gives colleagues a practical reference when an unexpected situation forces them to choose between competing demands.
Mobilising influence and collaboration
Another lesson concerns influence. An organisational chart identifies reporting relationships and formal authority, but it offers only a partial picture of whose opinion people trust. A long-serving colleague, a technically respected employee or someone who connects different teams may shape how an initiative is understood throughout the business.
Identifying these people requires attention to how work actually happens. Who is asked for advice when an unusual problem arises? Whose judgement carries weight in a difficult discussion? Who can explain an unfamiliar decision in language colleagues understand? Involving these individuals early can reveal concerns that a formal review might miss.
A respected sceptic can be particularly valuable. Someone prepared to question an assumption may help identify a weakness before it becomes expensive to correct. Their involvement needs to be meaningful, with room to influence the approach. Asking for input after every important decision has already been made risks weakening the trust that participation is supposed to build.
Collaboration needs the same attention to underlying causes. If colleagues are reluctant to share expertise because their targets reward only individual output, another meeting will do little to help. If they cannot find the right expertise, a direct introduction may be enough. Where teams use different terminology or assumptions, working through a task together can establish a shared understanding. The leader’s role is to identify the barrier and make cooperation workable.
Listening with accountability
Trust also depends on how people are treated when they speak openly. A leader may invite questions and still discourage them through impatience, defensiveness or an immediate search for someone to blame. Colleagues pay attention to these reactions. They help determine which information will be shared next time.
The useful standard is both openness and accountability. People should be able to raise a concern, acknowledge an error or challenge an assumption respectfully. They should also understand the standards expected of them and take responsibility for agreed actions. These expectations belong together: early disclosure makes corrective action possible, while accountability ensures that the issue is addressed.
Feedback about a leader’s own decisions deserves particular attention. It is easier to report that a task is behind schedule than to explain that the original instruction created confusion. A specific invitation can make that conversation more productive: which part of my decision has made the work harder, or where have I created an unnecessary dependency?
The response matters as much as the question. Listening carefully, checking the facts and resisting the urge to justify every choice can make it easier for colleagues to be candid. The leader still has to exercise judgement. Some suggestions will be adopted, others will need further assessment, and some will be declined with an explanation.
Closing that conversation is essential. When someone raises an issue, they should know what will happen next, who is responsible and when it will be reviewed. Where a concern leads to an adjustment, acknowledging the contribution shows that speaking up has practical value. Where no change is made, explaining the reasoning prevents silence from being mistaken for disregard.
Delegating with clear boundaries
The module also highlighted the need to adjust leadership involvement as a team develops. Early in an unfamiliar task, people may need direct guidance. As capability grows, the leader can move towards joint problem-solving and then greater independence. Continuing to approve every detail after the team is ready to act can create a dependency that slows progress.
Effective delegation therefore needs defined boundaries. The person receiving responsibility should understand the outcome, the decisions they can make, the limits they must observe and the situations that require escalation. A supervisor handling routine purchasing, for example, needs an agreed spending limit, quality requirements and a route for exceptions. Those conditions make independent action more dependable.
Applying the learning
I see a practical application in choosing one current initiative and examining the experience of the people carrying it out. Whose concern has been dismissed too quickly? Whose informal influence has been overlooked? Which decision still comes back to the leader unnecessarily? These questions can expose a specific improvement that is within reach.
The lasting lesson for me is to pay closer attention to what happens when someone offers a view I had not considered. Taking that contribution seriously, making a considered decision and following through are everyday leadership practices. Repeated consistently, they give people greater confidence to take ownership of the work and raise concerns while there is still time to act.
Continue the conversation
Have an opportunity or perspective to share? I welcome a clear introduction.