For the AI lead

Leading the effort

For whoever's been tasked with campus AI, Chief AI Officer or an informal lead, especially when the role is new, the authority is thin, and not everyone agrees it should exist. How to define the position, lead without formal power, and meet resistance without burning trust.

You've been asked to lead campus AI, with a title or a tap on the shoulder and a vague charge. The hard part is rarely the technology. The role is new, its authority unclear, and not everyone agrees it should exist. This page covers how to define the position, lead with a thin mandate, and meet resistance without burning the trust the job runs on.

Formal or informal, leading the effort is two jobs that reinforce each other. Structure without relationships is a charter no one honors; relationships without structure reset with every reorg.

Structural

The position itself: mandate, decision rights, reporting line, and resources. It tells the campus what the role is and gives it standing to act.

Defined in the role charter and in building authority without formal power.

Relational

The trust the role runs on: alliances with offices that already own pieces of this, and credibility with people who must change how they work. Earned person by person, not granted by title.

Built through the relationship map, the resistance playbook, and protecting the mandate.

Define the role first

Ambiguity sinks these roles. Define the position first, then get your sponsor to adopt it in writing. This charter is for the person, not the governance body (Pillar 4). Adapt every line; the value is in the conversation it forces.

Open the printable, adaptable role charter
01Purpose & mandate

Why does this role exist, in one or two sentences?

Starting languageTo coordinate the responsible adoption of AI across the institution in service of its mission, setting direction, enabling good practice, and stewarding risk, not to own every AI decision.

02What you own

What are you accountable for?

Starting languageInstitutional AI strategy and roadmap; convening governance; shared guidance, literacy, and the approved-tool path; coordinating risk review with the offices that own it.

03What you explicitly do NOT own

What stays with existing offices? (Naming this is what builds trust.)

Starting languageSecurity and infrastructure (CISO/CIO), legal and compliance (Counsel), procurement, academic policy (Senate), and unit-level operational decisions. You coordinate; they decide in their domains.

04Decision rights

What can you decide alone, what do you recommend, what must go to a body?

Starting languageDecide: guidance, the enablement program, what's on the approved list. Recommend: policy, major spend. Escalate: high-stakes or contested initiatives to the governance body.

05Reporting line & sponsor

Who do you report to, and who is your cabinet-level air cover?

Starting languageReport to the Provost or CIO; named cabinet sponsor who carries the mandate when it's challenged and renews it publicly.

06Resources

What people, budget, and time does the role actually require?

Starting languageProtected time (a real FTE share, not volunteer overtime); a small operating budget; access to IT, legal, and IR; a cross-functional body to convene.

07Success measures

How will this role be judged in a year, and on what it can actually control?

Starting languageDirection adopted; guidance live and used; a functioning governance cadence; risk reviewed before launch, not 'number of AI tools shipped.'

08Review & sunset

When is the mandate revisited, and how does it renew?

Starting languageReviewed at 12 months against these measures; renewed by the sponsor; structure adjusted as maturity grows so the role evolves instead of ossifying.

Map your relationships to existing roles

You aren't replacing anyone. You're the connective tissue between offices that already own pieces of this. Name what stays theirs, and the turf anxiety eases. Each role: their stake, the friction you'll feel, and how to partner.

Provost / CAO
Their stakeOwns academic mission, faculty relations, and usually the budget that matters.
The frictionMay see AI as IT's problem, or a threat to academic freedom.
How to partnerFrame AI as serving teaching and learning, and make them (or the President) your sponsor.
For cabinet & board
CIO / CTO
Their stakeOwns the systems AI runs on; often assumed to 'own AI' by default.
The frictionTurf: is this role above, beside, or under IT?
How to partnerSettle the boundary early, in writing: you set direction and governance; IT builds and operates.
IT, data & security
CISO / Security
Their stakeOwns data and system risk; AI is a fast-moving new threat surface.
The frictionBecomes the default 'no' if looped in late.
How to partnerBring them in early as a design partner, and route tool review through their process.
The intake & review path
General Counsel
Their stakeOwns legal and compliance exposure, the fastest-growing AI risk area.
The frictionRisk-averse by job; may want to wait for certainty.
How to partnerGive them a seat and open questions, not finished decisions. Proportionate review lets low-risk uses move.
Legal & compliance
Faculty Senate
Their stakeHolds authority over curriculum, integrity, and instruction. Can stop you.
The frictionSees AI mandates as administrative overreach.
How to partnerConsult before deciding; bring options, not edicts. Pedagogy is theirs.
Shared governance map
CFO / Budget
Their stakeOwns the money; AI is an ongoing operating cost.
The frictionWants ROI before commitment.
How to partnerBring effort tiers and a phased ask tied to mission outcomes, not a blank check.
Finance & budget
CHRO / People
Their stakeOwns workforce impact, training, and job change.
The frictionFear and workload land here first.
How to partnerCo-own enablement and change management; AI literacy is workforce strategy.
Engagement & enablement
Students & their advocates
Their stakeMost affected, least consulted.
The frictionDecisions made about them without them erode trust fastest.
How to partnerGive students a voting seat. They're your legitimacy and your early warning.
Public & transparency

