Minimizing Data Governance Fatigue to Maximize Value

April Blackburn: You really cannot talk about modern transportation without talking about data. It touches everything. Data governance sets out the conditions for effective decision-making based on trustworthy information; it is the framework of policies, roles, and processes that defines how data is owned, managed, and used across an organization. Simply put, data governance is about making sure data actually works for you rather than against you.

A formalized data governance framework, as opposed to case-by-case practices, builds trust and helps the organization stay resilient as circumstances change. It also enables people to carry out mission-critical functions. Performance management, federal reporting, and predictive maintenance, for example, can only work well when the underlying data is consistent and trusted. Strong governance turns individual wins into repeatable, scalable practices.

Data affects operations, asset management, planning, finance—every part of an organization. When taking an enterprise view of data and governance, you are really asking how to manage this foundational asset so people throughout the organization can rely on it.

April Blackburn: One of the biggest barriers is data fatigue. Departments of Transportation (DOTs) and other organizations have long struggled to implement effective data governance, despite ongoing efforts. So, they are now asking fair questions: Haven’t we already done this work? Why do we have to do more? Likely, in such cases, the work was limited or uneven, with governance addressing a system, a project, or a reporting need but not extending across the organization. When that happens, reporting becomes inconsistent, confidence in the data drops, and trust erodes. This situation leads to another barrier: silos.

We have found that silos—driven by legacy technology, organizational structures predating an enterprise-wide data strategy, high integration costs, and unclear data ownership—often foster territorial behavior that impedes cross-functional data governance. Data managed strictly by departments or trapped in older systems becomes fragmented and hard to use consistently. DOTs make more progress when they focus on high-value, mission-critical data and organize governance around data domains, such as assets or finance, instead of organizational charts.

Another challenge is that people often resist governance because they perceive it as an IT-driven compliance task rather than recognizing it as a foundational business capability across the organization; they also see governance as extra work on top of their regular responsibilities. However, when experience shows that well-designed governance reduces rework, improves data quality, and makes their jobs easier, excitement builds. Small wins create momentum because the value is visible.

In reality, governance matters because it supports what leaders already care about—funding, safety, performance, and defensible decisions. When that connection is clear, governance feels practical, not theoretical.

When governance is done well, the framework acts like guardrails, rather than an unnecessary constraint, allowing people to move forward with clarity to deliver value efficiently and confidently. When data falls outside the guardrails, organizations lose time reworking and taking corrective measures, which can cause frustration and slow progress.

Overcoming these barriers takes a practical, phased approach that meets DOTs and other organizations where they are. Governance works best when it starts with clear priorities, grows over time, and becomes part of how people already work. That approach builds trust, supports mission-critical functions, and helps all organizations move forward.

April Blackburn: Yes, a common misconception is that IT owns data governance. Data governance does not belong to just one group. While IT enables data governance, the capability goes well beyond IT; and while compliance is a critical component of data governance, it represents only one dimension of its value.

Data governance works best as a shared enterprise responsibility. IT is often where data governance starts because IT teams know how to build solutions and support them across the organization. But governance only sticks when the business is actively involved.

When governance is fragmented or informal, organizations feel the effects quickly through inconsistencies in reporting, confusion around ownership, and a lack of confidence in performance measures. That makes it harder to make decisions and harder to defend them.

Because data supports so many business areas, it is important for governance to reflect that reality. Clear roles and shared accountability help people trust the data and rely on it, even as leadership or priorities change.

In general, organizations have to think beyond their own walls. In the case of DOTs, much of the data comes from consultants, metropolitan planning organizations, local agencies, sensors, and private providers. Governance should extend into that ecosystem. Expectations around quality, standards, and ownership need to be clear upfront, not figured out later.

When a well-designed structure is in place, governance stops feeling like overhead. It becomes an embedded practice, driving better outcomes and preparing organizations to adopt technologies responsibly.

April Blackburn: If we are serious about modern transportation, we have to be serious about our data. Technology will only become more integral to everything we do. That means the foundation has to be solid.

There are five elements we consider when building a strong data governance foundation:

Ownership and Accountability

Every major data domain needs a clearly defined owner and steward. Governance does not work without accountability. When ownership is unclear, issues sit unresolved and trust declines. When it is clear, decisions get made and standards hold.

Policies and Standards

Organizations need consistent definitions and agreed-upon rules for how data is created, used, and shared. These should support how the agency actually operates. Consistency is what allows leaders to rely on reports across divisions without second-guessing the results.

Data Quality and Security

Data must be accurate, complete, and protected. Quality cannot be assumed. It has to be monitored and reinforced. When leaders connect data quality to funding decisions, safety outcomes, and performance measures, governance becomes part of the business conversation, rather than an IT task.

Lifecycle and Traceability

Data does not just appear in a dashboard. It originates somewhere; it moves; it is transformed; and it is reported. People must be able to trace that path. They need to see where a number came from and reproduce it using the same data and logic. If results cannot be recreated, confidence drops quickly. Leaders cannot make sound decisions if they doubt the numbers.

Culture and Leadership

Governance is sustained by culture. Tools and policies matter, but leadership behavior matters more. Leaders set expectations by asking thoughtful questions about the data behind the information they receive. They remove organizational barriers and reinforce that stewardship is part of each role. When governance is reflected in performance discussions and leadership KPIs, it becomes embedded in how the organization operates.