Change Management in a very complex Research Organization

yehardeb1

Starting to get Involved
#1
Morning,

I am currently contracting in a very complex but exciting business model. It is research that is trying to operate commercially and has a mixture of scientists and engineers.

The business operates roughly 9 different versions of change management through IT and software, hardware, technical change, property, document control as it has an inherent culture where people like to do there own thing - this is changing, pardon the pun.

We are in the process of trying to remove the various iterations of change and pull everyone with us on this journey, we now have a high level flow of how to manage change (based on CM2) and trying to think configuration management.

Our stumbling block is - we kind of understand the concept of managing change at this high level however we are all divided on how to actually implement "the doing" of change. For example, we operate systems and changing a configurable item has effects on the wider system which is managed through projects and baselines and if we implement a change we should be managing this through a sub lifecycle and each type of change i.e. hardware / software has different sub lifecycles and this is where confusion is driving the opinion apart.

As I said, a very complex research organisation.

Has anyone got ideas to share, industry best practices, contacts, reference materials that could help us better understand on how to apply change management into a business? Also any industry standards that could help us that could be relevant?

I would appreciate anyone's advice please!
 

somashekar

Staff member
Super Moderator
#2
Morning,

I am currently contracting in a very complex but exciting business model. It is research that is trying to operate commercially and has a mixture of scientists and engineers.

The business operates roughly 9 different versions of change management through IT and software, hardware, technical change, property, document control as it has an inherent culture where people like to do there own thing - this is changing, pardon the pun.

We are in the process of trying to remove the various iterations of change and pull everyone with us on this journey, we now have a high level flow of how to manage change (based on CM2) and trying to think configuration management.

Our stumbling block is - we kind of understand the concept of managing change at this high level however we are all divided on how to actually implement "the doing" of change. For example, we operate systems and changing a configurable item has effects on the wider system which is managed through projects and baselines and if we implement a change we should be managing this through a sub lifecycle and each type of change i.e. hardware / software has different sub lifecycles and this is where confusion is driving the opinion apart.

As I said, a very complex research organisation.

Has anyone got ideas to share, industry best practices, contacts, reference materials that could help us better understand on how to apply change management into a business? Also any industry standards that could help us that could be relevant?

I would appreciate anyone's advice please!
Very complex.... A simple solution can be Time.
A reasonable deadline within which everything is made to happen, then changed and run for analysis.
 

yodon

Staff member
Super Moderator
#3
Sounds like you need a "systems" champion - someone who sees / manages the big picture and can control / direct changes at the high level while allowing the lower level teams to manage the changes according to the direction of the upper level.
 

yehardeb1

Starting to get Involved
#4
Does anyone have any examples of a successful change management system that implements and control configurable systems?

Any organisations / training consultants that anybody can recommend? I would be very keen to hear from you.

Many Thanks
 

Top Bottom