Build authority without formal power

Most campus AI leads start with a thin or borrowed mandate. You lead by influence long before the org chart catches up.

Borrow authority before you have your own

Anchor every action to an adopted vision and a named sponsor. 'The cabinet asked me to coordinate this' carries further than your title at first.

Be useful before you're powerful

Solve a problem for a skeptical unit in month one: answer the question everyone's avoiding, or unblock a stuck pilot.

Convene, don't command

You rarely can mandate, and doing so would backfire. Bring the right people together and let shared decisions carry the weight.

Make the invisible visible

Inventory the shadow AI already in use, without blame. Naming reality makes the case for coordination better than any pitch.

Give credit away

Let units and partners own the wins. Hoarding credit collects rivals; sharing it collects allies.

Move at the speed of trust

Push faster than the culture allows and you'll be routed around. Momentum builds; overreach resets it.

The resistance playbook

Resistance is information, usually a legitimate concern behind a blunt objection. Take each one seriously; the response that respects the concern is the one that converts the skeptic.

The skeptic"This is hype. It'll blow over like the last thing."

The real concernThey've survived a dozen tech fads and been left with the cleanup. The fatigue is earned.

Your responseAgree that most of the hype won't last, then point to what's already in use on campus. Govern the durable questions (data, integrity, oversight), not the products.

The territorial peer"Why do we need a new role? My office already handles this."

The real concernA coordinating role can look like a demotion or a land grab.

Your responseLead with what they keep. Name in your charter what stays theirs, and position yourself as the link between offices, not a layer above them.

The faculty defender"This is administrative overreach into academic freedom."

The real concernA legitimate concern about who controls curriculum and pedagogy.

Your responseConcede the principle: pedagogy belongs to faculty. Bring options and evidence to the senate, and support their choice instead of making it.

The privacy & ethics advocate"This is surveillance. It'll harm the people we serve."

The real concernOften the most mission-aligned person in the room, and often right about the risk.

Your responseTreat them as an ally. Bring them into design early and let them shape the guardrails; their endorsement makes the program defensible.

The overwhelmed adopter"I don't have time for one more initiative."

The real concernWorkload and change fatigue; AI feels like extra work.

Your responseTake something off their plate. Lead with a time-saving use for their job, and fund the training. Adoption follows relief, not pressure.

The unconvinced executive"Show me the ROI before we invest."

The real concernAccountable for scarce dollars and wary of open-ended commitments.

Your responseBring effort tiers and a phased ask tied to mission outcomes. Name what you'll defer; restraint earns the next yes.

Protect the mandate

These roles fail from political erosion as often as from bad strategy. Protect the mandate as deliberately as you spend it.

Becoming the single point of failure

The tellEverything routes through you; nothing moves when you're out.

The fixDistribute ownership from the start: embedded leads, a standing body, documented decisions.

Owning the blame, sharing none of the credit

The tellYou're named when AI goes wrong, invisible when it goes right.

The fixWins belong to the institution, risk decisions to the body. Refuse accountability without authority in your charter.

Mandate decay

The tellThe energy that created the role fades; budget and attention drift.

The fixReport value to your sponsor on a cadence, and tie the role to the strategic plan and budget cycle.

Saying yes to everything

The tellYou're in every meeting, accountable for every AI question.

The fixUse 'what you don't own' as a boundary, and route what isn't yours to its owner.

A quick path through the framework

  1. 1
    See how it runs

    The meeting-in-a-box: the four recurring rituals (mission talk, intake, portfolio review, annual reset) with agendas.

    Governance Meeting Kit
  2. 2
    Diagnose where you stand

    The nine-domain governance self-assessment surfaces what's invisible, unowned, or missing.

    Governance Guide
  3. 3
    Choose a structure

    Five governance models, the roles each needs, and the design considerations behind them.

    Structures & considerations
  4. 4
    Prioritize initiatives

    Score candidate AI uses on six dimensions, including evidence they work, and right-size review to risk.

    Strategic Compass

Your first move: run the 90-minute mission & AI conversation and stand up monthly intake.