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, maybe with a title, maybe with a tap on the shoulder and a vague charge. The hardest part is rarely the technology. It's that the role is new, its authority is unclear, and not everyone agrees it should exist. This page is for you: how to define the position so the campus knows what to do with it, how to lead when your mandate is thin, and how to meet resistance without burning the trust the job runs on.

Whether your role is formal or informal, leading the effort is two jobs at once, and they reinforce each other. Structure without relationships is a charter no one honors; relationships without structure is goodwill that resets with every reorg.

Structural

The position itself: a defined mandate, decision rights, a reporting line, and resources, the scaffolding that 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 actually runs on: alliances with the offices that already own pieces of this, and credibility with the people who must change how they work, built person by person, not granted by title.

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

Define the role first

Ambiguity is what sinks these roles. Before the work, define the position, then take it to your sponsor and get it adopted in writing. This is a charter for the person, distinct from the AI governance body's charter (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 fear it threatens academic freedom.
How to partnerFrame AI as serving teaching and learning; make them (or the President) your sponsor. Their backing is your mandate.
For cabinet & board
CIO / CTO
Their stakeOwns the systems AI runs on and is often assumed to 'own AI' by default.
The frictionTurf, is this role above, beside, or under IT? Ambiguity breeds conflict.
How to partnerSettle the boundary early and in writing: you set direction and governance, IT builds and operates. Allies, not rivals.
IT, data & security
CISO / Security
Their stakeOwns risk for data and systems; AI is a new and fast-moving threat surface.
The frictionCan become the default 'no' if looped in late or treated as a checkbox.
How to partnerBring them in early as a design partner; route tool review through their process, don't around it.
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 slow or block until certainty exists.
How to partnerGive them a seat and real questions, not finished decisions. Proportionate review lets low-risk uses move while they focus on real exposure.
Legal & compliance
Faculty Senate
Their stakeHolds authority over curriculum, academic integrity, and instruction. Can stop you.
The frictionSees AI mandates as administrative overreach into academic territory.
How to partnerConsult before deciding; bring options, not edicts. Respect that pedagogy is theirs.
Shared governance map
CFO / Budget
Their stakeOwns the money; AI is an ongoing operating cost, not a one-time buy.
The frictionWants ROI before commitment; wary of open-ended spend.
How to partnerBring honest effort tiers and a phased ask, not a blank check. Tie spend to mission outcomes.
Finance & budget
CHRO / People
Their stakeOwns workforce impact, training, and the change AI forces on staff jobs.
The frictionAdoption is a people problem; fear and workload land here first.
How to partnerCo-own enablement and change management; AI literacy is a workforce strategy, not just IT training.
Engagement & enablement
Students & their advocates
Their stakeMost affected, least consulted; integrity, access, and equity land on them.
The frictionDecisions made about them without them erode trust fastest.
How to partnerGive students a real seat. Their voice is your legitimacy and your early-warning system.
Public & transparency

Build authority without formal power

Most campus AI leads start with a thin or borrowed mandate. You lead by influence long before you lead by org chart. These are the moves that build real authority faster than a title would.

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, until your own credibility catches up.

Be useful before you're powerful

Solve a real problem for a skeptical unit in month one, answer the question everyone's avoiding, unblock a stuck pilot. Usefulness earns standing that authority can't grant.

Convene, don't command

You rarely have the power to mandate, and using it would backfire. Your leverage is the table you set: bring the right people together and let shared decisions carry the weight.

Make the invisible visible

Inventory the shadow AI already in use. Naming reality, without blame, makes the case for coordination better than any pitch, and positions you as the one who sees the whole board.

Give credit away

Let units and partners own the wins. A coordinator who hoards credit collects rivals; one who distributes it collects allies, and allies are durable authority.

Move at the speed of trust

Push faster than the culture allows and you'll be routed around. Right-size your ambition to what the institution can absorb; momentum compounds, overreach resets it.

The resistance playbook

Resistance is not failure. It's information, and usually a real concern wearing a blunt objection. Steelman each one; 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 sold as revolutions and been left with the cleanup. The fatigue is earned.

Your responseAgree that the hype is real and most of it won't last, then point at what's already in use on campus today. You're not chasing a trend; you're governing a reality that's already here. 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 new coordinating role can look like a demotion or a land grab over their turf.

Your responseLead with what they keep, not what you take. Name explicitly in your charter what stays theirs; position yourself as the connective tissue between offices, not a layer above them. Make them more effective, not smaller.

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

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

Your responseConcede the principle outright: pedagogy belongs to faculty. Bring options and evidence to the senate, not edicts. Your job is to enable informed faculty choice, not to make the choice for them.

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 frequently right about the risk.

Your responseTreat them as an ally, not an obstacle. Bring them into design early; let them shape the guardrails. Their scrutiny makes the program defensible, and their endorsement is worth more than anyone's.

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

The real concernReal workload, real change fatigue. AI feels like extra work, not relief.

Your responseDon't add to their plate, take something off it. Lead with a concrete, time-saving use for their actual job, and resource the training. Adoption follows relief, never pressure.

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

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

Your responseBring honest effort tiers and a phased ask tied to mission outcomes, not a blank check. Name what you'll defer. Disciplined restraint reads as credibility and earns the next yes.

Protect the mandate

These roles fail as often from political erosion 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 real body, documented decisions. Build the program to outlive you.

Owning the blame, sharing none of the credit

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

The fixMake wins the institution's and risk decisions the body's. Accountability without authority is a scapegoat seat, refuse it in your charter.

Mandate decay

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

The fixReport visible value to your sponsor on a cadence; tie the role to the strategic plan and budget cycle so it renews structurally, not on goodwill.

Saying yes to everything

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

The fixA defined scope is a survival tool. Use 'what you don't own' as a real boundary, and route what isn't yours to who owns it.