A senior leader sends the launch email, appears in a short video and tells everyone that the change matters. The project team is pleased to have visible backing. A fortnight later, managers are struggling to release people for training and two departments are working towards different priorities.
That is where sponsorship becomes practical. I see the sponsor’s role as a continuing responsibility for the conditions in which people can adopt the change. An announcement opens the conversation; the decisions, attention and follow-through after it show people whether that support will last.
Make the role specific
Start by agreeing what the sponsor needs to do personally. A broad promise to support the programme leaves too much room for interpretation. Name the decisions only that leader can make, the other leaders they need to engage and the groups that need to hear directly from them.
Prosci describes sponsorship through active participation, building support among leaders and communicating with those affected. Those responsibilities provide a useful starting point. The practical next step is to translate them into a small set of actions connected to the organisation’s actual work.
For a new service process, that might mean agreeing the operational priority, resolving a conflict between two directors and attending a manager discussion about implementation. A sponsor should be able to see why each request requires their authority, rather than receiving an undifferentiated list of meetings.
Explain the business reason in everyday language
People need to understand what problem the organisation is trying to solve. The sponsor can explain why the current position is no longer sufficient, what a better outcome would look like and how the change connects to commitments the organisation has already made.
Use examples that make sense to the audience. A colleague dealing with repeated customer calls may understand reducing avoidable hand-offs more readily than a phrase about strategic transformation. Explain the consequence for the work, while being honest about what is still being designed.
Repeat the reason at meaningful points rather than simply repeating the launch message. When a milestone moves or a design changes, explain what that means for the original purpose. People can cope with an evolving route more easily when they can still recognise the destination.
Align the leaders whose priorities affect delivery
Support from one executive does not automatically create support across the organisation. A change can depend on technology, operations, finance and people teams making compatible choices. The sponsor needs to identify where those choices meet and where unresolved differences could obstruct adoption.
Have the difficult conversations before passing instructions down through management layers. If one department is measured on speed and another on additional checks, staff may receive conflicting signals. A friendly programme update cannot settle a disagreement about which outcome takes priority.
Record the agreement in language managers can use. For example, leaders might agree that additional learning time will be protected during the first two weeks, with a temporary adjustment to output expectations. The useful result is a clear operating decision, not simply a statement of collective enthusiasm.
Protect the capacity needed to learn
Training attendance, practice and local problem-solving consume time. If the sponsor asks people to adopt a new way of working while every existing target remains fixed, managers may have no workable route to comply. Make the capacity requirement visible alongside the delivery dates.
Ask what will stop, move or receive temporary cover. The answer should identify an owner and an agreed period. Where capacity cannot be released, revisit the rollout sequence or scope rather than leaving the project team to absorb an impossible commitment through extra communication.
Consider a contact team learning a new case system. An hour in training may also require shift cover and time afterwards to practise unfamiliar tasks. The sponsor does not need to design the rota, but does need to support the trade-off that makes the rota possible.
Equip managers for the next conversation
Managers need enough context to explain what changes for their teams and enough authority to respond to practical concerns. Give them a short conversation guide, known impacts, an escalation route and a clear statement of which questions are still awaiting a decision.
The sponsor should reinforce that asking questions is part of implementation. A manager who raises a genuine operational problem should not feel that they are being disloyal. Useful challenge can expose an assumption early enough for the organisation to improve the approach.
Keep the feedback loop visible. If several managers ask the same question, decide whether the problem lies in the message, the design or an unresolved policy. Updating an FAQ may help, but some questions require a decision that only a senior owner can make.
Stay available when the work becomes awkward
Sponsors are often busiest when programmes need them most. Agree a predictable contact rhythm and a route for genuinely urgent decisions. A short, prepared discussion can be more effective than a large steering meeting where the important issue appears at the end of the agenda.
Bring a clear request. Explain the problem, the options, the operational consequences and the decision date. A change practitioner can help the sponsor use their time well by separating matters requiring executive authority from those the delivery team can resolve itself.
For example, two functions may both need the same specialists during a critical week. The sponsor’s contribution is to agree the organisational priority with the relevant leaders. Asking the project manager to negotiate indefinitely simply moves an authority problem to someone who cannot settle it.
Look at adoption alongside delivery progress
A completed installation or an issued procedure shows that an output exists. It does not show whether people can use it in ordinary conditions. Ask for a small amount of evidence about the behaviours, confidence and operational results the change is intended to support.
That evidence might include observed task completion, recurring support questions or the use of old workarounds. Interpret it alongside workload and local circumstances. A lower usage figure may reveal a genuine process obstacle, rather than a lack of effort from the people affected.
Agree what the evidence will change. If an important task is still failing, decide whether to adjust support, fix the design or slow the next rollout. Reviewing a dashboard becomes useful when it leads to a proportionate response with a named owner.
Respond to concerns without labelling people
The word resistance can hide several different problems. Someone may disagree with the purpose, lack the skill to perform a task, fear an unintended consequence or be protecting a service that the project has not fully understood. Begin by finding out which problem is present.
A sponsor can create room for honest discussion while remaining clear about decisions already made. Explain what is open to influence and what is fixed. Avoid inviting feedback in a way that implies every aspect of the change can be renegotiated when that is not true.
Then report what happened to the concern. An answer might be a design adjustment, additional support or an explanation of why the proposed route remains. Even an unwelcome decision is easier to understand when the reasoning and accountability are visible.
Continue beyond the first successful week
Once the initial pressure reduces, it is tempting to withdraw attention immediately. Keep enough sponsorship in place to check whether new practices survive normal workload, staff absence and competing demands. Confirm who owns the next review before the project team reduces its involvement.
Recognise useful progress specifically. Highlight a manager who protected learning time or a team that identified a defect before it affected customers. This tells people which contributions matter and avoids treating adoption as a competition to report the most positive story.
Effective sponsorship is visible in what leaders make possible. If your programme needs stronger sponsorship, clearer manager support or a better connection between delivery and adoption, I would be happy to discuss an approach that fits the organisation and the decisions ahead.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
