We Followed the Governance Process Perfectly. It Still Blew Up

The feature worked. That was the problem.

We had shipped something to our university's mobile app that genuinely helped students: a home screen that pulled every student's upcoming assignments straight from the LMS. Open the app, and there it was — everything due, across all your courses, in one place. The early signal was exactly what you hope for: students took to it right away.

If you have ever shipped anything to real users, you know that feeling. The metric moves the right direction in the first week. People use the thing without being told to. You let yourself believe the hard part is behind you.

The hard part had not started.

The revolt arrived because it worked

The pushback did not come from students. It came from faculty. And the part worth sitting with, because it's easy to skip past: the objection wasn't that the feature hurt students.

The objection was that it helped students by changing how faculty delivered their own material. Plenty of instructors publish the full course up front and then use release dates and module sequencing to control when students actually engage with each piece. Our home screen ignored all of that pacing — it pulled the raw due dates and flattened the whole semester into one day-one list. When faculty described how that felt, one word kept coming back: violated. Not inconvenienced — violated.

Read that again, because the reflex is to file it under "faculty resist change." It is not that. The control they lost was real and specific: when their students saw what was coming. They don't want all fourteen weeks of deadlines staring a student down before the course has found its footing — and the LMS gave them tools to prevent exactly that. Our app routed around those tools and made the full list a feature. The thing that helped students removed something faculty had been quietly relying on.

Not every objection was high-minded — a revolt is always a coalition, and some people were just annoyed. But enough of them were high-minded that I stopped filing the whole thing under "resistance."

That is signal.

When a feature helps one group by removing another group's sense of control, the backlash is information, not noise. The people pushing back are telling you the price of the win. And the win was real — which is exactly why I won't tell you we shouldn't have done it.

"But we did it right"

Here is where I lose the people who already know the moral of this story. Because they think they know it: you should have involved faculty earlier.

We did.

We took the feature through shared governance the way you are supposed to. The Faculty Senate has a subcommittee dedicated to technology governance — the body whose job is to review things exactly like this and make a recommendation. They reviewed it. They were impressed. They loved it.

Now, on paper, that subcommittee was advisory. It recommends and reviews; the full Faculty Senate is where the real decision effectively gets made. The subcommittee's "yes" was never, formally, an institutional authorization. I knew that.

And it didn't matter, because in practice its blessing functioned as a green light — for me, and for everyone downstream of me. Once the subcommittee was enthusiastic, the question stopped feeling open. Every step I was told to complete, I completed. The process ran exactly as I understood it.

Then it went to the broader Faculty Senate, and the broader Senate revolted.

That is the part worth your time. Not a process that failed me — a process I read correctly on the org chart and still over-read in the room. The gap between what the subcommittee was authorized to do and the weight its "yes" actually carried is the whole trap. And I walked right into it, with everyone around me.

Why the subcommittee couldn't feel it

The subcommittee was not wrong to like the feature. They evaluated it well — for the constituency they could feel. They just couldn't feel this one.

In our case, the subcommittee skewed toward faculty comfortable with technology — the people least likely to feel this particular loss of control when a tool reaches into the classroom. The feature didn't threaten how they teach. It may have delighted them.

But the cost wasn't distributed evenly across the faculty. It landed hardest on the professors whose pedagogy depended on controlling the sequence — and those professors were not in the room. The committee approved a trade they personally weren't going to pay. That is not a knock on their judgment. It is a fact about who was sitting there.

This trap generalizes well beyond higher education.

Delegated consent has limits

A subcommittee's "yes" is not the Senate's "yes." A subcommittee's blessing is not the constituency's consent — even when, in the moment, it sure feels like both.

We build delegated governance so leaders don't have to poll every stakeholder on every decision. That is the entire point, and it usually works. But delegation quietly assumes the delegates feel what the constituency feels. The moment a decision redistributes control rather than just adding value, that assumption breaks. The delegates who benefit, or who are simply comfortable, no longer represent the people who pay.

And the failure mode isn't that the formal authority is unclear. It's that an advisory "yes" stops feeling advisory once it's enthusiastic. Everyone downstream treats it as settled, because nobody wants to relitigate a recommendation the experts already loved.

You have seen this outside a campus. A steering committee signs off on the new system, and the people who do the work revolt at rollout. [NEEDS optional: a non-higher-ed parallel — e.g., a hospital's clinical informatics committee approving an EHR workflow the floor nurses then reject]. The committee was real. The approval was real. It just wasn't consent from the people whose day changed.

Shipping a feature that moves control from one group to another is not a technical act. It is a political act. And you cannot get political consent from a committee that doesn't pay the political cost — no matter what the org chart lets that committee sign.

What I'd do differently — and what I wouldn't

Here's the part I don't enjoy telling: we pulled the feature. Fully. Not a toggle, not an opt-in, not a quiet rollback to a pilot group. Gone. The student win got reversed because the faculty cost turned out to be one we couldn't hold.

And even so, I won't recant the idea. It helped students, and building it was the right instinct. What was wrong wasn't the feature — it was that I let an enthusiastic advisory "yes" carry me past the people who'd feel it, until removal was the only move left.

What I'd change is upstream of the build.

Before shipping the obvious win, I'd name the trade out loud: this helps students by taking X away from instructors. Saying it plainly forces the question you can otherwise dodge — who pays in control, not just who benefits in value.

Then I'd pressure-test the governance body itself. Not "did the committee approve it" but "does this committee actually contain the people who'll feel the cost?" If the answer is no, its approval isn't the answer you need — no matter how much formal weight that approval carries. So, alongside the formal process and not instead of it, I'd go find the people who will pay and ask them directly, before the green light, not during the revolt. Shared governance is the floor here, not the thing you route around.

And I'd treat backlash from a constituency that wasn't in the room as legitimate signal by default, not as resistance to be managed. The faculty who objected weren't behind. They were telling me what the subcommittee couldn't.

A caveat worth naming: this whole lesson assumes a campus with strong shared governance — a Faculty Senate with real teeth. Community colleges and heavily-unionized institutions route power differently, and the map of "who actually consents" looks different there. Find your version of the room.

The question to carry

Before you ship the obvious win, the question isn't "will they like it?"

It's: whose control does this quietly remove — and does the committee that approved it actually speak for them?

I had a clean process and a green light I read as more than it was. I'd rather have known the trade I was making than been reassured that the right people had nodded.

So here's what I'm genuinely curious about, because I don't think I'm the only one: when has your process worked exactly as you understood it and the thing still blew up? What did the green light hide?