Slate Success Starts with Governance

Most institutions think the hardest part of a Slate project is implementation. It isn’t. 

The hardest part is deciding what you’re actually willing to change before anything is built. That work starts in discovery, the point where institutions are forced to confront how decisions are made, who owns outcomes, and whether alignment is real or just polite agreement in meetings. When those questions get rushed or avoided, they don’t disappear. They surface later as exceptions, rework, and frustration once the system is live. 

By the time Slate launches, most outcomes are already set. Teams either established clear ownership and decision-making early, or they deferred those conversations and called the deferral “flexibility.” 

Teams leave this phase believing they’re aligned, only to realize six weeks after go-live that no one actually agreed on who owns reporting, portals, or automation decisions. 

Why institutions confuse activity with agility

Agility gets misunderstood. It’s not building faster, responding to every request, or saying “yes” more often. Real agility is the ability to make decisions repeatedly without reopening the same conversations every time. That only works when governance is clear. 

When governance is weak, institutions compensate with over-customization. Instead of making decisions, they build around every exception. The result is a Slate environment that’s fragile, slower to evolve, and harder to sustain. 

Slate’s flexibility tends to amplify whatever governance model already exists, including the weak ones. It’ll support almost any direction an institution chooses, including the ones that make long-term progress harder. 

What effective governance enables 

The start of good governance comes from understanding what it is. Data and system governance is a set of decision rights establishing who controls what aspects of the system. Schools need to build an accountability framework to encourage desirable behavior in the valuation, creation, storage, use, archiving, and deletion of data and information. It includes the processes, roles, standards, and metrics that ensure the effective and efficient use of data and information in enabling an organization to achieve its goals.  

Healthy Slate environments tend to share a few traits: ownership is explicit, decision rights are clear, and not every choice requires consensus. New requests are evaluated consistently, not just based on what Slate can do, but on whether the request aligns with long-term priorities and what tradeoffs it introduces. 

Teams are comfortable saying no or “not yet.” Decisions are documented so they don’t need to be relitigated every few months. Past decisions are revisited intentionally, not reactively. Change happens because conditions shift, not because pressure builds.   

This kind of structure doesn’t limit agility. It makes it possible. 

The shift institutions need to make 

The goal isn’t to “finish” Slate, but to build an operating model that can evolve with it. 

Institutions that treat Slate as a project eventually hit a ceiling. Institutions that view governance as an ongoing discipline reap value long after implementation, because they invested early in clarity, ownership, and decision-making. 

That work starts in discovery. It shows itself at go-live. And it defines everything that comes after.