For cabinet & board

Leadership essentials

The decisions only leadership can make, how to bring faculty and students along, and what most AI material skips: who owns it, what it costs, what not to do, and how it goes wrong.

Benchmarks and cost tiers here are pattern-based, not survey data. They describe what comparable institutions typically do, not measured outcomes.

The one slide you'll actually get

A one-page brief for the board

The whole model and the single 90-day ask on one printable page, to forward before a meeting.

Open the one-page brief

What tends to matter, by institution type

Maturity varies widely within every type; what's predictable is where a mission pulls AI priorities first. Read this for typical concerns and pitfalls, not as a ranking.

Community & two-year college

Mission centers on access, affordability, and workforce relevance, with close ties to employers and transfer pathways.

First energy
Access, workforce relevance, and employer-facing skills.
The trap
AI access dividing by who can pay, widening the gaps the access mission exists to close.

First moveAnchor AI decisions to the access and workforce mission, and make equitable student access an explicit requirement.

Regional public university

Broad-access mission across several colleges, with parallel initiatives that need connecting and unclear decision rights.

First energy
Connecting scattered pilots and giving someone decision rights.
The trap
Initiatives multiply with no shared decision path, so each college re-argues the same questions.

First moveRoute coordination through one cross-college body with decision rights and fast lanes for low-stakes uses.

Large public research (R1 / R2)

Decentralized, with authority spread across strong colleges, which makes one uniform policy hard.

First energy
Research integrity, funder compliance, and data governance across units.
The trap
Centralizing everything; a single mandate collides with college and faculty autonomy.

First moveGovern by data, behavior, and risk (not by unit), and give the senate a standing role in academic AI policy.

Private liberal arts college

Small and teaching-centered, with dense faculty governance, a strong values identity, and lean staffing.

First energy
Teaching, academic integrity, and values alignment, with faculty voice central early.
The trap
The conversation becomes a referendum on banning AI instead of a values-led design choice.

First moveLead with mission and faculty co-design: adapt syllabus AI statements and ratify principles through governance.

Private research university

Multiple schools, often a medical center, and central IT; the challenge is a shared operating model.

First energy
Risk, reputation, and a defensible portfolio of high-stakes systems.
The trap
Documentation theater: heavy process on low-risk tools while high-stakes systems go untracked.

First moveRegister and monitor high-stakes systems only; keep light paths for everything else.

Multi-campus system or district

Campuses at different readiness levels; the system office must set a floor without flattening them.

First energy
Common principles and minimums without overriding campus autonomy.
The trap
A one-size mandate the most advanced campus has outgrown and the least ready can't meet.

First moveSet system-wide principles and a minimum bar; let each campus set its own pace above it.

Who owns it, and what it costs

The first cabinet question is "Who's accountable, and who pays?" Three places governance can live, and three effort tiers.

Where it can live

Provost-led

Best whenInstitutions where teaching, integrity, and faculty governance are the center of gravity.

Anchors AI to mission and academic authority; the senate trusts the venue.

Can under-weight infrastructure, security, and operational AI. Pair with a strong CIO.

CIO / IT-led

Best whenInstitutions whose pressing risks are data, security, procurement, and embedded AI.

Strong on tooling, data classification, and documentation; close to where AI enters.

Faculty may see it as a technology decision. Give the senate a voting seat.

Cabinet-chartered cross-functional body

Best whenMost institutions past the earliest stage: a standing group with delegated decision rights.

Balances academic, IT, legal, and student voices; survives leadership turnover.

Becomes theater without a named owner, a charter, and authority to decide.

What it takes, effort, not just dollars

Start-light
People
Part of one person's job
Spend
Essentially no new budget: time, not dollars
You get
A front door, an adopted one-pager, and acceptable-use guidance. Enough to prevent the obvious harms.

Nascent campuses, or anyone proving the lightest version works first.

Coordinated
People
A small part-time cross-functional group with a named lead
Spend
Modest: reallocation, some training, maybe an enterprise license you already have
You get
Intake, risk tiering, a baseline maturity read, and 1–2 visible initiatives run through the Compass.

Emerging campuses connecting scattered pilots.

Funded program
People
A dedicated owner or small office with budget authority
Spend
A dedicated line item: staff time, tooling, and monitoring for high-stakes systems
You get
A maintained registry, portfolio tracking, monitoring and incident response, and an annual review cycle.

Established programs hardening for durability, not expanding for its own sake.

What not to do in year one

Everything looks important. Here's what to defer.

Stand up a big new standing committee first

Authority with nothing to govern becomes theater. Use an existing meeting; formalize once there's a portfolio.

Write a full AI policy before you've run anything

Policy written ahead of practice ages badly. Write guidance for the questions you actually face; let policy follow evidence.

