Latest Articles

Every Major Incident Deserves a Major Problem Review — Here's How to Do It Right When to Conduct a Major Problem Review Team members should carry out in-depth reviews of major problems. When a Major Incident occurs, a problem should always be raised. After resolution, team members should carry out in-depth reviews of major problems. What a Major Problem Review Covers A major problem review should cover: What happened: The incident timeline and events Why it happened: Root cause analysis What worked: What went well in the response What could have been better: Areas for improvement What we learned: Key lessons and insights What we'll do differently: Action items and follow-up The Major Problem Review Process Step 1: Schedule Promptly Schedule the review within 5 business days of the incident. Quickness matters—details are fresher, and the incident is still top of mind. Step 2: Gather Participants Include: Incident Commander (if used) Technical responders Problem Manager Service owners Management (for significant incidents) Step 3: Prepare the Review Collect: Incident timeline Communications Actions taken Root cause analysis Resolution details Step 4: Conduct the Review Review the incident timeline Discuss the root cause Identify what worked well Identify areas for improvement Document action items Step 5: Follow Up Assign owners to action items Set due dates Track completion Share learnings Key Questions to Ask Area Questions Detection How was the incident detected? Could it have been detected faster? Response Was the response effective? What could have been better? Communication Were stakeholders informed appropriately? Resolution Was the resolution effective? Could it have been faster? Prevention What could prevent recurrence? Learning What can we learn from this incident? Major Problem Review Template Incident Summary Date and time Duration Severity Impact Timeline When events occurred Key decisions Communications Root Cause What caused the incident Contributing factors What Worked What went well What Could Have Been Better Areas for improvement Lessons Learned Key insights Action Items # Action Owner Due Date 1 Action Name Date Conclusion Major problem reviews are essential for learning from significant failures. By conducting thorough reviews, organizations can prevent recurrence, improve response, and build resilience. Action Items for Your Organization Establish a major problem review process Create a major problem review template Schedule reviews promptly after major incidents Assign action items with owners and due dates Share learnings across the organization

Are You Doing Change Management or Just Going Through the Motions? — The Change Maturity Model The Maturity Model Change management maturity describes how advanced your change enablement practice is. Low maturity means changes are slow, risky, and often fail. High maturity means changes are fast, safe, and deliver business value. Maturity Levels Level 1: Initial/Reactive Characteristics: Ad-hoc processes Inconsistent execution High failure rate No formal roles Reactive problem-solving Signs you're at Level 1: Changes often fail or cause incidents No formal change process Emergency changes are the norm Level 2: Repeatable Characteristics: Some process exists Inconsistently followed Basic categorization Some documentation Emerging accountability Signs you're at Level 2: Change process is documented Some changes are tracked Approval process exists Level 3: Defined Characteristics: Standardized process Documented workflows Clear roles and responsibilities CAB functions effectively Change types are used Signs you're at Level 3: Process is consistently followed Changes are categorized Success metrics are tracked Level 4: Managed Characteristics: Process performance is measured Proactive improvement Risk-based decision-making Integration with other processes Change success rates are high Signs you're at Level 4: Metrics are used for improvement Changes are fast and safe Change success is tracked Level 5: Optimizing Characteristics: Continuous improvement Integrated with DevOps AI-driven decision-making Automated approvals for low-risk changes Proactive risk management Signs you're at Level 5: AI assists in risk assessment Standard changes are fully automated Change is viewed as an enabler, not a barrier Maturity Assessment Questions Area Question Process Is there a formal, documented change process? Categorization Are changes categorized appropriately? CAB Does the CAB function effectively? Risk Is risk assessed consistently? Metrics Is change performance measured? Automation Are low-risk changes automated? Integration Is change integrated with other processes? Building a Roadmap Level 1 → Level 2: Document the process Define roles Track changes Level 2 → Level 3: Categorize changes Establish CAB Define workflows Level 3 → Level 4: Implement metrics Proactive improvement Integrate processes Level 4 → Level 5: Automate approvals AI integration Continuous improvement Conclusion Change management maturity is a journey. Organizations that assess their maturity and build a roadmap for improvement will achieve faster, safer changes and better business outcomes. Action Items for Your Organization Assess your current change management maturity Identify gaps in your process Build a roadmap to the next level Measure progress over time Celebrate improvements

