Significant organizational change can be brought about by your technology projects, and if you are not careful, chaos can be created. In this video, Bob McGannon takes you through the steps to imbed organizational change including having a plan, communication, evaluation of roles, training and measuring the effectiveness of your solution. In addition, he will explore obstacles to progress including potential power shifts, current experts preserving their roles, and other resistant stakeholders.
- Deepak Chopra is quoted as saying,…"All great changes are preceded by chaos."…Now I hope that's not true for our technology projects,…but the reality is we can create chaos if we're not careful.…Significant organizational change can be brought about…by your technology projects.…Earlier I discussed how to identify…the specific business processes that will be changing.…In this video I'm going to give you tips…to assess the degree of organizational change…that may result from your project,…and how your project can be used to steer that change.…
Let me give you an example.…Several years I was implementing a solution…for a trucking company,…so they could maximize truckloads in both directions.…We decided to deploy GPS technology,…which was new at the time.…Both the management team and the truckers…supported this change because full truckloads…meant more money for both parties.…However, as the solution was getting…close to implementation,…the truckers realized the technology…would also provide details of the exact location…
- Identify three characteristics of the ideal To Be process map.
- Summarize the steps to manage organizational change.
- Recognize three details to consider when evaluating a cloud solution.
- Recall the consequence of failing to address functionality gaps in a technical solution.
- Determine which facts to collect before discussing resource availability with sponsors.
- Identify the questions to ask when asking team members for feedback on milestone development.