Organizations constantly require changes that widely differ in their processes. You can define the life cycle of changes and track every step of the process by using change workflows.
Workflows are helpful in two main ways:
- To set up the notification matrix for technicians involved in different stages in the change workflow
- To design workflow for changes that stand out of the general cases and that require quick processing or special attention
General workflow: For changes that essentially require the processing of all 6 stages.
Emergency workflow: Changes that are highly pressed for time, such as, server restart for an application or a system that stops working, connection severing for vulnerability attacks, banking website crash, etc. These changes require immediate action and need not go through the usual 6 stages fo the workflow, but rather a simplified workflow with a few stages skipped.
- The change must occur in a high impact asset (asset used by a group of people) such as printers, routers, access points or in a working configuration such as Active Directory server, SAP server, etc.
- The change must have already been approved