Your Kubernetes Cluster Just Failed — Which Cloud Is Responsible? The Multi-Cloud Incident Challenge Modern enterprises run highly distributed, hybrid, multi-cloud environments made up of heterogeneous platforms, interconnected applications, and third-party integrations. When an incident occurs in a multi-cloud environment, the challenges multiply: Challenge Description Which cloud is responsible? Multiple clouds, multiple responsibilities What are the dependencies? Interdependencies across clouds Who should be notified? Multiple teams, multiple clouds What's the impact? Complex service mapping How to remediate? Different tools and processes across clouds The Unified Alerting Challenge Alerts come from multiple sources: Source Type Example SNMP traps Network devices Router alerts Syslog messages System components Server alerts xMatters events Service platform Service alerts Cloud platform alerts Cloud providers AWS CloudWatch Kubernetes events Container platform Pod failures Each differs in format, granularity, and context, posing a significant challenge for unified incident handling. Multi-Cloud Incident Response Framework Step 1: Unified Alerting Consolidate alerts from all clouds and platforms. Approach Description Cloud-native Use each cloud's native alerting Cross-cloud Use tools that can monitor multiple clouds Unified Use a platform that consolidates alerts Step 2: Service Mapping Understand service dependencies across clouds. Need Challenge Service mapping across clouds Which services depend on which? Blast radius assessment What services are affected? Business impact assessment What business functions are impacted? Step 3: Coordinated Response Respond effectively across clouds. Need Challenge Cross-cloud coordination Teams across clouds need to coordinate Unified tooling Consistent incident management tools Communication Stakeholders need consistent updates SIAM for Multi-Cloud Incident Response SIAM (Service Integration and Management) is particularly relevant for multi-cloud incident response. SIAM Principles Applied to Multi-Cloud Principle Application Unified governance Single governance across clouds Cross-provider processes Consistent processes for all clouds Integrated tooling Tools that work across all clouds Shared accountability Clear accountability for each cloud SIAM Roles for Multi-Cloud Incident Response Role Responsibility Multi-Cloud Incident Commander Coordinates across clouds Cloud Technical Leads Technical leads for each cloud Cross-Cloud Communications Communications across clouds Real-World Impact Global Energy Leader A global energy leader with 55,000 users implemented a structured SIAM framework to: Strengthen collaboration across key business stakeholders Synchronize workflows between processes and tools Implement predictive monitoring to identify potential high-severity issues early Enrich their CMDB with accurate configuration data Standardize onboarding and offboarding of suppliers across 11 key partners Conclusion: Multi-Cloud Incident Management Is Complex—But Manageable Multi-cloud incident management is more complex than single-cloud incident management. But with the right framework—unified alerting, service mapping, coordinated response, and SIAM—it's manageable. The key is not to treat each cloud in isolation. The key is to treat them as an integrated whole. Action Items for Your Organization Implement unified alerting: Consolidate alerts from all clouds Build service mapping: Understand dependencies across clouds Define cross-cloud processes: Consistent incident response across clouds Consider SIAM: Implement SIAM for multi-cloud governance Train teams: Ensure teams understand multi-cloud incident response

How Mature Is Your Controls Management Program? — Use This Self-Assessment to Find Out The Maturity Self-Assessment This self-assessment tool helps you evaluate the maturity of your controls management program across five domains. Scoring Instructions Score each dimension from 1-5: 1 = Not Yet Started: No formal approach 2 = Initial: Basic approach, inconsistent 3 = Defined: Standardized approach, documented 4 = Managed: Measured, monitored, improved 5 = Optimizing: AI-driven, continuous, self-healing Domain 1: Control Design Dimension 1 2 3 4 5 Controls are documented           Controls are linked to requirements           Controls are designed for testability           Control ownership is assigned           Technology dependencies are documented           Score (1-5): _____ Domain 2: Control Operation Dimension 1 2 3 4 5 Controls are executed consistently           Controls are evidenced           Controls are tested regularly           Exceptions are managed           Controls are reviewed regularly           Score (1-5): _____ Domain 3: Control Monitoring Dimension 1 2 3 4 5 Controls are monitored           Key Risk Indicators are tracked           Key Control Indicators are tracked           Alerts are in place           Monitoring is continuous           Score (1-5): _____ Domain 4: Control Automation Dimension 1 2 3 4 5 Evidence collection is automated           Control assessments are automated           Remediation is automated           Controls are AI-augmented           Controls are self-healing           Score (1-5): _____ Domain 5: Control Governance Dimension 1 2 3 4 5 Control ownership is clear           Control accountability is enforced           Controls are integrated with ITSM           Controls are rationalized           Controls are continuously improved           Score (1-5): _____ Results Interpretation Average Score: _____ Score Range Maturity Level Description 1.0-1.9 Initial Ad-hoc, inconsistent, reactive 2.0-2.9 Repeatable Basic processes, emerging consistency 3.0-3.9 Defined Standardized, documented, consistent 4.0-4.4 Managed Measured, monitored, improved 4.5-5.0 Optimizing AI-driven, continuous, self-healing Maturity Level Descriptions Initial (1.0-1.9) Controls are not documented or consistently executed No formal controls management process Reactive to issues Audit readiness is low Repeatable (2.0-2.9) Some controls are documented Basic process exists Inconsistent execution Emerging ownership Defined (3.0-3.9) Controls are documented and linked to requirements Standardized process Consistent execution Clear ownership Managed (4.0-4.4) Controls are measured and monitored Continuous improvement Integrated with other processes Strong visibility Optimizing (4.5-5.0) AI-driven controls Self-healing capability Continuous compliance Fully integrated Improvement Roadmap If you scored mostly 1-2 (Initial/Repeatable): Focus on documenting controls and establishing basic processes Assign ownership Implement basic testing If you scored mostly 2-3 (Repeatable/Defined): Standardize processes Formalize testing Establish evidence collection If you scored mostly 3-4 (Defined/Managed): Implement continuous monitoring Track KRIs and KCIs Automate evidence collection If you scored mostly 4-5 (Managed/Optimizing): Implement agentic AI Enable self-healing controls Achieve continuous compliance Conclusion Controls maturity is a journey. This self-assessment helps you understand where you are and build a roadmap to where you want to be. Action Items for Your Organization Complete the controls maturity self-assessment Identify your maturity level Build a roadmap to the next level Measure progress regularly Celebrate improvements

