Common Enterprise Wide Data Governance Issues: #2 The quality of data entered by front-end staff is not as high as desired

This post is one of a series dealing with common Enterprise Wide Data Governance Issues.  Assess the status of this issue in your Enterprise by clicking here:  Data Governance Issue Assessment Process

Causes:

  1. Front-end staff are put under pressure to ‘sell business’ and sort out details later.
  2. Front-end staff have no incentive to enter high-quality data.
  3. Front-end staff are unaware of the downstream impact of poor data.
  4. Little realisation on the part of front-end staff that data entered at account opening may be re-used repeatedly for 30+years.
  5. Front-end systems may lack data validation software.
  6. Front-end systems may not enforce business rules between related fields.
  7. Reluctance to add data validation to legacy Front-end systems

Impact:

  • Incomplete or poor quality ‘informational’ or ‘Master data’ captured at data entry.
  • Risk that the enterprise and/or individual business units will fail to comply with regulatory requirements (e.g. the requirement to ‘Know your customer’).

Solution:
Agree and implement the following policies:

  1. Data owners must define the business rules to be applied to each data item at data entry time.
  2. Data owners must agree Data Quality requirements with the end users of the data, and the owners of the data entry processes.
  3. Data owners must agreee Data Quality Service Level Agreements with the end users of the data, and the owners of the data entry processes.
  4. Data Quality measurement must be implemented at each point of data entry to measure the quality of data being entered, and support the implementation of data quality Service Level Agreements.
  5. Front-end staff must be educated on the importance of data quality
  6. Front-end staff must be supported in taking the time and effort to “get it right first time”

Your experience:
Have you faced the above issue in your organisation, or while working with clients?  What did you do to resolve it?  Please share your experience by posting a comment – Thank you – Ken.

Common Enterprise Wide Data Governance Issues: #1 The quality of informational data is not as high as desired

In most Financial Institutions, transactional data quality is quite good across the Enterprise, in that customers transactions are successfully processed.

However, the quality of informational data (Master Data), such as customer details, is typically not as good as desired.  This is the ‘generic data governance issue’ that faces most organizations.   In this series of posts, I will take this high level data governance issue to a lower level of detail.

This post is one of a series dealing with common Enterprise Wide Data Governance Issues.  You can see the full list, together with the process for assessing the status of the issues in your Enterprise by clicking here:  Data Governance Issue Assessment Process

Your experience:
Have you faced the above issue in your organisation, or while working with clients?  What did you do to resolve it?  Please share your experience by posting a comment – Thank you – Ken.

Common Enterprise Wide Data Governance Issues: #3 No culture of Data as an ‘asset’, or ‘resource’

Some enterprises fail to recognise the true value of their data.  This post is one of a series dealing with common Enterprise Wide Data Governance Issues.  Assess the status of this issue in your Enterprise by clicking here:  Data Governance Issue Assessment Process

Impact:

  • There is little value attributed to capturing and maintaining high quality ‘informational’ or ‘Master data’.
  • The other Enterprise Wide Data Governance Issues in this series are all symptoms of the failure of the enterprise to treat Data as a corporate asset.  An Enterprise that treats Data as a valuable corporate asset understands the value of data, and is likely to have addressed the issues I have identified.

Solution:
Agree and implement the following policies:

  • Data must be treated as a valuable Enterprise asset, that can assist the Enterprise achieve its strategic objectives, and must be invested in proportionally to other Enterprise assets.
  • The CIO is responsible for ensuring that the quality of Master data is measured, target data quality levels are agreed, and measures are implemented to meet the defined targets.

Your experience:
Have you faced the above issue in your organisation, or while working with clients?  What did you do to resolve it?  Please share your experience by posting a comment – Thank you – Ken.

Common Enterprise Wide Data Governance Issues: #4 No clear ownership of data

In many large organisations, it is unclear as to who ‘owns the data’.   There is no one responsible for providing existing data to new projects that require it.   There is no one responsible for measuring, or maintaining data quality.  It is unclear who to ask when looking for information, e.g. to satisfy new regulatory requirements.  This post is one of a series dealing with common Enterprise Wide Data Governance Issues.  Assess the status of this issue in your Enterprise by clicking here:  Data Governance Issue Assessment Process

Impact:
New projects dependent on existing data (especially Master Data) must locate the data from first principles, and face the risk of not finding the data, or identifying inappropriate sources.   New projects dependent on existing data take longer than necessary to complete.  Multiple re-invention of the wheel results in the creation of islands of data, and a maintenance nightmare.

Solution:
Agree and implement the following Data Ownership policies:

  1. Overall ownership for data within the Enterprise lies with the CIO.
  2. Ownership for data within each Business Unit lies with the CIO and the head of the Business Unit.
  3. The CIO and head of each business unit must appoint a person with responsibility for the provision of data from that business unit, to those who require it.  This person is also responsible for the measurement and maintenance of data quality within the business unit.
  4. The CIO and head of each business unit must appoint a single point of contact to handle requests for data / information.

Your experience:
Have you faced the above issue in your organisation, or while working with clients?  What did you do to resolve it?  Please share your experience by posting a comment – Thank you – Ken.