Skip to main content

When Change Management and ServiceNow Policies Conflict

I was recently asked this question... "Say an RFC is submitted between Mon - Fri and the CAB is on a Tuesday the following week. We are finding the following issues.

1. The approvals within the ServiceNow workflow have not been approved by individuals within the RFC workflow, for example, the architecture or security team.

2. Due to a delay in approvals not being actioned by individuals by the time of the weekly CAB the change implementation dates need to be postponed and rescheduled until all approvals have been completed and change Comms sent out.

How can the above 2 issues be addressed?"

Addressing the issues related to the approval delays in the change management process could involve several strategies:

  • Improving Approval Turnaround Time
    • Automated Reminders and Escalations
      • Automated Reminders: Configure ServiceNow to send automated reminders to approvers at set intervals. These reminders should escalate in urgency the closer it gets to the CAB meeting.
      • Escalation Path: Implement an escalation path where if an approval is not completed within a certain time frame, it gets escalated to a higher authority or an alternate approver.
    • Clear SLAs and KPIs
      • SLAs for Approvals: Define Service Level Agreements (SLAs) for each approval step. For instance, the architecture or security team must complete their review within 48 hours.
      • KPIs for Approvers: Introduce Key Performance Indicators (KPIs) for approvers, which can be monitored and reported on regularly. This can help identify bottlenecks and hold individuals accountable.
    • Streamlined Approval Processes
      • Simplify Approval Criteria: Ensure that the approval process is as streamlined as possible. Only essential approvals should be included to avoid unnecessary delays.
      • Pre-approved Standards: For routine changes, establish pre-approved standards that do not require individual approvals for each instance.
  • Ensuring Timely Change Implementation
    • Enhanced Communication
      • Pre-CAB Communication: Implement a pre-CAB review meeting where pending approvals are discussed, and blockers are identified early. This can help ensure that all necessary actions are taken before the formal CAB.
      • Real-Time Status Updates: Use ServiceNow’s dashboard and reporting features to provide real-time status updates on the approval process. This can help track the progress and identify any pending actions promptly.
    • Flexible Scheduling
      • Buffer Time: Schedule changes with a buffer period to account for potential delays in approvals. This allows some flexibility without impacting the overall change schedule.
      • Expedited Changes: For urgent changes, have a fast-track approval process that can be utilized when necessary.
  • Additional Strategies
    • Training and Awareness
      • Training Programs: Conduct regular training sessions for all stakeholders involved in the approval process to ensure they understa

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...