Service Request Management Isn't About Tickets — It's About Employee Experience The Connection Between Service and Experience Service request management significantly impacts employee experience and satisfaction. Quick and transparent handling of requests boosts morale and confidence in management . The Connection: Driver Impact Satisfied employees More engaged and productive Engaged employees Higher performance Lower turnover Stable, experienced workforce Employee Experience Success Indicators Quick and transparent handling of requests: Employees feel valued when their requests are handled efficiently Confidence in management: When employees see things get done, they trust leadership Reduced frustration: No more guessing about request status or chasing responses How Service Request Management Affects EX Positive Impact Negative Impact Fast, automated resolution Slow, manual processes Transparent status tracking Requests disappear into the void Consistent experience Different experiences for different departments Easy self-service Complex forms and navigation Supportive, helpful interactions Frustrating, confusing responses Measuring Employee Experience Metric What It Measures CSAT Satisfaction with service NPS Willingness to recommend Effort score How easy was the interaction? Resolution time How quickly was it resolved? Repeat contact Was it resolved the first time? Conclusion Service request management isn't about tickets — it's about people. Organizations that design service experiences around employees will see better satisfaction, engagement, and retention. Action Items for Your Organization Survey employees on their service experience Identify friction points in the request process Design service experiences around employee needs Measure and track employee satisfaction Use feedback to improve

You Can't Improve What You Don't Measure — Key Change Enablement Metrics Why Metrics Matter Measuring change management effectiveness helps organizations : Identify areas for improvement Demonstrate the value of change management Make data-driven decisions Track progress over time Key Change Management Metrics Readiness Metrics Employee readiness assessment results: How prepared are employees for the change?  Employee engagement, buy-in, and participation measures: How engaged are employees in the change process?  Stakeholder sentiment tracking: How do employees feel about the change?  Training Metrics Training participation, tests, and effectiveness measures: Are employees completing training and learning?  Training completion rates vs. behavior change observed: Is training translating into behavior change?  Adoption Metrics Usage and utilization reports: Are employees using the new tools or processes?  Compliance and adherence reports: Are employees following new processes?  % of users actively using the system post-go-live: What percentage are actually using the change?  Help Desk Metrics Internal help desk metrics: Tickets solved, tickets reopened, ticket escalations, issues by resolution area  Incidents and problems: Are change-related issues decreasing?  Business Impact Metrics Observations of behavioral change: Are employees working differently?  Project KPI measurements: Are project goals being met?  Benefit realization and ROI: Is the change delivering business value?  Adherence to timeline: Is the change on schedule?  How to Use Metrics For Improvement Identify problem areas: Which aspects are underperforming? Track trends: Are adoption rates improving? Benchmark: How do you compare to targets? For Stakeholder Communication Show value: Demonstrate the impact of change efforts Build credibility: Data-backed reporting builds trust Justify investment: Show where resources are needed The ITIL Perspective Key metrics for ITIL change enablement include : Percentage of changes implemented without incidents Average time from request submission to deployment (by change type) Number of changes that resulted in unplanned downtime Mean Time to Recover (MTTR) for issues caused by changes Conclusion Measuring change management success requires a balanced set of metrics covering readiness, training, adoption, and business impact. Organizations that measure effectively can identify problems, track improvements, and demonstrate value. Action Items for Your Organization Define your key change management metrics Set up measurement and reporting Establish baseline measurements Review metrics regularly Use data to drive improvement