sisr2018 10 Techriques for Data Qualily Root-Cause Analysis - Data Quality Pro Blog Virtual Sum Training ¥ Jobs » 10 Techniques for Data Quality Roc Home => Blog >> Data Quality >> 10 Techniques for Data Quality Root-Cause Analys's Tackling Data Quality Root-Cause Issues How do you get started with identifying the true causes of defects? This article examines 10 techniques that are proven to help you get to the heart of your data quali! and move from a reactive to proactive and longer-term defect elimination. 1. Focus on problems that impact custome satisfaction It costs time and many valuable resources to resolve root-cause issues so targeting improvements directly benefit the customer is often a reasonable starting point. Categorisation and prioritisation is vital here so please read the sections below on how to use Pare analysis and create a fishbone diagram. htps:shwew.dataqualiypro.conv10-techniques-for-data-qualy-rook-cause-analysis! 19sisr2018 10 Techriques for Data Qualily Root-Cause Analysis - Data Quality Pro A Cause and Effect (C&E) Matrix is also a useful tool for linking process or data failures to custome Here is an example of a template we found on the internet: http://www.kevinotto.com/RSS/Software/DMAIC%20C&E%20Matrix%20Template.x|s 2. Eliminate the short-term practice of dat cleansing Data cleansing is one of the biggest cost-inducing activities of any business. Cleansing is typically z activity that delivers a quick-fix, tactical solution for a particular system or line-of-business but oft nothing to prevent issues either up or down the information chain. Data cleansing is not a scalable solution. By ignoring the root-cause of an issue we create a much |: problem as a single fault typically manifests itself exponentially as it interacts with different proce people and systems across the business. For these reasons, although it may appear a cheaper solution locally, long-term it is always far mor expensive to the business as a whole. Tip: Identify areas where data cleansing is taking place as an additional starting point for your root-cause efforts. 3. Ensure information chains are accurate detailed We've covered the basic process of creating information chains before in Data Quality Pro and the pivotal to root-cause analysis. ‘Armed with an information chain, you will have a simple yet effective tool when carrying out your activities (see below). They do need to be well maintained, sufficiently detailed and continuously monitored to help you « data flows however so don't treat information chain creation as a one-off exercise. htps:shwew.dataqualiypro.conv10-techniques-for-data-qualy-rook-cause-analysis! 29ayaz018 10 Techriques fr Data Quay Root. Cause Analysis - Data Quality Pro Tip: By monitoring information chains regularly you will create an early-warning system that can identify potential causes are impacting your business. A. Include external data sources in your roi cause investigation We can take all available measures to ensure defect-free data in our organisation but ultimately if flowing into our business from 3rd parties this can pose a weak spot. Ensure you have an effective supplier management policy in place complete with service level agre that continuously monitor and report defects. We need to monitor these external flows regularly so we can alert the business when a breach int been found. Tip: Don't be territorial over these monitoring processes and reports, share the logic and the approach wit so they can implement pre-delivery checks. This creates a win-win scenario as it will help them improve sc ratings and reduce penalty charges not just on your agreement but their other clients. 5. Use the 5 Why’s to discover multiple cat The 5 Why's root-cause discovery process is fairly well known but is covered here for clarity. It is typically used when interviewing those who work along the information chain to investigate p root-causes. The interviewer simply asks "Why?" a particular condition arises, in an iterative fashion. One question people occasionally raise is “When do we stop asking why?”. This is very subjective but | typically halt the process when I derive at a cause that the organisatior sufficiently equipped and resourced to tackle. Tip: Don't just rely on ‘why: analysis. Iso ask the what/when/where/how type questions to, it will give a much ric htps:shwew.dataqualiypro.conv10-techniques-for-data-qualy-rook-cause-analysis! 319