Clear priorities, practical support and shared responsibility help teams put new ways of working into practice.
Organisational change rarely fails because the idea behind it was poor. More often, a sensible change loses momentum because people are unsure what it means for their work, lack the time or skills to adopt it, or receive mixed signals about how much it matters. Leaders have considerable influence over each of these factors, and the way they behave during a change often shapes the outcome more than the plan itself.
This article looks at four areas where leadership makes a practical difference, with illustrative examples, common pitfalls and questions leaders can ask themselves along the way.
Explain the purpose and listen
Leaders influence how teams understand and respond to change. Explain the problem, the intended outcome and what is still uncertain. Give people a practical way to raise concerns.
Reflection can help leaders recognise where their own decisions or habits need to change. It works best alongside evidence from the people affected.
A clear explanation of purpose answers three questions: what problem are we solving, what will be different when we succeed, and why now. It also acknowledges what is not yet known. People tend to trust leaders who are open about uncertainty more than those who present every detail as settled, particularly when later developments reveal that it was not.
Listening needs to be practical rather than symbolic. A single town hall with a short question session will not surface the concerns of people who are uncomfortable speaking in a large group. Smaller conversations, anonymous feedback routes and time set aside in team meetings give a fuller picture. What matters most is that people can see their input being considered, even when the answer is that something cannot change.
Consider a hypothetical finance function introducing a new approval process. The leadership team explains the purpose clearly, but only after listening to team leads do they learn that month-end deadlines make the proposed go-live date unworkable. Moving the date by a few weeks costs little and signals that feedback has consequences.
Connect the vision to everyday work
A broad ambition needs practical decisions about priorities, time and responsibilities. Explain what will change for each team and what support will be available.
Avoid assuming agreement means readiness. People may understand the purpose while still needing information, skills or capacity to participate.
A vision statement can be accurate and still leave people unsure what to do on Monday morning. Translating it into everyday terms means being specific for each group affected: which tasks will change, which tools they will use, what will stop and when. Without this translation, teams fill the gap with their own assumptions, which are often more worrying than the reality.
Capacity is a frequent blind spot. If a team is asked to learn a new way of working while maintaining its existing workload in full, adoption will be slow and resentment will build. Leaders should decide what can be paused, deferred or supported temporarily, and say so explicitly. This is one of the clearest signals that the change is a genuine priority.
Useful questions for leaders at this stage include:
- Can each affected team describe what will be different for them?
- Have we made room in workloads for people to learn and adapt?
- Do people have the information and skills they need, or only the explanation?
- Are our own decisions and behaviours consistent with what we are asking of others?
Share responsibility clearly
Senior sponsorship matters, but change also depends on delivery leads, managers, specialists and users. Agree what each group owns and how issues move between them.
Give teams appropriate authority and resources. Clear expectations make it easier to act while keeping important decisions visible.
A sponsor sets direction, secures resources and resolves conflicts that others cannot. Delivery leads plan and coordinate the work. Line managers translate the change for their teams and notice early when something is not working. Specialists contribute expertise in areas such as data, compliance or technology. Users test, adopt and refine the new approach. Each role is necessary, and confusion between them is a common reason for delay.
It helps to write down who owns which decisions and how issues are escalated. This does not need to be elaborate. A simple table of decisions, owners and escalation routes, reviewed periodically, prevents many of the stalls that occur when everyone assumes someone else is responsible.
A common pitfall is delegating responsibility without authority. If a manager is accountable for adoption in their team but cannot adjust priorities or request support, they will struggle to act. Equally, leaders should avoid stepping back entirely once delivery begins. Visible, consistent sponsorship throughout the change tells people it still matters.
Support learning and review progress
Provide opportunities to try the new approach, learn from feedback and adjust. Respond constructively to difficulties, while keeping the intended outcome in view.
People adopt new ways of working through practice, not only through explanation. Training is most effective when it is close to the real task, delivered at the point people need it and followed by support as they begin using the new approach. Short guides, drop-in sessions and named colleagues who can answer questions all help to bridge the gap between learning and confident use.
Reviewing progress should combine measures and conversation. Usage figures or process times can show whether a change is being adopted, but they rarely explain why. Regular check-ins with teams reveal the practical obstacles that numbers miss. Communication and visible identity can also help a change feel coherent, for instance when an internal service team brings its information and tools together in one recognisable place, as in our intranet and branding programme for an internal services team.
When difficulties arise, the leadership response sets the tone. Treating early problems as information rather than failure encourages people to report issues while they can still be fixed. At the same time, leaders need to keep the intended outcome in view so that adjustments improve the change rather than gradually abandon it.
Where to start
A practical first step is to test the current plan against the four areas above. Can the purpose be explained simply? Does each team know what will change for them? Are responsibilities and authority clear? Is there a plan for learning, support and review? Gaps in any of these areas are usually easier to address before delivery begins than after.
Glyz supports programme delivery, change management and training. Through our capability and change service, we help leaders translate a proposed change into a plan that teams can understand, adopt and sustain.
