I've transitioned large numbers of people onto new systems (operating and other) and I've hit just about every problem along the way. When you're introducing s

I've transitioned large numbers of people onto new systems (operating and other) and I've hit just about every problem along the way. When you're introducing somebody to a new system, it's not enough to say "ah it looks they same, so they'll be okay". Visual parity helps but people very quickly get hesitant if things have different names, and it gets worse if they have muscle memory for certain operations that now don't work. Sometimes it's better that things don't look the same: Uncanny Valley is a real thing that upsets people. If it looks the same but works differently, it may as well look different. On your description I would suggest that document management is probably going to be your biggest focus. You need to familiarise yourself with the tasks that get performed, and also how they get performed. When jumping between office suites, people often struggle with the cooky names everything gets. Neither Excel or Calc say Spreadsheet. Consider altering your launchers. Icons can help too. Documents and downloads need to be in expected places and also look right (type icons). You also have to consider what happens when something breaks. This might be global, this might just be a particular function like printing, but veteran users usually find a way around problems that don't involve bug reports and a 2 week wait. > for upcoming event What's your lead time here? Deploying something significantly new to production without some burn-in and fault-finding time is a mistake, whatever the change. Check that there are no device requirements your solution won't fulfil (eg does it work with projectors) There's nothing wrong with Linux. Most people can get along with it fine. The Power Karens in here likening this to abuse are over-reacting. Ask her to try it. See if it sticks.