Faculty Governance and Platform Decisions: How to Bring the Senate Along

Faculty governance is not an obstacle to overcome. It is the institutional design choice that makes platform decisions durable. The most transformative CIOs we have worked with treat the senate as a co-author, not a gate. They engage early, they bring the right artifacts, and they pick platform patterns that respect the rhythm of academic governance. This post is what that operational practice looks like in production. It is written for the higher ed CIO who has been in front of a senate and knows the dynamics. It is also written to be forwarded to the Provost or Faculty Senate Chair the CIO is partnering with on the next decision.

Why governance fatigue is the actual constraint

The five-year platform programs of the last two decades have asked the senate to vote on more replacement projects than the senate has political capital to support. This is not a failure of governance. It is a rational response to a pattern. The senate that has voted on three five-year platform programs in twelve years is right to be tired.

The published research backs this up. The 2023 EDUCAUSE study on ERP implementation in higher education found that success depended more on change management and stakeholder engagement than on vendor selection, the central finding of a sector-wide research effort. Our research review walks through this in detail. The CIOs who win the senate are the ones who recognize what the senate already knows.

This is the structural reason orchestration lands better than consolidation in faculty senate conversations. Orchestration is a different ask. Smaller, faster, reversible. The senate is not being asked to bet the institution on a five-year vendor relationship. They are being asked to approve a one-quarter pilot on a platform that already runs in IT.

The most transformative CIOs we have worked with frame platform decisions in those terms before the senate has to ask. The ask is not "approve a transformation." The ask is "approve a contained pilot, with a defined reversibility path, and we will come back with the data."

That is a vote a senate can give.

What faculty senates actually want from a platform conversation

Not vendor demos. Not architecture diagrams. Three things, in this order.

Who decides. The senate wants to know which decisions belong to the cabinet, which belong to the senate, and which belong jointly. The CIO who shows up without a clear decision rights map gets the conversation hijacked by the most senior senate member with the strongest opinion. The CIO who shows up with the map gets a working session.

Who gets hurt. Every platform decision creates winners and losers. Faculty whose workflows get disrupted. Staff whose roles change. Departments whose processes get standardized. The senate is not opposed to disruption. The senate is opposed to disruption it cannot see coming. The CIO who names the disruption explicitly is doing the senate's work for them, which is exactly what builds trust.

What is reversible. This is the question most CIOs do not lead with, and it is the question senates care most about. Five-year ERP replacements are not reversible in any practical sense. A one-quarter pilot of a workflow on top of an existing platform is. The reversibility of the platform pattern is more politically valuable than its sophistication.

The CIOs who answer all three before the senate asks are the ones who get co-design conversations instead of defensive ones. The conversation that follows is not a hearing. It is a working session.

The three engagement moments

The CIOs who do this well engage the senate at three specific moments. Skipping any one of them is the most common reason senate votes go sideways.

Moment 1: Before the project starts. Frame-setting. Bring the senate the diagnostic, not the solution. "We are seeing this pattern in our institution. Here is what the published research says. Here is what we are considering. We want your input before we scope a pilot." This conversation is the one that determines whether the senate will treat the eventual proposal as theirs or as something done to them.

Moment 2: At the pilot stage. Data plus reversibility. "Here is what we built in the pilot. Here is what the data shows. Here is what would happen if we stopped now versus what would happen if we expanded." The senate that gets this conversation has the artifacts they need to vote yes with confidence. They also have the artifacts they need to vote no without it being a betrayal of the prior conversation.

Moment 3: At the expansion stage. Institutional commitment. "Based on the pilot data and the senate's input, we are recommending expansion to the next domain over the following timeline. Here is the budget, the staffing, and the next reversibility checkpoint." This is the vote that funds the program. The senates that vote yes here are the senates that already voted yes at moments one and two.

The CIOs who treat all three moments as governance work, not project work, get a senate that builds with them. The senate is not a stakeholder to manage. It is a co-author of the institutional record.

What to bring to the senate

The most transformative CIOs we have worked with show up with a specific set of artifacts. These are not slide decks.

A written brief, one to two pages. Faculty governance runs on documents. A written brief gets read before the meeting, attached to the minutes, and quoted in subsequent debate. A slide deck does none of those things. Faculty senates have institutional memory measured in decades, and they remember what is in writing.

