The Change Control process has an unfortunate reputation for burdening IT professionals with unnecessary bureaucracy. A systems engineer will be tasked with filling out a Change Request form, attending the absurd theatre of the Change Advisory Board, and coming up with arguments why the change is "low risk".

Many of the current Change Managers have inherited the process from a predecessor. They have had limited training, and often have no access to the original bodies of knowledge (ITIL, COBIT, ISO/IEC 20000 etc).

Change Enablement

The purpose of Change Enablement (also known as Change Management, or Change Control) is to manage the risk of IT-related change to an organisation. I've put an emphasis on the word "manage" because the Change Manager is not, and must not be involved in the implementation of change.