Latest Articles

Headline: Excessive Controls Dilute Assurance — Rationalization Creates Leaner, More Effective Controls The Controls Proliferation Problem Over time, layers of controls have been accumulated in response to regulatory changes, incidents, breaches, and shifting organizational priorities. The result is often a complex and burdensome framework weighed down by excess controls—many of which are inefficient, redundant, or misaligned with actual risk and compliance needs . The consequences of controls proliferation: Demonstrating effective risk management becomes difficult  Increased risk of non-compliance as controls are misaligned with regulatory expectations  Ineffective assurance and audit fatigue as excessive controls dilute testing capacity  Ineffective and complex change management as it's harder to update and embed controls  Why Rationalization Matters Excessive controls create more problems than they solve: They consume resources without adding value They dilute assurance by spreading testing capacity thin They create audit fatigue through repetitive testing They make change management harder The solution: rationalization. The Control Rationalization Process Step 1: Diagnose and Prioritize Assess the current control landscape to identify duplication, inefficiency, and manual effort. Focus on controls that are needed to meet regulatory obligations and/or address the most significant risks . Key questions: What controls do we have? What regulatory obligations do they address? What risks do they mitigate? Are they effective? Are they efficient? Step 2: Benchmark and Rationalize Compare practices against peers and regulatory standards. Consolidate and streamline controls to close gaps and prioritize effectively . Rationalization options: Action When to Use Eliminate Control is redundant, outdated, or not addressing a real risk Consolidate Multiple controls address the same risk or obligation Automate Control is manual and can be automated Redesign Control is ineffective or inefficient Retain Control is effective and efficient Step 3: Automate and Modernize Leverage data, automation, and AI to enhance monitoring, testing, and reporting. Embed smarter oversight and enable continuous improvement . Step 4: Strengthen Governance Clarify ownership and accountability, align controls to legal duties, and ensure they remain defensible and agile . The Governance Gap Problem Organizations may experience a persistent gap between what platforms report and how their organization behaves under pressure. Incidents recur, risks emerge unexpectedly, and cultural or coordination failures undermine otherwise well-designed controls . The core problem: Most platforms are built to manage artifacts and abstractions, not the living system of people, processes, and technologies that produce real outcomes . The solution: Rationalization must address not just control design but also operational reality. The Regulatory Driver Regulatory obligations are increasing year-on-year, and enforcement is tougher, which raises the risk and cost of non-compliance . Regulators expect high standards of compliance and have very low tolerance for contraventions . Key questions for rationalization: Does this control actually meet the regulatory requirement? Is it designed to be defensible? Can we prove it operates effectively? Conclusion Control rationalization is essential for effective controls management. Organizations that rationalize their control environments will reduce costs, improve assurance, and meet evolving regulatory expectations. Action Items for Your Organization Map your current control landscape Identify duplication and inefficiency Prioritize controls based on risk and regulatory requirements Eliminate redundant controls Consolidate overlapping controls Automate manual controls Strengthen governance and ownership

Headline: Stop Reacting to Change Resistance — Predict Where It Will Happen and Intervene Early The Power of Predictive Analytics One of the most powerful applications of AI in change management is predictive analytics. It helps change management experts see where they might hit bumps and how to manage them proactively . "This is where AI is going to offer the most powerful strategic value," Sergi said. "It will help us move from being reactive to predicting" . Forecasting Productivity Dips Productivity dips are a normal part of change, as employees adjust to new tools or processes. But if change managers have an idea where they'll occur, they can set expectations with company leaders in advance . Sergi gives the AI historical data, employee demographics, and process changes, and asks it to forecast the likely dip in the recovery curve for productivity. This allows her to prepare interventions and communicate proactively. Identifying At-Risk Employees AI can also identify employees who may be at risk for struggling with change, based on factors like : Role complexity: Employees with complex, interdependent roles Adaptability: Historical patterns of how employees respond to change Engagement metrics: Participation in change-related activities Sentiment scores: Employee sentiment from surveys and communications Importantly, this doesn't mean people will be singled out as laggards. AI-generated predictive analytics simply give change managers a better sense of which employees might need extra support or proactive coaching . How Predictive Analytics Works in Practice The process typically involves : Collecting historical and real-time data on adoption, behavior, and performance Using machine learning models to identify patterns that preceded past challenges Forecasting outcomes for current change initiatives Providing actionable insights for proactive intervention Practical Applications Application How It Helps Timing optimization Determine the best time for rollout Support targeting Identify groups needing extra support Resource allocation Allocate resources where they're needed most Risk mitigation Address potential resistance before it escalates Conclusion Predictive analytics shift change management from reactive problem solving to proactive planning . By anticipating where challenges will emerge, change managers can intervene early and keep transformation on track. Action Items for Your Organization Collect historical change data for AI analysis Identify key predictive metrics (engagement, sentiment, adoption) Implement predictive analytics tools Use insights to guide change interventions Measure the impact of predictive insights on change success

