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

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?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the...

The Four Ps of Service Design - It’s not all about Technology

In the rapidly evolving landscape of IT service management (ITSM), the principles of service design have expanded beyond just focusing on technology. As we embrace new methodologies and innovations in 2024, the Four Ps of Service Design remains a critical framework to ensure comprehensive and effective service delivery. See also: The New Four P's of Service Management These Four Ps are People, Processes, Products, and Partners. 1. People: At the core of any service design are the people who deliver and consume the services. In today's world, this includes a diverse range of stakeholders from employees and customers to vendors and partners. Effective service design considers user experience (UX) and employee experience (EX) to ensure services are intuitive and meet the needs of all users. The rise of AI and automation has transformed roles, making it essential to invest in continuous learning and development to keep skills relevant. 2. Processes: Streamlined and efficient proc...