>> Each onboarding session had to be customised to their specific needs.@Ed Braunbeck ?super important point. I think using the customer's language in the training decks and co-developing the training material with a couple of managers and users from their team really helped us with some very large rollouts (1000+ users) of a chat product I used to lead. We can also leave that customised training material and recording of the session with them.
@Katherine Bentley do share what else you try out with this customer
Andrew makes some important points around training, change management, shared plans, and expectations.
Here are a few more tips assuming you are talking about large / enterprise clients:* Have a solid agenda for your kick-off meeting that addresses the methodology, goals, rules of engagement and escalations, and expectation setting. "Well begun is half done" is something I've truly come to believe in. Use the kick-off to align and energise the teams, and to lock-in resources you need from the customer side to make the onboarding a success.* Set up a cadence of meetings with a steering committee (project executive sponsor, project champion, potentially 1-2 other execs) maybe once in 2-3 weeks to ensure that any blockers are resolved fast, trade-off calls are taken instantly, and there is clarity around goals and success.* Have a phased roll-out ensuring enough ROI in phase 1 to showcase success and keep the momentum behind the product adoption going* Choose the right capabilities to roll-out and also the right initial group to roll-it out to. You want to get your customer to identify their team members with a growth mentality who welcome change and see the big picture around your product. So the first 5-10 users become your evangelists for the next 90.* Ensure you have sign-offs on the goals and what success should mean* Don't fall into the trap of trying to address everything the old system handled in the same way - this is part of change management, but be intentional around pushback on things that your new system doesn't need that customers may still ask for moving from a legacy experience.Hopes these pointers are helpful!