Renée Alvarez — Data Governance Coordinator

When you tell people you coordinate data governance, do they know what you mean?

Usually? No. I mean, people are polite, so they nod, but I can tell they are thinking either cybersecurity or another committee that is going to send them a policy to read. And honestly, when I started, I probably would have given you a definition that was technically correct and completely useless.

I guess what I would say now is that data governance is how we decide who is responsible for information, what our terms mean, who should have access, and what happens when something is wrong. My job is to help the district make those decisions on purpose instead of letting software settings or historical habits make them for us. It is less glamorous than the phrase sounds. Some days it is two departments agreeing on what “active student” means. But that agreement can fix ten reports and three integrations, so it matters.

What did the governance program look like when you arrived?

There was a council on paper. It had a membership list, a charter, and meeting minutes from about a year earlier. So, you know, all the artifacts of governance without much governing happening. The meetings had become presentations from IT. People would listen, maybe ask a question, and then go back to their departments. Nobody was making cross-functional decisions.

That was not because people did not care. They were busy, and the agenda was too broad. We would say “student data quality” as if that were one solvable item. I learned pretty quickly that if governance feels like an additional layer of work, it will always lose to the emergency already sitting on someone’s desk.

So how did you get the council moving again?

We stopped trying to govern everything. That was our first real win. We picked student withdrawal dates because the issue was concrete and everybody felt the consequences. Attendance, enrollment, CALPADS, special programs, and school sites were all using the field, but not always in the same way. A date that looked like a small clerical detail could affect reporting, access, funding, and whether a student still appeared on a teacher’s roster.

We mapped who entered it, which rules applied, where it traveled, and who could correct it. Then the council made three actual decisions: one definition, one source, and one escalation path. I remember somebody saying, “Oh, this is what governance is.” That was the moment. We fixed a recurring problem, but more importantly, people saw that the council could remove work rather than create it.

What technology helps you do this work?

A metadata catalog helps, although I should say ours is not some magical enterprise platform. We started with a structured inventory and a ticket workflow. The value was being able to connect a data element to an owner, a definition, the systems using it, and open issues. Before that, the knowledge lived in people’s heads or in an old email somebody hoped they could find.

We also use data-quality monitoring, access-review reports, and lineage diagrams. But I am careful about buying a governance tool before the district has governance habits. A tool can show that an owner field is blank. It cannot make a director accept ownership. That part still requires a conversation, sometimes several conversations.

You mentioned access reviews. Was that another area where you had a win?

Yes, and this one was a little uncomfortable. We found that some staff retained access after changing positions because each application had its own process. Nobody had intentionally granted inappropriate access; the district simply did not have one reliable role-change signal. The first report was, frankly, messy. People got defensive because it looked like we were auditing their judgment.

We changed the approach. Instead of sending a giant exception list, we worked with HR, identity management, and three system owners to define what should happen when a person transfers. We piloted a monthly review and gave managers a simple way to confirm or remove access. Within a semester, the oldest exceptions were gone and new ones were being caught much earlier. I guess the win was not just cleaner access. We moved from blame to a repeatable control that people understood.

What is the hardest part of the role?

Getting decision authority to match responsibility. A data steward may understand the issue better than anyone, but they may not have the authority to tell two departments to change. On the other hand, an executive can make the decision but may not see the operational consequences. I spend a lot of time getting the right people into the same conversation and being very explicit about who is recommending and who is deciding.

And, I mean, governance exposes old tensions. If two reports have disagreed for five years, there may be a reason nobody wanted to settle the definition. You have to be patient without letting patience become avoidance.

Has coordinating governance changed how you think about leadership?

Definitely. I used to think leadership meant having a clear answer and getting people aligned around it. Now I think a lot of leadership is designing a fair way to reach the answer and making the responsibility visible afterward. I do not need to be the expert in attendance, special education, finance, or assessment. I need to make it possible for those experts to solve a shared problem without one perspective quietly dominating.

I have also learned that language matters. If I say “compliance,” one group hears risk and another hears paperwork. If I say, “A counselor is seeing the wrong students because this role was never updated,” the purpose becomes real.

What would you tell a district that wants to begin data governance?

Pick one problem that crosses departments and causes visible pain. Do not begin with a fifty-page framework. Name the people who create, correct, approve, use, and protect that information. Give them a decision small enough to finish. Then document what they decided and show where the work improved.

I mean, you will need the charter eventually. You will need policies and standards. But people believe in governance after they experience a problem becoming clearer, not after they see a diagram with a lot of boxes.

Reflective questions

1. What recurring district problem could serve as a practical first governance use case?
2. Where does responsibility for data exist without matching decision authority?
3. How can a governance council demonstrate that it removes work rather than adds it?
4. Which role changes or transfers create access risk in your district?
5. What knowledge currently exists only in the memory or email of individual employees?
6. How should technical experts, data stewards, and executive decision-makers share responsibility?