SUCCESSFUL CHANGE MANGEMENT GINA MINKS GINA MINKS CONSULTING, LLC - - PowerPoint PPT Presentation

successful change mangement
SMART_READER_LITE
LIVE PREVIEW

SUCCESSFUL CHANGE MANGEMENT GINA MINKS GINA MINKS CONSULTING, LLC - - PowerPoint PPT Presentation

SUCCESSFUL CHANGE MANGEMENT GINA MINKS GINA MINKS CONSULTING, LLC SEPTEMBER 2019 THIS WEBINAR WILL COVER: Creating a How change can Ideas for identifying communication plan impact your projects project stakeholders for stakeholders and


slide-1
SLIDE 1

SUCCESSFUL CHANGE MANGEMENT

GINA MINKS GINA MINKS CONSULTING, LLC SEPTEMBER 2019

slide-2
SLIDE 2

THIS WEBINAR WILL COVER:

How change can impact your projects Ideas for identifying project stakeholders

Creating a

communication plan

for stakeholders and why it’s so important

The decision-making process for implementing change The advantages of using workflows to aid change management What constitutes an effective workflow for changes

slide-3
SLIDE 3

RISK MANAGEMENT VS CHANGE MANAGEMENT

RISK

Identified and mitigated during the project planning process

High probability risks are addressed before the project begins

CHANGE

Unexpected and often not addressed in the original project processes

Relies on specific techniques for successful implementation of change

Change

Risk Change Management is ALWAYS Risk Management BUT Risk Management is NOT ALWAYS Change Management

slide-4
SLIDE 4

WHY CHANGE?

slide-5
SLIDE 5

DRIVING FORCES OF CHANGE:

 Crisis  Organizational Structure  T

echnology

 Business Processes  Internal / External Pressure  Opportunities  Planned Abandonment  Just Because….

slide-6
SLIDE 6

HOW CHANGE IMPACTS PROJECTS

slide-7
SLIDE 7

HOW CHANGE CAN AFFECT A PROJECT

 Budget  Scope  Schedule  Staff  Quality of Work  Support  Credibility

slide-8
SLIDE 8

SUCCESS OR FAILURE? IT DEPENDS…

 Nature of the change  Consequences of the change  Organizational history of change  Individual personality types  Individual experiences with change

slide-9
SLIDE 9

CHANGE MANAGEMENT -- SUCCESS

 The software technician is hit by a bus. A new tech is hired and can quickly come up

to speed on duties because of detailed project documentation and current status reports.

 An unexpected software upgrade is scheduled so any delays won’t immediately affect

student, faculty or staff work.

 A “special edition” e-newsletter is sent to the public keeps everyone informed of

project delays due to weather issues.

 Explicit instructions are sent to staff about how to change their passwords after a

security breach.

slide-10
SLIDE 10

CHANGE MANAGEMENT -- FAILURE

 Institution changes from Office 365 to G-Suite without confirming all the business

processes work with G-Suite tools.

 Content Management system is implemented without confirming it works with

legacy data.

 Failing to communicate an extreme delay in implementation leads administration to

believe project is a failure and budget is allocated elsewhere.

 A new tracking system for email and work projects is implemented without staff

input or training opportunities.

slide-11
SLIDE 11

THREE C’S OF CHANGE MANAGEMENT

COMMUNICATION COORDINATION CONTINUITY

slide-12
SLIDE 12

THREE C’S OF CHANGE MANAGEMENT

COMMUNICATION WITH STAKEHOLDERS COORDINATION OF TASKS CONTINUITY OF OPERATION

slide-13
SLIDE 13

FINDING THE RIGHT CHANGE AGENT

slide-14
SLIDE 14

QUALITIES OF A CHANGE AGENT

 Clear vision  Patient yet persistent  Asks tough questions  Knowledgeable and leads by example  Strong relationships built on trust

slide-15
SLIDE 15

DESIGNATING A CHANGE AGENT

plpnetwork.com

Different Skills than the Project Manager

Cuturally Sensitive

