Agile that works inside shared governance

A university does not have a CEO who can sign off on a new way of working. It has a faculty senate, a dozen administrative units, and IT shops that answer to deans, not to a CIO. Change happens by consent, which is slower to start and far harder to undo.

Bring a corporate agile playbook to a campus and watch it stall in the first month. There is no executive who can mandate the change, no single IT organization to standardize, and a culture that treats consensus and faculty autonomy as principles worth defending rather than obstacles to clear. The reflexive read is that higher education is simply too slow for agile work. I think that read is wrong, and a little arrogant. Campuses change through a different mechanism than companies do, and the rollouts that fail are usually the ones that never learned what the mechanism is.

The mechanism is consent, and consent is earned through evidence. A dean, a department chair, and a governance committee are all being asked the same thing: approve a change whose consequences land on the people they are responsible to. When they hesitate, they are doing their job. The mistake practitioners make is to treat that hesitation as resistance and look for a way around it. There is no way around it, and there should not be. There is only a way through it, which is to give the people with a vote something real to look at.

The bottleneck is usually what nobody can see

Shared governance takes the blame for slow change on campus, and it rarely deserves it. Committees are not the problem. The problem is that people are routinely asked to approve work they cannot see clearly: an initiative summarized in a memo, progress relayed secondhand, dependencies that were never written down. Faced with a fuzzy picture and real accountability, a reasonable person defaults to caution. Faced with thin information, that caution is exactly what good stewardship looks like.

So the question I care about on a campus is not how to move governance faster. It is how to make the work legible enough that the governance has something concrete to weigh. When a committee can see what is happening, what it depends on, and what it will cost, the deliberation that felt like molasses tends to find its footing, because now there is a specific thing to say yes to, amend, or decline. The committee was never slow, only starved of detail.

A campus does not resist the change it can see clearly. It resists the change it is asked to approve on faith, and it is right to.

Make the work visible to everyone who has a vote

This is the work that agile delivery does well on a campus, and it is the opposite of mandate. Configured for a decentralized institution, Jira and Confluence give every stakeholder, IT, administrative units, faculty committees, and leadership, the same view of where things actually stand. Coaching changes how a team works. The platform makes that change visible to the people whose consent it depends on, which on a campus is most people. Visibility is also why agile fits higher education better than the corporate stereotype suggests: transparent, incremental work produces exactly the evidence shared governance is built to act on. You ship something small, it is visible, the next decision is made on what happened rather than on what was promised.

I have watched this play out where the constraints were as serious as they come. At a top US law school, technology ran as a centralized service that could not keep up, and the path forward was a distributed, self-service model the school had to be brought along to support, unit by unit. The shift cut roughly $900,000 a year, but the durable part was the operating model, owned by the people who used it rather than imposed on them. You can read how that came together. None of it would have held if it had arrived as a directive from above. It held because each step was visible, each decision had its evidence, and the consent was real.

Student data raises the bar, as it should

AI can take real weight off IT and student services, and surface answers buried in the documentation sprawl every institution accumulates. Near student records, it inherits an obligation that predates it. Family Educational Rights and Privacy Act (FERPA) protected data calls for deliberate access controls, clear boundaries on what a model can see, and a person in the loop wherever a record is in play. That is not a campus exception. It is the same discipline we apply anywhere the stakes are high, here with student trust on the line, which an institution does not extend cheaply and should not be asked to.

Meet the campus where it actually decides, by consent and on evidence, and the change that was supposed to be impossible turns out to be a matter of patience and visibility. You are not overriding shared governance. You are giving it what it needed to say yes.

If you want to make your delivery legible enough for governance to move on it, see where delivery is getting stuck.