Specific<\/strong><\/p>\n Benefits that are specific are much easier to showcase and get people behind. Generic benefits can hit a deaf note that no one can identify themselves with. If your benefit answers the 5 W\u2019s \u2013 Who? What? When? Where? Why? \u2013 then it\u2019s probably fairly specific.<\/p>\n Measurable<\/strong><\/p>\n A benefit that is measurable allows you to track progress along the way. It answers the questions \u201chow much?\u201d or \u201chow many?\u201d. Break your broad benefit into smaller chunks. The small victories build excitement and help you maintain motivation and support for your data governance program.<\/p>\n Achievable<\/strong><\/p>\n Achievable benefits are those that the data governance program has the ability to complete with available resources. Ensure when going over that benefit that it contains an action verb explaining how the benefit will be accomplished. It needs to be realistic. Sure, it can be a challenge to get that benefit, but should still be something you can commit to based on the available resources and other priorities.<\/p>\n Relevant<\/strong><\/p>\n It could be a great benefit, such as ensuring regulatory compliance, but if it’s not relevant to your organization, don’t mention it. <\/p>\n Time-bound<\/strong><\/p>\n Benefits that are time-bound give a sense of urgency for completion. You need to define both a start date to do something to address the benefit and an end date to get that benefit by. It\u2019s not always feasible to get that benefit immediately.<\/p>\n","protected":false},"template":"","class_list":["post-3105","tva_lesson","type-tva_lesson","status-publish","hentry","tva_courses-practical-data-governance","post-wrapper","thrv_wrapper"],"yoast_head":"\n