---
title: Data Governance Content Creation Loop
description: IData Blog | Data Governance Content Creation Loop
image: https://blog.idatainc.com/hubfs/DG_Content_Creation_Loop_Diagram.png
---

[![iData_notag_tm](https://blog.idatainc.com/hs-fs/hubfs/iData_notag_tm.png?width=184&name=iData_notag_tm.png)](http://www.idatainc.com)

# Data Governance Content Creation Loop

## Data Governance Content Creation Loop

[April 22, 2024](https://blog.idatainc.com/archive/2024/04) By  [Jim Walery](https://blog.idatainc.com/author/jim-walery)  In [content](https://blog.idatainc.com/tag/content), [data](https://blog.idatainc.com/tag/data), [governance](https://blog.idatainc.com/tag/governance), [stewardship](https://blog.idatainc.com/tag/stewardship), [definitions](https://blog.idatainc.com/tag/definitions), [glossary](https://blog.idatainc.com/tag/glossary), [business](https://blog.idatainc.com/tag/business), [intelligence](https://blog.idatainc.com/tag/intelligence), [creation](https://blog.idatainc.com/tag/creation), [loop](https://blog.idatainc.com/tag/loop)

Data governance and [data intelligence](https://blog.idatainc.com/data-governance-topics) is not just about content. It is not just about having the information. It is about having processes to help keep that information up to date and a knowledge base to access that information. This blog post will discuss the human curation activity around your data, points of engagement, and the content creation loop.

![DG_Content_Creation_Loop_Diagram](https://blog.idatainc.com/hs-fs/hubfs/DG_Content_Creation_Loop_Diagram.png?width=1042&height=458&name=DG_Content_Creation_Loop_Diagram.png)

In this blog post we will discuss these questions:

- How do people request things?
- How do people find things?
- How do people search for things?
- What do people do if they can't find information around their data?
- How do people engage with the data stewards who have the answers to their requests?
- How does information get captured?

We feel that the best approach to data governance is a just-in-time, customer service, help desk approach. Organizations need to focus on the current and most critical, and not the past. Critical reports are a good starting point for creating a bunch of other data-related content. Do not do report specifications on your 1000 reports. Focus on the new ones or the current ones that people have questions about. The energy and the resources are put on requests, not the past. Rather than spinning your energy to document all your reports before you roll data governance out, just document a couple of the critical reports. See this [blog post](https://blog.idatainc.com/resources-just-in-time-data-governance) for more information on this approach.

There is a great deal of data governance-related content: business glossary definitions. information about [data systems](https://blog.idatainc.com/data-system-inventory-resources), data models, information on reports and integrations, [reference data](https://blog.idatainc.com/reference-data-resources) (code values, lookup tables, valid values), [data quality](https://blog.idatainc.com/many-parts-data-quality) rules, and data-related polices and monitoring those policy attributes such as data access, privacy, security sharing, retention, and backups. There is a significant amount of content which requires a great deal of effort. That is why we feel the content creation loop is a great way to create usable data governance-related content. The idea is to put this data governance information in some organized way that is easily accessible, findable, and maintainable over time. And a tool like the [Data Cookbook](http://www.datacookbook.com) is a great help.

One of the most critical things you can do in a documented report is to associate the data getting presented on that report with business glossary terms. For example, in a report there are columns for student status and GPA. Are these defined in our [business glossary](https://blog.idatainc.com/business-glossary-resources)? If so, does that definition match what we are looking for?  If not available, you might then go create that glossary definition. In documenting a report then you might end up with creating 5 to 10 different glossary definitions.

Move forward. Documenting an old report is reverse engineering and will take longer than if done when the report was created. It is a much smaller effort to capture information as you build new content than when you go back in time. You do not want this information around your [report catalog](https://blog.idatainc.com/data-processing-catalog-resources) or glossary definitions to be just a [binder on a shelf](https://blog.idatainc.com/dg-binder-on-shelf) that nobody ever looks at. It doesn't add any value. You have wasted time. You want your data-related content to be used.

I am looking at this report and trying to understand if this report is useful. Is this a good report? How is a particular value calculated? Or what does this field mean? Data governance content could answer these questions. By having this information, you gain [trust](https://blog.idatainc.com/data-trust-resources) and knowledge in the data. And with this information you make better decisions.   That is the point of having this information so people can have more trust or have more knowledge or more reuse.

If data users are not engaging with the data-related content, they are not getting any value out of it. It is not about the content created. It is how many people are engaging and using the content. This is where we talk about this concept of [points of engagement](https://blog.idatainc.com/understanding-points-of-engagement), the searching and discovery for this and how that gets started. The points of engagement of searching and discovery can lead to requests. The assigned data steward creates content that needs to be reviewed. There is an ongoing assessment or approval or review of this content.

I am looking at a report/dashboard and I have a question on it. It would be nice if I could link over to information or connect to the information on the glossary terms. And can I make a request for information or curation right inside the report/dashboard that I am viewing. This is an as needed request that then can lead to a data steward defining a term or curating the report.

Often when you are talking about faculty information there are multiple stakeholders. You might have HR people who have a vested interest in how things are defined such as faculty load. And you also have financial people who are interested in that because it might impact grants and payments. And you also have student data involving faculty which means that the registrar is involved. You have a bunch of people that need to agree on what this definition means or have a slightly different context when we're using that definition. Often the content needs a review and goes to others to review and approve.

The assumption here is that your organization has limited resources and time to curate and create all of this content. We have never met an organization that has a bunch of subject matter experts (SME) sitting around with nothing to do.

How do you prioritize the effort and still be sure that you are supporting the necessary engagement? If someone has a question about a report, how do you make sure that they can get the answer they need without understanding that you have limited resources? This is where this [customer service/just in time/help desk approach](https://blog.idatainc.com/resources-just-in-time-data-governance) comes into play. You want to prioritize the content creation based on requests. Your goal is to provide data consumers with the information they need to understand the report or build the report. And this helps you to leverage expertise when you need it. Like an IT [Helpdesk](https://blog.idatainc.com/help-desk-approach-dg). If you have a question, then you look in the knowledge base. If the answer is found, you take care of the issue yourself. Self-service is good. If the answer is not found, you make a request, and the appropriate data steward is assigned to solve your issue. Hopefully the resolution will be put into the knowledge base for the next person that has that same issue.

In the content creation loop, people come in, search for discovery, and hopefully find what they are looking for, and they leave the loop. But what happens if they have questions or do not find what they need. They continue with the content creation loop.

You want to implement processes as opposed to waiting for data governance content perfection. Make it easy on your data users. Have them access the report specifications (purpose, description, owner, etc.) along with the business glossary right in the report. And have them make requests regarding that report right in the report. Maybe that [data request](https://blog.idatainc.com/resources-data-request-life-cycle) accesses your ticketing system that is already used in your organization. The request should be put into a workflow that sends the request to the appropriate [data steward](https://blog.idatainc.com/data-stewardship-resources) or, if none defined, a [support triage person](https://blog.idatainc.com/dg-triage).

Hope that this blog post was beneficial to you and your organization in creating your data governance related content.

IData has a solution, the [Data Cookbook](http://www.datacookbook.com/tour/), that can aid the employees and the organization in its [data governance and data intelligence](https://blog.idatainc.com/data-governance-component-resources) efforts including data requests. IData also has experts that can assist with data governance, [reporting](https://blog.idatainc.com/dg-reporting-analytics-resources), [integration](https://blog.idatainc.com/system-integration-resources), and other technology services on an as needed basis. Feel free to contact us and let us know how we can assist.

 [![Contact Us](https://no-cache.hubspot.com/cta/default/4171032/6765be6f-f024-407e-aadb-a1418a68ab0f.png)](https://cta-redirect.hubspot.com/cta/redirect/4171032/6765be6f-f024-407e-aadb-a1418a68ab0f)

(image credit ContentCreationLoop Diagram #1246)

![Jim Walery](https://app.hubspot.com/settings/avatar/e2a751ec95ddcd02d65a750bc8aea9dc)

##### About the Author

Jim Walery is a marketing professional who has been providing marketing services to technology companies for over 20 years and specifically those in higher education since 2010. Jim assists in getting the word out about the community via a variety of channels. Jim is knowledgeable in social media, blogging, collateral creation and website content. He is Inbound Marketing certified by HubSpot. Jim holds a B.A. from University of California, Irvine and a M.A. from Webster University. Jim can be reached at jwalery\[at\]idatainc.com.

### Subscribe to Email Updates

### Recent Posts

### Archives

- [February 2018 (13)](https://blog.idatainc.com/archive/2018/02)
- [May 2019 (6)](https://blog.idatainc.com/archive/2019/05)
- [January 2019 (5)](https://blog.idatainc.com/archive/2019/01)
- [February 2019 (5)](https://blog.idatainc.com/archive/2019/02)
- [October 2019 (5)](https://blog.idatainc.com/archive/2019/10)
- [March 2021 (5)](https://blog.idatainc.com/archive/2021/03)
- [June 2021 (5)](https://blog.idatainc.com/archive/2021/06)
- [July 2021 (5)](https://blog.idatainc.com/archive/2021/07)
- [September 2021 (5)](https://blog.idatainc.com/archive/2021/09)
- [March 2022 (5)](https://blog.idatainc.com/archive/2022/03)
- [October 2018 (4)](https://blog.idatainc.com/archive/2018/10)
- [March 2019 (4)](https://blog.idatainc.com/archive/2019/03)
- [June 2019 (4)](https://blog.idatainc.com/archive/2019/06)
- [July 2019 (4)](https://blog.idatainc.com/archive/2019/07)
- [December 2019 (4)](https://blog.idatainc.com/archive/2019/12)
- [April 2020 (4)](https://blog.idatainc.com/archive/2020/04)
- [May 2020 (4)](https://blog.idatainc.com/archive/2020/05)
- [June 2020 (4)](https://blog.idatainc.com/archive/2020/06)
- [August 2020 (4)](https://blog.idatainc.com/archive/2020/08)
- [January 2021 (4)](https://blog.idatainc.com/archive/2021/01)
- [April 2021 (4)](https://blog.idatainc.com/archive/2021/04)
- [May 2021 (4)](https://blog.idatainc.com/archive/2021/05)
- [August 2021 (4)](https://blog.idatainc.com/archive/2021/08)
- [January 2022 (4)](https://blog.idatainc.com/archive/2022/01)
- [June 2022 (4)](https://blog.idatainc.com/archive/2022/06)
- [July 2022 (4)](https://blog.idatainc.com/archive/2022/07)
- [August 2022 (4)](https://blog.idatainc.com/archive/2022/08)
- [November 2022 (4)](https://blog.idatainc.com/archive/2022/11)
- [February 2023 (4)](https://blog.idatainc.com/archive/2023/02)
- [September 2023 (4)](https://blog.idatainc.com/archive/2023/09)
- [May 2018 (3)](https://blog.idatainc.com/archive/2018/05)
- [November 2018 (3)](https://blog.idatainc.com/archive/2018/11)
- [April 2019 (3)](https://blog.idatainc.com/archive/2019/04)
- [August 2019 (3)](https://blog.idatainc.com/archive/2019/08)
- [September 2019 (3)](https://blog.idatainc.com/archive/2019/09)
- [November 2019 (3)](https://blog.idatainc.com/archive/2019/11)
- [January 2020 (3)](https://blog.idatainc.com/archive/2020/01)
- [February 2020 (3)](https://blog.idatainc.com/archive/2020/02)
- [March 2020 (3)](https://blog.idatainc.com/archive/2020/03)
- [July 2020 (3)](https://blog.idatainc.com/archive/2020/07)
- [September 2020 (3)](https://blog.idatainc.com/archive/2020/09)
- [October 2020 (3)](https://blog.idatainc.com/archive/2020/10)
- [November 2020 (3)](https://blog.idatainc.com/archive/2020/11)
- [December 2020 (3)](https://blog.idatainc.com/archive/2020/12)
- [February 2021 (3)](https://blog.idatainc.com/archive/2021/02)
- [October 2021 (3)](https://blog.idatainc.com/archive/2021/10)
- [November 2021 (3)](https://blog.idatainc.com/archive/2021/11)
- [December 2021 (3)](https://blog.idatainc.com/archive/2021/12)
- [February 2022 (3)](https://blog.idatainc.com/archive/2022/02)
- [May 2022 (3)](https://blog.idatainc.com/archive/2022/05)
- [October 2022 (3)](https://blog.idatainc.com/archive/2022/10)
- [January 2023 (3)](https://blog.idatainc.com/archive/2023/01)
- [January 2024 (3)](https://blog.idatainc.com/archive/2024/01)
- [June 2024 (3)](https://blog.idatainc.com/archive/2024/06)
- [August 2024 (3)](https://blog.idatainc.com/archive/2024/08)
- [September 2025 (3)](https://blog.idatainc.com/archive/2025/09)
- [December 2025 (3)](https://blog.idatainc.com/archive/2025/12)
- [March 2026 (3)](https://blog.idatainc.com/archive/2026/03)
- [April 2026 (3)](https://blog.idatainc.com/archive/2026/04)
- [May 2026 (3)](https://blog.idatainc.com/archive/2026/05)
- [June 2026 (3)](https://blog.idatainc.com/archive/2026/06)
- [July 2026 (3)](https://blog.idatainc.com/archive/2026/07)
- [August 2026 (3)](https://blog.idatainc.com/archive/2026/08)
- [December 2018 (2)](https://blog.idatainc.com/archive/2018/12)
- [April 2022 (2)](https://blog.idatainc.com/archive/2022/04)
- [September 2022 (2)](https://blog.idatainc.com/archive/2022/09)
- [December 2022 (2)](https://blog.idatainc.com/archive/2022/12)
- [March 2023 (2)](https://blog.idatainc.com/archive/2023/03)
- [April 2023 (2)](https://blog.idatainc.com/archive/2023/04)
- [May 2023 (2)](https://blog.idatainc.com/archive/2023/05)
- [June 2023 (2)](https://blog.idatainc.com/archive/2023/06)
- [July 2023 (2)](https://blog.idatainc.com/archive/2023/07)
- [August 2023 (2)](https://blog.idatainc.com/archive/2023/08)
- [October 2023 (2)](https://blog.idatainc.com/archive/2023/10)
- [November 2023 (2)](https://blog.idatainc.com/archive/2023/11)
- [February 2024 (2)](https://blog.idatainc.com/archive/2024/02)
- [March 2024 (2)](https://blog.idatainc.com/archive/2024/03)
- [April 2024 (2)](https://blog.idatainc.com/archive/2024/04)
- [July 2024 (2)](https://blog.idatainc.com/archive/2024/07)
- [September 2024 (2)](https://blog.idatainc.com/archive/2024/09)
- [November 2024 (2)](https://blog.idatainc.com/archive/2024/11)
- [December 2024 (2)](https://blog.idatainc.com/archive/2024/12)
- [January 2025 (2)](https://blog.idatainc.com/archive/2025/01)
- [February 2025 (2)](https://blog.idatainc.com/archive/2025/02)
- [March 2025 (2)](https://blog.idatainc.com/archive/2025/03)
- [April 2025 (2)](https://blog.idatainc.com/archive/2025/04)
- [May 2025 (2)](https://blog.idatainc.com/archive/2025/05)
- [June 2025 (2)](https://blog.idatainc.com/archive/2025/06)
- [July 2025 (2)](https://blog.idatainc.com/archive/2025/07)
- [August 2025 (2)](https://blog.idatainc.com/archive/2025/08)
- [January 2026 (2)](https://blog.idatainc.com/archive/2026/01)
- [February 2026 (2)](https://blog.idatainc.com/archive/2026/02)
- [June 2013 (1)](https://blog.idatainc.com/archive/2013/06)
- [July 2013 (1)](https://blog.idatainc.com/archive/2013/07)
- [March 2014 (1)](https://blog.idatainc.com/archive/2014/03)
- [May 2015 (1)](https://blog.idatainc.com/archive/2015/05)
- [July 2015 (1)](https://blog.idatainc.com/archive/2015/07)
- [August 2015 (1)](https://blog.idatainc.com/archive/2015/08)
- [January 2017 (1)](https://blog.idatainc.com/archive/2017/01)
- [March 2017 (1)](https://blog.idatainc.com/archive/2017/03)
- [May 2017 (1)](https://blog.idatainc.com/archive/2017/05)
- [June 2017 (1)](https://blog.idatainc.com/archive/2017/06)
- [August 2017 (1)](https://blog.idatainc.com/archive/2017/08)
- [November 2017 (1)](https://blog.idatainc.com/archive/2017/11)
- [December 2017 (1)](https://blog.idatainc.com/archive/2017/12)
- [January 2018 (1)](https://blog.idatainc.com/archive/2018/01)
- [June 2018 (1)](https://blog.idatainc.com/archive/2018/06)
- [July 2018 (1)](https://blog.idatainc.com/archive/2018/07)
- [August 2018 (1)](https://blog.idatainc.com/archive/2018/08)
- [September 2018 (1)](https://blog.idatainc.com/archive/2018/09)
- [December 2023 (1)](https://blog.idatainc.com/archive/2023/12)
- [May 2024 (1)](https://blog.idatainc.com/archive/2024/05)
- [October 2024 (1)](https://blog.idatainc.com/archive/2024/10)
- [October 2025 (1)](https://blog.idatainc.com/archive/2025/10)
- [November 2025 (1)](https://blog.idatainc.com/archive/2025/11)
- [September 2026 (1)](https://blog.idatainc.com/archive/2026/09)

### Categories

- [2019 (1)](https://blog.idatainc.com/tag/2019)
- [2020 (1)](https://blog.idatainc.com/tag/2020)
- [2024 (1)](https://blog.idatainc.com/tag/2024)
- [acceptance (1)](https://blog.idatainc.com/tag/acceptance)
- [access (3)](https://blog.idatainc.com/tag/access)
- [accountability (1)](https://blog.idatainc.com/tag/accountability)
- [action (3)](https://blog.idatainc.com/tag/action)
- [actions (3)](https://blog.idatainc.com/tag/actions)
- [Admissions (1)](https://blog.idatainc.com/tag/admissions)
- [adoption (6)](https://blog.idatainc.com/tag/adoption)
- [adult (1)](https://blog.idatainc.com/tag/adult)
- [advantages (1)](https://blog.idatainc.com/tag/advantages)
- [agile (1)](https://blog.idatainc.com/tag/agile)
- [agreements (1)](https://blog.idatainc.com/tag/agreements)
- [ai (12)](https://blog.idatainc.com/tag/ai)
- [analytics (22)](https://blog.idatainc.com/tag/analytics)
- [answers (2)](https://blog.idatainc.com/tag/answers)
- [approach (8)](https://blog.idatainc.com/tag/approach)
- [areas (1)](https://blog.idatainc.com/tag/areas)
- [artificial (17)](https://blog.idatainc.com/tag/artificial)
- [assessment (11)](https://blog.idatainc.com/tag/assessment)
- [assistance (1)](https://blog.idatainc.com/tag/assistance)
- [at-risk (1)](https://blog.idatainc.com/tag/at-risk)
- [avoid (2)](https://blog.idatainc.com/tag/avoid)
- [back (1)](https://blog.idatainc.com/tag/back)
- [barriers (2)](https://blog.idatainc.com/tag/barriers)
- [base (4)](https://blog.idatainc.com/tag/base)
- [begin (1)](https://blog.idatainc.com/tag/begin)
- [benefit (3)](https://blog.idatainc.com/tag/benefit)
- [benefits (7)](https://blog.idatainc.com/tag/benefits)
- [best (26)](https://blog.idatainc.com/tag/best)
- [BI (2)](https://blog.idatainc.com/tag/bi)
- [binder (2)](https://blog.idatainc.com/tag/binder)
- [blog (2)](https://blog.idatainc.com/tag/blog)
- [book (1)](https://blog.idatainc.com/tag/book)
- [brainstorming (1)](https://blog.idatainc.com/tag/brainstorming)
- [business (25)](https://blog.idatainc.com/tag/business)
- [buy (1)](https://blog.idatainc.com/tag/buy)
- [buyin (6)](https://blog.idatainc.com/tag/buyin)
- [capabilities (1)](https://blog.idatainc.com/tag/capabilities)
- [cases (1)](https://blog.idatainc.com/tag/cases)
- [catalog (12)](https://blog.idatainc.com/tag/catalog)
- [ccpa (1)](https://blog.idatainc.com/tag/ccpa)
- [CDO (3)](https://blog.idatainc.com/tag/cdo)
- [certification (2)](https://blog.idatainc.com/tag/certification)
- [challenges (5)](https://blog.idatainc.com/tag/challenges)
- [change (3)](https://blog.idatainc.com/tag/change)
- [checklist (1)](https://blog.idatainc.com/tag/checklist)
- [chief (3)](https://blog.idatainc.com/tag/chief)
- [citizen (1)](https://blog.idatainc.com/tag/citizen)
- [clean (1)](https://blog.idatainc.com/tag/clean)
- [cleanup (1)](https://blog.idatainc.com/tag/cleanup)
- [cloud (1)](https://blog.idatainc.com/tag/cloud)
- [collaboration (1)](https://blog.idatainc.com/tag/collaboration)
- [committee (13)](https://blog.idatainc.com/tag/committee)
- [communication (27)](https://blog.idatainc.com/tag/communication)
- [community (2)](https://blog.idatainc.com/tag/community)
- [complexity (1)](https://blog.idatainc.com/tag/complexity)
- [compliance (3)](https://blog.idatainc.com/tag/compliance)
- [components (3)](https://blog.idatainc.com/tag/components)
- [connectors (2)](https://blog.idatainc.com/tag/connectors)
- [consulting (1)](https://blog.idatainc.com/tag/consulting)
- [consumer (3)](https://blog.idatainc.com/tag/consumer)
- [content (43)](https://blog.idatainc.com/tag/content)
- [contents (4)](https://blog.idatainc.com/tag/contents)
- [continuous (1)](https://blog.idatainc.com/tag/continuous)
- [control (1)](https://blog.idatainc.com/tag/control)
- [controlling (1)](https://blog.idatainc.com/tag/controlling)
- [cookbook (32)](https://blog.idatainc.com/tag/cookbook)
- [corporation (1)](https://blog.idatainc.com/tag/corporation)
- [creation (7)](https://blog.idatainc.com/tag/creation)
- [CRM (4)](https://blog.idatainc.com/tag/crm)
- [cultural (1)](https://blog.idatainc.com/tag/cultural)
- [culture (12)](https://blog.idatainc.com/tag/culture)
- [curated (3)](https://blog.idatainc.com/tag/curated)
- [curating (3)](https://blog.idatainc.com/tag/curating)
- [custodian (1)](https://blog.idatainc.com/tag/custodian)
- [customer (3)](https://blog.idatainc.com/tag/customer)
- [cybersecurity (1)](https://blog.idatainc.com/tag/cybersecurity)
- [cycle (1)](https://blog.idatainc.com/tag/cycle)
- [dashboards (2)](https://blog.idatainc.com/tag/dashboards)
- [data (312)](https://blog.idatainc.com/tag/data)
- [Data Cookbook (185)](https://blog.idatainc.com/tag/data-cookbook)
- [databases (3)](https://blog.idatainc.com/tag/databases)
- [decision (2)](https://blog.idatainc.com/tag/decision)
- [definition (7)](https://blog.idatainc.com/tag/definition)
- [definitions (9)](https://blog.idatainc.com/tag/definitions)
- [deliverables (5)](https://blog.idatainc.com/tag/deliverables)
- [department (1)](https://blog.idatainc.com/tag/department)
- [description (1)](https://blog.idatainc.com/tag/description)
- [desk (3)](https://blog.idatainc.com/tag/desk)
- [dictionary (4)](https://blog.idatainc.com/tag/dictionary)
- [digital (1)](https://blog.idatainc.com/tag/digital)
- [dimensions (1)](https://blog.idatainc.com/tag/dimensions)
- [direction (1)](https://blog.idatainc.com/tag/direction)
- [discovery (1)](https://blog.idatainc.com/tag/discovery)
- [distribution (1)](https://blog.idatainc.com/tag/distribution)
- [dx (1)](https://blog.idatainc.com/tag/dx)
- [dynamic (1)](https://blog.idatainc.com/tag/dynamic)
- [ed (19)](https://blog.idatainc.com/tag/ed)
- [education (84)](https://blog.idatainc.com/tag/education)
- [educause (3)](https://blog.idatainc.com/tag/educause)
- [efficiencies (1)](https://blog.idatainc.com/tag/efficiencies)
- [efficiency (1)](https://blog.idatainc.com/tag/efficiency)
- [elemens (1)](https://blog.idatainc.com/tag/elemens)
- [elements (4)](https://blog.idatainc.com/tag/elements)
- [emergent (1)](https://blog.idatainc.com/tag/emergent)
- [employee (4)](https://blog.idatainc.com/tag/employee)
- [enablement (1)](https://blog.idatainc.com/tag/enablement)
- [enforcement (1)](https://blog.idatainc.com/tag/enforcement)
- [engagement (19)](https://blog.idatainc.com/tag/engagement)
- [entry (4)](https://blog.idatainc.com/tag/entry)
- [erp (5)](https://blog.idatainc.com/tag/erp)
- [ETL (2)](https://blog.idatainc.com/tag/etl)
- [examples (2)](https://blog.idatainc.com/tag/examples)
- [executive (1)](https://blog.idatainc.com/tag/executive)
- [expectations (1)](https://blog.idatainc.com/tag/expectations)
- [failure (1)](https://blog.idatainc.com/tag/failure)
- [features (1)](https://blog.idatainc.com/tag/features)
- [flow (4)](https://blog.idatainc.com/tag/flow)
- [football (1)](https://blog.idatainc.com/tag/football)
- [forum (1)](https://blog.idatainc.com/tag/forum)
- [framework (20)](https://blog.idatainc.com/tag/framework)
- [friction (1)](https://blog.idatainc.com/tag/friction)
- [front (1)](https://blog.idatainc.com/tag/front)
- [functional (4)](https://blog.idatainc.com/tag/functional)
- [gaps (1)](https://blog.idatainc.com/tag/gaps)
- [gatekeeper (1)](https://blog.idatainc.com/tag/gatekeeper)
- [GDPR (2)](https://blog.idatainc.com/tag/gdpr)
- [getting (2)](https://blog.idatainc.com/tag/getting)
- [glossary (27)](https://blog.idatainc.com/tag/glossary)
- [governance (297)](https://blog.idatainc.com/tag/governance)
- [government (1)](https://blog.idatainc.com/tag/government)
- [guidance (1)](https://blog.idatainc.com/tag/guidance)
- [HE (42)](https://blog.idatainc.com/tag/he)
- [health (2)](https://blog.idatainc.com/tag/health)
- [healthcare (1)](https://blog.idatainc.com/tag/healthcare)
- [HEDW (1)](https://blog.idatainc.com/tag/hedw)
- [help (3)](https://blog.idatainc.com/tag/help)
- [helping (3)](https://blog.idatainc.com/tag/helping)
- [higher (86)](https://blog.idatainc.com/tag/higher)
- [hiring (1)](https://blog.idatainc.com/tag/hiring)
- [how (3)](https://blog.idatainc.com/tag/how)
- [idata (143)](https://blog.idatainc.com/tag/idata)
- [idatahub (1)](https://blog.idatainc.com/tag/idatahub)
- [implementation (3)](https://blog.idatainc.com/tag/implementation)
- [import (1)](https://blog.idatainc.com/tag/import)
- [importance (4)](https://blog.idatainc.com/tag/importance)
- [improve (1)](https://blog.idatainc.com/tag/improve)
- [improvement (1)](https://blog.idatainc.com/tag/improvement)
- [in (2)](https://blog.idatainc.com/tag/in)
- [included (1)](https://blog.idatainc.com/tag/included)
- [inexpensive (1)](https://blog.idatainc.com/tag/inexpensive)
- [information (5)](https://blog.idatainc.com/tag/information)
- [initiative (3)](https://blog.idatainc.com/tag/initiative)
- [institutional (2)](https://blog.idatainc.com/tag/institutional)
- [integration (22)](https://blog.idatainc.com/tag/integration)
- [intelligence (280)](https://blog.idatainc.com/tag/intelligence)
- [intervention (1)](https://blog.idatainc.com/tag/intervention)
- [inventory (22)](https://blog.idatainc.com/tag/inventory)
- [investment (2)](https://blog.idatainc.com/tag/investment)
- [ipeds (1)](https://blog.idatainc.com/tag/ipeds)
- [ir (1)](https://blog.idatainc.com/tag/ir)
- [issues (3)](https://blog.idatainc.com/tag/issues)
- [it (1)](https://blog.idatainc.com/tag/it)
- [items (2)](https://blog.idatainc.com/tag/items)
- [iteration (2)](https://blog.idatainc.com/tag/iteration)
- [JIT (8)](https://blog.idatainc.com/tag/jit)
- [journey (3)](https://blog.idatainc.com/tag/journey)
- [just (9)](https://blog.idatainc.com/tag/just)
- [K-12 (1)](https://blog.idatainc.com/tag/k-12)
- [key (3)](https://blog.idatainc.com/tag/key)
- [know (1)](https://blog.idatainc.com/tag/know)
- [Knowledge (20)](https://blog.idatainc.com/tag/knowledge)
- [knowledgebase (25)](https://blog.idatainc.com/tag/knowledgebase)
- [language (1)](https://blog.idatainc.com/tag/language)
- [leadership (1)](https://blog.idatainc.com/tag/leadership)
- [learning (3)](https://blog.idatainc.com/tag/learning)
- [lessons (2)](https://blog.idatainc.com/tag/lessons)
- [level (1)](https://blog.idatainc.com/tag/level)
- [levels (1)](https://blog.idatainc.com/tag/levels)
- [libary (1)](https://blog.idatainc.com/tag/libary)
- [librarian (1)](https://blog.idatainc.com/tag/librarian)
- [library (1)](https://blog.idatainc.com/tag/library)
- [life (1)](https://blog.idatainc.com/tag/life)
- [lifecycle (3)](https://blog.idatainc.com/tag/lifecycle)
- [lineage (6)](https://blog.idatainc.com/tag/lineage)
- [lists (5)](https://blog.idatainc.com/tag/lists)
- [literacy (10)](https://blog.idatainc.com/tag/literacy)
- [loop (1)](https://blog.idatainc.com/tag/loop)
- [maintain (1)](https://blog.idatainc.com/tag/maintain)
- [maintenance (2)](https://blog.idatainc.com/tag/maintenance)
- [management (32)](https://blog.idatainc.com/tag/management)
- [manufacturing (1)](https://blog.idatainc.com/tag/manufacturing)
- [map (3)](https://blog.idatainc.com/tag/map)
- [market (1)](https://blog.idatainc.com/tag/market)
- [matrix (3)](https://blog.idatainc.com/tag/matrix)
- [measurement (3)](https://blog.idatainc.com/tag/measurement)
- [metadata (3)](https://blog.idatainc.com/tag/metadata)
- [method (1)](https://blog.idatainc.com/tag/method)
- [migrating (3)](https://blog.idatainc.com/tag/migrating)
- [migration (1)](https://blog.idatainc.com/tag/migration)
- [model (1)](https://blog.idatainc.com/tag/model)
- [monkey (1)](https://blog.idatainc.com/tag/monkey)
- [new (1)](https://blog.idatainc.com/tag/new)
- [non-profit (1)](https://blog.idatainc.com/tag/non-profit)
- [not (1)](https://blog.idatainc.com/tag/not)
- [office (1)](https://blog.idatainc.com/tag/office)
- [officer (3)](https://blog.idatainc.com/tag/officer)
- [onboarding (3)](https://blog.idatainc.com/tag/onboarding)
- [operations (2)](https://blog.idatainc.com/tag/operations)
- [organization (2)](https://blog.idatainc.com/tag/organization)
- [organizational (1)](https://blog.idatainc.com/tag/organizational)
- [organizations (1)](https://blog.idatainc.com/tag/organizations)
- [out (1)](https://blog.idatainc.com/tag/out)
- [oversight (8)](https://blog.idatainc.com/tag/oversight)
- [own (1)](https://blog.idatainc.com/tag/own)
- [owner (1)](https://blog.idatainc.com/tag/owner)
- [ownership (3)](https://blog.idatainc.com/tag/ownership)
- [parts (1)](https://blog.idatainc.com/tag/parts)
- [path (2)](https://blog.idatainc.com/tag/path)
- [people (36)](https://blog.idatainc.com/tag/people)
- [plan (3)](https://blog.idatainc.com/tag/plan)
- [planning (2)](https://blog.idatainc.com/tag/planning)
- [platform (1)](https://blog.idatainc.com/tag/platform)
- [playbook (1)](https://blog.idatainc.com/tag/playbook)
- [points (8)](https://blog.idatainc.com/tag/points)
- [policies (15)](https://blog.idatainc.com/tag/policies)
- [policy (2)](https://blog.idatainc.com/tag/policy)
- [portal (2)](https://blog.idatainc.com/tag/portal)
- [potential (1)](https://blog.idatainc.com/tag/potential)
- [practices (20)](https://blog.idatainc.com/tag/practices)
- [pragmatic (3)](https://blog.idatainc.com/tag/pragmatic)
- [principles (2)](https://blog.idatainc.com/tag/principles)
- [priorities (3)](https://blog.idatainc.com/tag/priorities)
- [priorization (2)](https://blog.idatainc.com/tag/priorization)
- [privacy (2)](https://blog.idatainc.com/tag/privacy)
- [problem (2)](https://blog.idatainc.com/tag/problem)
- [process (35)](https://blog.idatainc.com/tag/process)
- [processes (2)](https://blog.idatainc.com/tag/processes)
- [processing (7)](https://blog.idatainc.com/tag/processing)
- [products (2)](https://blog.idatainc.com/tag/products)
- [project (11)](https://blog.idatainc.com/tag/project)
- [projects (3)](https://blog.idatainc.com/tag/projects)
- [protection (2)](https://blog.idatainc.com/tag/protection)
- [purpose (1)](https://blog.idatainc.com/tag/purpose)
- [quality (38)](https://blog.idatainc.com/tag/quality)
- [questions (5)](https://blog.idatainc.com/tag/questions)
- [quick (1)](https://blog.idatainc.com/tag/quick)
- [quotes (1)](https://blog.idatainc.com/tag/quotes)
- [reasons (1)](https://blog.idatainc.com/tag/reasons)
- [recap (1)](https://blog.idatainc.com/tag/recap)
- [reference (17)](https://blog.idatainc.com/tag/reference)
- [regulation (1)](https://blog.idatainc.com/tag/regulation)
- [related (8)](https://blog.idatainc.com/tag/related)
- [report (12)](https://blog.idatainc.com/tag/report)
- [reporting (19)](https://blog.idatainc.com/tag/reporting)
- [repository (1)](https://blog.idatainc.com/tag/repository)
- [request (25)](https://blog.idatainc.com/tag/request)
- [research (3)](https://blog.idatainc.com/tag/research)
- [resiliency (1)](https://blog.idatainc.com/tag/resiliency)
- [resolution (2)](https://blog.idatainc.com/tag/resolution)
- [resources (33)](https://blog.idatainc.com/tag/resources)
- [responsibilities (3)](https://blog.idatainc.com/tag/responsibilities)
- [return (2)](https://blog.idatainc.com/tag/return)
- [review (1)](https://blog.idatainc.com/tag/review)
- [road (3)](https://blog.idatainc.com/tag/road)
- [roadmap (16)](https://blog.idatainc.com/tag/roadmap)
- [ROI (7)](https://blog.idatainc.com/tag/roi)
- [roles (3)](https://blog.idatainc.com/tag/roles)
- [SaaS (3)](https://blog.idatainc.com/tag/saas)
- [savings (1)](https://blog.idatainc.com/tag/savings)
- [schedule (1)](https://blog.idatainc.com/tag/schedule)
- [science (1)](https://blog.idatainc.com/tag/science)
- [scientist (1)](https://blog.idatainc.com/tag/scientist)
- [score (2)](https://blog.idatainc.com/tag/score)
- [security (4)](https://blog.idatainc.com/tag/security)
- [self-service (2)](https://blog.idatainc.com/tag/self-service)
- [sensitive (1)](https://blog.idatainc.com/tag/sensitive)
- [service (7)](https://blog.idatainc.com/tag/service)
- [services (1)](https://blog.idatainc.com/tag/services)
- [session (1)](https://blog.idatainc.com/tag/session)
- [shadow (7)](https://blog.idatainc.com/tag/shadow)
- [sharing (2)](https://blog.idatainc.com/tag/sharing)
- [shelf (1)](https://blog.idatainc.com/tag/shelf)
- [silo (3)](https://blog.idatainc.com/tag/silo)
- [single (1)](https://blog.idatainc.com/tag/single)
- [SIS (1)](https://blog.idatainc.com/tag/sis)
- [situations (1)](https://blog.idatainc.com/tag/situations)
- [skills (3)](https://blog.idatainc.com/tag/skills)
- [smarter (1)](https://blog.idatainc.com/tag/smarter)
- [soft (2)](https://blog.idatainc.com/tag/soft)
- [software (1)](https://blog.idatainc.com/tag/software)
- [solis (1)](https://blog.idatainc.com/tag/solis)
- [solution (3)](https://blog.idatainc.com/tag/solution)
- [source (1)](https://blog.idatainc.com/tag/source)
- [specification (4)](https://blog.idatainc.com/tag/specification)
- [specifications (2)](https://blog.idatainc.com/tag/specifications)
- [spotlight (1)](https://blog.idatainc.com/tag/spotlight)
- [sprawl (3)](https://blog.idatainc.com/tag/sprawl)
- [staff (3)](https://blog.idatainc.com/tag/staff)
- [stakeholders (2)](https://blog.idatainc.com/tag/stakeholders)
- [start (10)](https://blog.idatainc.com/tag/start)
- [started (4)](https://blog.idatainc.com/tag/started)
- [steward (34)](https://blog.idatainc.com/tag/steward)
- [stewardship (47)](https://blog.idatainc.com/tag/stewardship)
- [story (2)](https://blog.idatainc.com/tag/story)
- [strategy (2)](https://blog.idatainc.com/tag/strategy)
- [student (2)](https://blog.idatainc.com/tag/student)
- [students (1)](https://blog.idatainc.com/tag/students)
- [success (8)](https://blog.idatainc.com/tag/success)
- [summary (1)](https://blog.idatainc.com/tag/summary)
- [support (3)](https://blog.idatainc.com/tag/support)
- [supporting (1)](https://blog.idatainc.com/tag/supporting)
- [survey (4)](https://blog.idatainc.com/tag/survey)
- [system (23)](https://blog.idatainc.com/tag/system)
- [systems (5)](https://blog.idatainc.com/tag/systems)
- [tacit (1)](https://blog.idatainc.com/tag/tacit)
- [team (2)](https://blog.idatainc.com/tag/team)
- [technical (4)](https://blog.idatainc.com/tag/technical)
- [technology (21)](https://blog.idatainc.com/tag/technology)
- [telling (1)](https://blog.idatainc.com/tag/telling)
- [thoughts (3)](https://blog.idatainc.com/tag/thoughts)
- [ticket (3)](https://blog.idatainc.com/tag/ticket)
- [time (7)](https://blog.idatainc.com/tag/time)
- [tool (5)](https://blog.idatainc.com/tag/tool)
- [tools (5)](https://blog.idatainc.com/tag/tools)
- [top (2)](https://blog.idatainc.com/tag/top)
- [topics (2)](https://blog.idatainc.com/tag/topics)
- [training (25)](https://blog.idatainc.com/tag/training)
- [traits (1)](https://blog.idatainc.com/tag/traits)
- [transformation (1)](https://blog.idatainc.com/tag/transformation)
- [transition (1)](https://blog.idatainc.com/tag/transition)
- [trend (1)](https://blog.idatainc.com/tag/trend)
- [triage (1)](https://blog.idatainc.com/tag/triage)
- [trust (17)](https://blog.idatainc.com/tag/trust)
- [trusted (2)](https://blog.idatainc.com/tag/trusted)
- [truth (1)](https://blog.idatainc.com/tag/truth)
- [types (1)](https://blog.idatainc.com/tag/types)
- [urban (1)](https://blog.idatainc.com/tag/urban)
- [use (1)](https://blog.idatainc.com/tag/use)
- [used (1)](https://blog.idatainc.com/tag/used)
- [uses (1)](https://blog.idatainc.com/tag/uses)
- [valid (6)](https://blog.idatainc.com/tag/valid)
- [value (7)](https://blog.idatainc.com/tag/value)
- [versioning (1)](https://blog.idatainc.com/tag/versioning)
- [vertical (1)](https://blog.idatainc.com/tag/vertical)
- [visualization (1)](https://blog.idatainc.com/tag/visualization)
- [warehouse (5)](https://blog.idatainc.com/tag/warehouse)
- [warehousing (1)](https://blog.idatainc.com/tag/warehousing)
- [way (1)](https://blog.idatainc.com/tag/way)
- [webinar (1)](https://blog.idatainc.com/tag/webinar)
- [what (5)](https://blog.idatainc.com/tag/what)
- [where (1)](https://blog.idatainc.com/tag/where)
- [who (2)](https://blog.idatainc.com/tag/who)
- [why (7)](https://blog.idatainc.com/tag/why)
- [wins (1)](https://blog.idatainc.com/tag/wins)
- [workflow (1)](https://blog.idatainc.com/tag/workflow)
- [writing (1)](https://blog.idatainc.com/tag/writing)

### Address

1727 King Street, Suite 250  
Alexandria, VA 22314 USA

- <https://www.linkedin.com/company/idata-incorporated>

- [Jobs](http://www.idatainc.com/about-us/jobs/)
- [Contact Us](http://www.idatainc.com/about-us/contact-us/)

Copyright © 2026 [IData Incorporated](http://idatainc.com). All rights reserved