Inclusiveness Awareness of Others

Entrepreneurial

Innovative Resilient

Socially Responsible

Stakeholder Focus Commitment to results Active Learner

Self-awareness Flexible thinking Developing others

slide-16
SLIDE 16

THE CHANGE AGENT SHOULD:

 Build personal capital  Pick their battles  Fully understand and research the problem  Take the proper approach  Propose solutions, NOT problems  Handle objections properly  Remains positive  Allow leaders to take credit  Be willing to compromise  Keep trying

slide-17
SLIDE 17

COMMUNICATION WITH STAKEHOLDERS

slide-18
SLIDE 18

IDENTIFYING STAKEHOLDERS - CPIG

 Customers  Providers (Internal or External)  Influencers (Internal or External)  Governance

REMEMBER: Forgetting a stakeholder can be detrimental to the project/change Review stakeholders throughout the project

Consider creating a stakeholder profile

slide-19
SLIDE 19

Reaction = Shock/Denial

Communicate

Reaction = Frustration/Depression

Listen to Concerns & Offer Support

Reaction = Willing to Experiment

Allow time to explore & test

Reaction = Accept Change

Celebrate the Commitment

How Do Stakeholders Deal with Change?

slide-20
SLIDE 20

COMMUNICATION PREFERENCES

Channel

 Email  Phone  Face-to-Face  Physical report  Meeting

Message

 Status Update  In-depth  Overview  Administrative information  Public-centered

slide-21
SLIDE 21

IMPLEMENTING CHANGE

slide-22
SLIDE 22

SUCCESSFUL CHANGE = CONSISTENT AND TRANSPARENT

 What information is needed to make a change?  Who can request a change?  What is the process for evaluating the change?  Who can approve a change?  What is the process for communicating the change to stakeholders?  How is the successful change communicated?  How is the change process evaluated?

slide-23
SLIDE 23

WORKFLOWS FOR SUCCESSFUL CHANGE

slide-24
SLIDE 24

DEVELOP A CHANGE MANAGEMENT WORKFLOW

 Identification of issue needing change  Change request  Evaluation of change request  Approval  Implementation of change  Documentation of change  Evaluation of change process

Communication

slide-25
SLIDE 25

CREATE A PROCESS THAT WORKS

Communication to Stakeholders

Identification of Issue Request Change Evaluate Change Request Approval Implementation Documentation

  • f Change

Evaluation of Change Process

slide-26
SLIDE 26

MORE THAN HIGH LEVEL WORKFLOW

Identification of issue needing change – Specific information Change request -- Documentation, impact statement, submission process Evaluation of change request – Who needs to be involved?, What is impacted? Standards?

slide-27
SLIDE 27

MORE THAN HIGH LEVEL WORKFLOW

Approval – Who is authorized to approve the change, dissemination, documentation Implementation of change – How is team empowered to make the change? Workflows, Schedules, Budgets, Staff Documentation of change – Who will document the change to the scope of work, project workflow, etc. Evaluation of change process – Who evaluates, method, documentation, changes to process

slide-28
SLIDE 28

EVALUATING THE CHANGE PROCESS

slide-29
SLIDE 29

LESSONS LEARNED

 What was the business impact? (Remember CoOP)  What did and did not work? (BE SPECIFIC)  Identify process problems  Identify implementation problems  Identify staff / people problems

slide-30
SLIDE 30

CHANGING THE CHANGE MANAGEMENT PROCESS

 Identify the problem  Evaluate the process  Make the change  Communicate the change to the change process

Remember: Every organization is different with different people and different histories.

slide-31
SLIDE 31

A REVIEW OF CHANGE MANAGEMENT

Know your stakeholders

Know

Understand why the change needs to happen

Understand

Communicate the change

Communicate

Implement the change

Implement

Follow a workflow for implementing change

Follow

Evaluate the change

Evaluate

slide-32
SLIDE 32

QUESTIONS??

CONTACT ME:

GINA MINKS

GINA@ GINAMINKSCONSULTING.COM