A one-paragraph executive summary. For the senate members who will not read the brief. Almost half of any senate will not. This paragraph carries the vote. Write it last, after the brief is finished, so it reflects the brief rather than the other way around.

A list of who has been consulted. Department chairs. Affected staff. Student government, where relevant. Faculty senate vote outcomes depend in large part on whether the political work has been done in the rooms before the senate room. The list of consulted parties is the document that demonstrates the political work happened.

A defined reversibility plan. What happens at the end of the pilot. What conditions trigger expansion. What conditions trigger a halt. This is the document that converts a vote-of-trust into a vote-of-evidence. It is also the document that makes a future "no" vote possible without it being a personal repudiation of the CIO.

A faculty co-sponsor. Not a CIO defending a project. A faculty member presenting alongside the CIO. The senate listens differently when the proposal comes from one of their own. The faculty co-sponsor does not need to be a technologist. They need to be respected.

These five artifacts together are the difference between a senate vote that approves and a senate vote that defers. The CIOs who run this practice consistently are the ones whose platforms survive leadership transitions.

How orchestration in particular fits faculty governance

The orchestration pattern fits the rhythm of faculty governance in ways replacement does not.

It is contained. A one-quarter pilot in one department, on a platform that is already running, is a vote the senate can give without putting the institution at risk.

It is reversible. The orchestration layer can be turned off. The systems of record stay in place. Nothing has been migrated. Nothing is locked in. The reversibility is not theoretical. It is architectural.

It is incremental. The senate can vote on each expansion separately. Trust accumulates one workflow at a time. The senate that has voted yes on three orchestration pilots in two years has built institutional confidence the same way they built confidence in any other gradual expansion of authority. By watching it work.

It produces evidence quickly. The data from the first pilot becomes the artifact for the next conversation. The senate is not being asked to trust a five-year roadmap. They are being asked to trust a one-quarter outcome.

This is why the orchestration framing of our Pillar 1 piece and the research review on ERP replacement both point to the same conclusion. Orchestration is not just better technology. It is better-shaped governance.

A note for Provosts and faculty senate chairs

This post is forwardable for a reason. The CIO who sends it is signaling something specific.

If you have received this from your CIO, the signal is this. They are not asking you to rubber-stamp a vendor decision. They are asking to engage the senate at moment one rather than moment three. They are committing to the artifact list above. They are committing to a reversibility plan.

That is a CIO worth working with. The platform decision will still belong to the cabinet. The institutional design choice belongs to you. The most durable institutions get both right.

If you have not received this from your CIO, it is also a useful artifact. The questions in this post are the ones a senate has every right to ask before any platform vote. The CIO who can answer them is the CIO ready for the conversation.

Frequently asked questions

What if our senate has been burned by past platform projects?

That is the most common starting point we encounter. The repair work is the artifact list above, applied to a small first pilot with a defined reversibility plan. Trust does not come back through a single conversation. It comes back through a single successful pilot, transparently reported, that vindicates the senate's prior caution rather than dismissing it.

Do we need to bring this conversation to the senate if it is just an IT pilot?

Probably yes, even if the answer is "we are informing you, not asking you to vote." Senates remember what they were told and when. A CIO who informs the senate of a pilot that later becomes contentious has institutional cover. A CIO who skipped the disclosure has none.

What if the Provost and the senate disagree?

That is a real institutional question, not a platform question. The artifact list does not solve it. What it does is force the disagreement into the open at moment one rather than moment three, which is when it can still be productive.

Where this leaves the institution

The CIOs whose platforms survive leadership transitions are the ones who treated faculty governance as the institution's design feature, not its bottleneck. The work is unglamorous. It is documentary. It is iterative. It builds slowly.

It is also the work that makes platform decisions durable across the leadership cycles, strategic plan revisions, and curriculum reforms that have killed every five-year platform program we have seen.

For the orchestration framing this post sits on top of, our Pillar 1 piece is the foundation. The full case is in our Beyond the Help Desk white paper.

If you want a working session on the engagement framework with your senate, that is what we do.

Bettera is the only ServiceNow consulting partner focused exclusively on higher education.