owenhollandsChange control is one topic of IT management that I find most fascinating. Organisations that have never dreamed of trying to document how they do something like capacity management will try and implement a full ITIL compliant change control system. For some reason, change control is so hard to get right.
This blog is about the people side of doing technology, so this post will be about how the people that are hands on with the technology interact with the change control system.
I am going to make this short and sweet.
As someone who is requesting, and making changes (as opposed to one reviewing, approving or managing the process)
- Do you have access to search for previous changes, potentially as part of fault finding?
- Do you get any benefits from the change control system? What are they?
- How much work is it for you to request a change?
- How much additional work is then required for you to get a change approved?
- Do you think the change control system would prevent accidents (like two changes to the same thing at the same time)?
- Do you see the change process as managing change, or simply reducing the number of changes (by making them harder to et approved)?
If you are someone to reviews, approves or manages the change process
- What do you think the people using your process would say about the above changes
Just some rhetorical questions. Personally I am a big believer in change control, but I have seen it “fail to thrive†so many times.