Setting Expectations for Functional Imperfections, Process Changes & Learning Curves When Implementing New Software

Time: 2:40 pm
day: Day Two


• Explaining what tasks will change and which will stay the same after buy-in to avoid disappointment
• Avoiding shiny object syndrome to ensure that new software is being used to its full extend after implementation
• Ensuring you have enough resources to implement the new software before buy-in to streamline the implementation process