How do I improve inconsistent and incomplete data documentation? What has worked for your team?
Sort By:
Oldest
CIO in Education2 years ago
Incomplete data documentation has caused a lot of issues for analytics and insights. Consolidating data silos and sources, integration of CMS platforms worked for our team to improve inconsistent and incomplete data documentation.CIO in Consumer Goods2 years ago
This is quite a broad question, so a few considerations are necessary to determine actions.1. Is the missing/inconsistent data identifiable? Can it be intercepted by rules? Could these rules be applied to fix/normalise the data?
2. If it cannot be identified or addressed in 1. above, can the impact be quantified? Will the analysis be flawed in the absence of correction, or can it be excluded/ignored/minimised in terms of the impact on the outcome.
3. If after 2. it is still an issue, then do not use the output/outcome, because the decisions will be based on flawed inputs
Chief Technology Officer in Manufacturing2 years ago
A year back, we took three actions to improve this. 1. Hired an outside agency to train resources on how the documentation consistency, completeness and quality can be improved and what are the parameters that need to be kept in mind
2. A peer review mechanism started to check quality, consistency and completeness of documentation. For this a new step in the workflow was added and AI was used to select right peer to review. This is helpful as the creator can not collaborate with the peer reviewer in advance (as each qualified and first time right document enters into a raffle)
3. A competition where the best work has to be nominated by the creator and winners get a reward and recognition. Also, the best work was earmarked in our collaboration app so that those can be used as benchmarks for future documents
So far working well and now we have up the ante so looking to take this next level
Chief Information Officer in Healthcare and Biotech2 years ago
Keep the documentation in a simple format so that it’s not viewed as an overhead. Build the review process in quick cycles so that the time gap is eliminated and there by procrastination of documentation
Carrot vs Stick for compliance is unavoidable
Chief Technology Officer (CTO) in Software2 years ago
Having the documentation process as part of the development cycle. The issue is not complete until the documentation has been updated and verified. It also needs to become part of the company culture as a whole such that it will stand out when it is not completed.