Ban student AI use as the headline move

Bans are unenforceable, push use underground, and widen gaps between students. Set course-level expectations instead.

Document every system at once

A full registry on day one stalls. Inventory the highest-risk handful first.

Chase maturity in pillars that don't match your risks

Effort should follow actual exposure, not an even radar chart. Leave low-stakes areas light on purpose.

Buy a flagship platform to signal seriousness

Tools don't replace governance. A purchase before there's an owner and acceptable-use guidance usually creates shadow AI.

How you'll know it's working, and how it goes wrong

Signals that matter, instead of vanity metrics, and the common ways it fails.

Signals it's working
  • Initiatives arrive through one intake instead of routing around governance.
  • Routine, low-risk uses get a decision in days, not weeks.
  • The senate and student government can name their role in AI decisions.
  • Your highest-stakes systems have a named owner and an appeal path.
  • People surface shadow AI to you instead of hiding it.
  • The program survives a leadership change without losing its cadence.
Where it goes wrong
Committee theater

A council meets and minutes pile up, but no decision gets faster.

FixGive it decision rights and a named owner, or fold the work into an existing body.

Ban-and-whack-a-mole

Each new tool triggers a new prohibition; AI use moves off the books.

FixGovern by disclosure, data, and human-in-the-loop, not product names.

Documentation theater

Heavy paperwork on harmless tools while a high-stakes model runs unregistered.

FixMatch review to risk: full scrutiny for high-stakes systems, light paths for the rest.

The equity gap widening

Students who can pay for premium tools pull ahead; accommodations lag.

FixMake access and accessibility explicit success criteria.

Consultation-after-the-fact

Faculty are 'consulted' after the decision is made; trust erodes.

FixDefine which decisions need senate input before they're settled.

Taking it to faculty senate

The objections you'll hear, each taken seriously, with a response that respects faculty authority and what to bring.

"This infringes on academic freedom and my classroom."

The underlying concernA central policy could dictate how a professor teaches or assesses.

Teaching, assessment, and academic integrity belong to faculty through shared governance. Institutional policy sets the floor (data protection, disclosure, accountability) and leaves classroom choices to the instructor.

Bring: The shared-governance authority map and adaptable (not mandated) syllabus statements.

"An AI policy means surveilling students and faculty."

The underlying concernDetection and monitoring tools could be punitive and inaccurate.

Govern by disclosure and design, not surveillance. Keep human judgment on consequential decisions; treat detection tools as unreliable and never as sole evidence.

Bring: The red/yellow/green acceptable-use grid and the human-in-the-loop requirement for high-stakes uses.

"You're moving too fast. This is consultation theater."

The underlying concernDecisions arrive finished, with token faculty input.

Name in advance which decisions require senate review and when. Academic AI policy goes through governance before adoption, written into the charter.

Bring: A draft charter naming the decisions that require senate consultation.

"This is an unfunded mandate on already-stretched faculty."

The underlying concernMore committees, more service, no resources.

The recommended start is light: adapt one syllabus statement, join one existing conversation. Heavy process is reserved for high-stakes initiatives.

Bring: The 'what not to do in year one' list and the start-light path.

"Banning AI is simpler and safer."

The underlying concernAllowing AI invites cheating and erodes rigor.

Bans are unenforceable and push use underground, which is less safe. Clear course-level expectations with disclosure preserve rigor and prepare students for a world that uses these tools.

Bring: Examples of tiered course-level AI expectations by assignment type.

"Why should faculty trust IT or administration to lead this?"

The underlying concernA technology office making academic decisions.

It shouldn't lead academic decisions. IT governs infrastructure and vets tools; the senate holds primary authority over the academic core.

Bring: The spheres-of-authority map showing faculty-led, shared, and administrative zones.

See the full shared-governance authority map

Students: where you'll take the most heat

Integrity, access, and accommodation draw the most questions. Four decisions to make on purpose.

AI you didn't choose to buy

Most campus AI didn't arrive through a decision. It was switched on inside tools you already license (LMS, CRM, productivity suite, ERP) or brought in on personal accounts. You govern it either way.

A quick path through the framework

  1. 1
    Read the one-page brief

    The whole model (pillars, Compass, the 90-day ask) on a single page you can print or forward.

    Open the brief
  2. 2
    See the case for it

    How the framework's coverage compares to NIST, ISO 42001, and the EU AI Act, and where it's honestly thinner.

    Standards alignment
  3. 3
    Anchor it to mission

    The first pillar: why AI strategy must answer to institutional purpose, with a worked example.

    Mission & Vision
  4. 4
    Approve a light start

    What a 90-day, low-risk start looks like, one conversation, a readiness baseline, one initiative.

    Adoption pathways

The one ask for your table: approve a 90-day light-touch start, then review the evidence.