Leadership & change
Is Your Team Ready for Another Change? A Practical Guide for L&D Leaders
A new platform, a revised operating model, an AI pilot and a leadership development programme can each have a convincing business case. Put them into the same quarter, with the same people expected to participate, and the combined demand can become unrealistic.
This is change saturation: the organisation asks people to absorb more change than they can reasonably practise, apply and sustain.
For learning and development leaders, the challenge goes beyond finding space in the training calendar. It means understanding what teams are already being asked to change—and whether they have room to turn new learning into everyday behaviour.
Look at the demand on people
Portfolio plans often show budgets, milestones and delivery owners. They also need to show which teams must attend workshops, redesign processes, test systems and learn new ways of working.
Consider a customer service team introducing an AI assistant while migrating its case management system. Both initiatives may require the same experienced colleagues to support testing, training and operational cover. Separate project plans can conceal that collision.
A useful question for every initiative is: Whose time and attention does this require, and when?
Bring L&D into prioritisation early
Involving L&D after a launch date has been committed leaves little room to shape a realistic learning journey.
Earlier involvement allows learning teams and business sponsors to agree:
- Which roles need new capability.
- What people should be able to do differently.
- How much practice and manager support will be needed.
- Which other changes affect those same people.
- What evidence will demonstrate application at work.
A training session is one part of that commitment. Preparation, practice, feedback and follow-through also need time.
Connect learning to real work
Training delivered too early can lose relevance before people can apply it. Training delivered too late leaves teams improvising during implementation.
Connect each learning activity to an upcoming task. A product team might practise prioritisation using its next backlog review. Managers preparing for AI adoption might assess one real workflow before considering wider deployment.
This gives participants a clear reason to learn and creates an opportunity to observe whether the learning helps.
Measure application alongside attendance
Attendance shows participation. It does not establish whether people can use the capability.
Depending on the programme, useful evidence might include the quality of a prioritisation decision, a completed workflow assessment, an observed coaching conversation or a team’s ability to identify and manage delivery dependencies.
Agree the evidence before delivery. Give managers a clear role in supporting practice afterwards.
For example, after a prioritisation workshop, a manager could observe the next planning discussion: can the team explain its choices, acknowledge capacity limits and agree what to defer? That provides a practical basis for feedback and further support.
Make capacity a leadership decision
When several initiatives compete for the same team, a longer training calendar will not resolve the conflict.
Leaders may need to sequence initiatives, reduce scope, protect practice time or defer a lower-priority commitment. These decisions belong in portfolio discussions, alongside funding and delivery risk.
Before approving the next programme, ask: What will these people need to stop, postpone or do differently to make room for this change?
If there is no credible answer, the adoption plan needs more work.
Planning a capability programme alongside organisational change? Talk to Agilinks about training and coaching shaped around your teams’ priorities and working context.