This content was created by Richard Schreiber. This content was uploaded by Richard Schreiber. This is a YouTube video titled "FAQ 3 part 2" featuring Richard Schreiber, the Software Whisperer, discussing strategies for implementing new software, including the use of pilot groups and change management techniques to ensure successful deployment and user buy-in.
Chapters
Hello again, Richard Schreiber, the Software Whisperer. Well, we talked in our last video about what's the best way to implement new software, and we describe two cases, one where you're deploying new software to replace legacy or older software, and another case where you're actually replacing a manual process. We talked about the importance of a pilot group as the typical way that new software is is rolled out so that it's tested with a small group of sometimes super users. But remember that it's critical to support this pilot group with enough resources so that they don't become disillusioned by the inevitable defects that may come up. See, a pilot group should be taught to expect defects and how to record them so that the developers can fix those defects, because it's impossible to detect every defect, even during user acceptance testing and lots of other manual testing. Change management is about getting users buy in really from the outset by telling them how the new system will improve the way that they do things versus the old system. It might be a different way that they have to learn, but ultimately it's better for them, better for their situation. But you want those pilot users to become good ambassadors to the software so that they help in rolling it out to the other user groups. This is Richard Schreiber, the Software Whisperer. Keep asking those questions.
