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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.'
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.
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.
Most campus AI leads start with a thin or borrowed mandate. You lead by influence long before the org chart catches up.
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.
Solve a problem for a skeptical unit in month one: answer the question everyone's avoiding, or unblock a stuck pilot.
You rarely can mandate, and doing so would backfire. Bring the right people together and let shared decisions carry the weight.
Inventory the shadow AI already in use, without blame. Naming reality makes the case for coordination better than any pitch.
Let units and partners own the wins. Hoarding credit collects rivals; sharing it collects allies.
Push faster than the culture allows and you'll be routed around. Momentum builds; overreach resets it.
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 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 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 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 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 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 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.
These roles fail from political erosion as often as from bad strategy. Protect the mandate as deliberately as you spend it.
The tellEverything routes through you; nothing moves when you're out.
The fixDistribute ownership from the start: embedded leads, a standing body, documented decisions.
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.
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.
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.
The meeting-in-a-box: the four recurring rituals (mission talk, intake, portfolio review, annual reset) with agendas.
Governance Meeting KitThe nine-domain governance self-assessment surfaces what's invisible, unowned, or missing.
Governance GuideFive governance models, the roles each needs, and the design considerations behind them.
Structures & considerationsScore candidate AI uses on six dimensions, including evidence they work, and right-size review to risk.
Strategic CompassYour first move: run the 90-minute mission & AI conversation and stand up monthly intake.