80% of Problems Come from 20% of Causes — Pareto Analysis Identifies What Matters Most The Pareto Principle The Pareto Principle (the 80/20 rule) suggests that roughly 80% of effects come from 20% of causes. Applied to problem management, this means that a small number of root causes are responsible for the majority of incidents. What Is Pareto Analysis? Pareto Analysis is a statistical technique used to identify the most significant causes contributing to the problem. By focusing on the "vital few" rather than the "trivial many," teams can maximize the impact of their problem management efforts. How to Perform Pareto Analysis Step 1: Collect Data Gather data on incident causes over a defined period: Track incident categories Record root causes Count frequency of each cause Step 2: Categorize Causes Group incidents by cause or category: What are the most common categories? What are the most frequent root causes? What systems have the most incidents? Step 3: Sort and Calculate Sort causes from most frequent to least frequent Calculate the percentage of total incidents for each cause Calculate the cumulative percentage Step 4: Create a Pareto Chart Bar chart showing frequency of each cause (descending) Line chart showing cumulative percentage Step 5: Identify the "Vital Few" Identify causes that account for 80% of incidents Focus problem management efforts on these causes Example Pareto Analysis Data from a service desk: Cause Count % of Total Cumulative % Password resets 450 30% 30% Application crashes 300 20% 50% Network issues 250 17% 67% Email problems 180 12% 79% Printer issues 120 8% 87% Other 200 13% 100% The "vital few" : Password resets, application crashes, network issues, and email problems account for 79% of incidents. Action: Focus problem management on these four areas. Benefits of Pareto Analysis Benefit Impact Focus Teams concentrate on what matters most Resource allocation Invest where returns are highest Quick wins Fixing top causes has immediate impact Strategic planning Data-driven decision making When to Use Pareto Analysis Scenario Use Case Many causes When there are too many potential causes to address all at once Data available When you have data on cause frequency Resource constraints When you need to prioritize Quick results When you need to show impact quickly Combining Pareto with Other Techniques Pareto identifies which causes to investigate (top 20%) 5 Whys investigates each of the top causes Ishikawa diagrams show the relationships Conclusion Pareto Analysis helps organizations focus on the "vital few" causes that generate the majority of incidents. By targeting these causes, problem management teams can have the greatest impact with limited resources. Action Items for Your Organization Collect data on incident causes over a defined period Perform Pareto Analysis on the data Identify the "vital few" causes Focus problem management resources on these causes Track the reduction in incidents from top causes

 Problem Management Doesn't Operate in a Silo — How Integration Creates a Resilient IT Ecosystem The Integration Imperative Problem management should not operate in isolation. Integrate it with incident management, change management, and knowledge management to ensure a holistic approach to IT service management . Integration with Incident Management The Problem-Incident Relationship Although Incident Management and Problem Management are separate processes, they are closely related and will typically use the same tools, and may use similar categorization, impact and priority coding systems. This will ensure effective and consistent communication when dealing with related incidents and problems . Key integration points: Incidents trigger problems (recurring incidents, major incidents) Problems have linked incidents Known errors help resolve incidents faster Incident trends inform problem priorities Integration with Change Management The Problem-Change Relationship Within problem management, the Request for Change (RFC) ticket will be the output for fixing errors where cause is known . Key integration points: Problems generate change requests to implement fixes Change management tracks implementation of fixes Problems can be updated with change status Changes can be linked to problems ServiceNow integration: Enables the creation of change requests directly from the problem record, ensuring a seamless transition from problem management to change management. Integration with Knowledge Management The Problem-Knowledge Relationship Problem Management will also maintain information about the appropriate workarounds and resolutions to problems, so that the number and impact of incidents can be reduced over time. In this respect, Problem Management has a strong interface with Knowledge Management, and tools such as the Known Errors Database (KEDB) will be used to document workarounds and root cause . Key integration points: Known errors are documented in the knowledge base Workarounds are captured as knowledge articles Problem insights inform knowledge creation Knowledge helps prevent incident recurrence Integration Benefits Benefit Description Faster resolution Known errors help incidents resolve faster Better data quality Consistent data across processes Complete visibility See the full picture across processes Knowledge sharing Lessons learned are captured and shared Risk reduction Changes are evaluated before implementation The Integration Ecosystem text Incident Management → Problem Management        ↓                      ↓ Problem Management → Change Management        ↓                      ↓ Problem Management → Knowledge Management        ↓                      ↓ Knowledge Management → Incident Management How to Implement Integration 1. Use a Unified Platform The same ITSM platform for all processes Consistent data models Built-in integrations 2. Define Integration Points What data is shared? When do handoffs occur? Who is responsible? 3. Configure Integrations Link incident and problem records Create change requests from problems Publish known errors to the knowledge base 4. Train Teams How the processes work together When to transition between processes How to use integrated tools Conclusion Problem management is most effective when integrated with incident, change, and knowledge management. This integration creates a resilient ITSM ecosystem where learning is captured, fixes are implemented, and incidents are prevented.