In all your software deployments did you blame the users for not getting it or did you redesign the software because it sucked (according to your users)?
Comment on UK government trial of Microsoft's M365 Copilot finds no clear productivity boost
ExcessShiv@lemmy.dbzer0.com 4 weeks agoHaving been part of multiple projects introducing new software tools (not AI) to departments before, people are usually just stubborn and don’t want to change their ways, even if it enables a smoother work-flow with minimal training/practice.
rebelsimile@sh.itjust.works 4 weeks ago
ExcessShiv@lemmy.dbzer0.com 4 weeks ago
I was one of the users, these are my observations with my colleagues reactions.
rebelsimile@sh.itjust.works 4 weeks ago
That’s not what I’m asking. You designed or built something for some users. They didn’t like it, or didn’t use it as you expected. Was your response to change the software or blame the users for not using it correctly?
sugar_in_your_tea@sh.itjust.works 4 weeks ago
That depends on the issue. Sometimes it’s a lack of training, sometimes it’s obtuse software. That’s a call the product owner needs to make.
For something like AI, it does take some practice to learn what it’s good at and what it’s not good at. So there’s always going to be some amount of training needed before user complaints should be taken at face value.
Lyrl@lemmy.dbzer0.com 4 weeks ago
I’ve occasionally been part of training hourly workers on software new to them. Having really, really detailed work instructions and walking through all the steps with themthe first time has helped me win over people who were initially really opposed to the products.
My experience with salaried workers has been they are more likely to try new software on their own, but if they don’t have much flexible time they usually choose to keep doing the established less efficient routine over investing one-time learning curve and setup time to start a new more efficient routine. Myself included - I have for many yeara been aware of software my employer provides that would reduce the time spent on regular tasks, but I know the learning curve and setup is in the dozens of hours, and I haven’t carved out time to do that.
So to answer the question, neither. The problem may be neither the software nor the users, but something else about the work environment.
Jhex@lemmy.world 4 weeks ago
The devil is in the details… what you describe screams to me what I call the “new boss syndrome”. New boss comes in and they feel the need to pee on everyone to mark their territory so they MUST bring in some genius change.
99% of the time, they are bringing in some forced change for the sake of change or something that worked on their previous place without taking into consideration the context.
I do not know almost anyone who prefers to work harder… either the changes proposed make no sense (or it’s too complex for people to understand the benefit) or the change is superfluous. That is usually where resistance to change comes from.