6
The Change Interventions (the how)

Change Management for Technology Projects 3

  • Upload
    dmdk12

  • View
    1.374

  • Download
    2

Embed Size (px)

DESCRIPTION

Change Management for Technology Projects 3

Citation preview

Page 1: Change Management for Technology Projects 3

The Change Interventions (the how)

Page 2: Change Management for Technology Projects 3

CurrentState

Future State

Page 3: Change Management for Technology Projects 3

Ownership

Page 4: Change Management for Technology Projects 3

1. Use Stakeholder and Change Readiness Analysis as a basis

1. Think carefully about what needs to be achieved with each contact and what communication method you should use.

2. Provide clear and unambigous messages.

3. Use a mixture of media – make it interesting for the audience.

4. Determine level of emotional content

5. Don’t over-communicate. Keep communications relevant and let people know when they’ll receive the next update.

6. Senior management should be seen to drive the communications. Sponsor to delivers key messages.

7. Ensure the project team all understand the key programme messages and communications – don’t let them misinform the stakeholders by mistake.

8. Constantly review communications for effectiveness.

Gu

idelin

es

Page 5: Change Management for Technology Projects 3

Pro

cess

1. Intent and strategic alignment

2. Roadmap3. Roles

4. Practical progress5. Responses to feedback6. Quick wins

7. Closure8. Lessons learnt9. Next steps

Page 6: Change Management for Technology Projects 3

Tools

Tool What When

Project Kick Off Kick Off Meeting to finalize process and gain clarity about high level roles

At commencement of project

Team meetings Working meetings to progress analysis, design or to discuss issues/progress on the project

Throughout the project for the project team and on a regular basis incorporating the associate members.

War room A dedicated project room with all material associated with the project on the walls

Throughout the project for the project team and those directly involved and affected

Syndicationworkshops

Interactive meeting with team members/business core team or executive members (from the business) to resolve issues, develop a concept/solution or other deliverable.

Workshops to ensure alignment of expectations and deals with bottle necks – throughout the process

Conference Room Pilot

A walk through of the system in a replicated user environment

Prior to Go Live and Go live Support

Review workshop

A structured walkthrough of the design (could be any deliverable in draft form) with key staff in the business. It is designed for participants to test the design for robustness and identify issues.

As and when required throughout the process

Solution or Blueprint Fair

A walkthrough of the solution, new working practices etc.

At the end of the Blueprinting Phase

Town meeting A conference where participants are sitting in tables of approx. 10 and can discuss the concepts and give feedback. Can cater for 100+ participants

Start of the Blueprinting Phase

Road show Presentation to a wide audience on key themes regarding the programme.

Useful for presenting ideas and concepts to wide audience.– following the Stakeholder and Resistance to Change Analysis

Notice board Use of companies existing notice/communications board

For messages to be broadcast to all outside the project team, if an established method within the organisation – throughout the project

Newsletter A publication highlighting project news and success

Throughout the project

Updates Updates (by e-mail, voicemail, intranet, notice board etc.) that indicate project progress or a significant event

Can be used on a regular basis for progress reporting or on an exceptional basis for success briefings or issues.