The posting went up on a Tuesday: "Head of AI Enablement," at a regional insurer that, eleven months earlier, had quietly scrapped two of its three GenAI pilots. The first paragraph was buzzword weather, "drive AI strategy across the enterprise," but the bullet points underneath told a different story: map current-state workflows, build adoption plans, manage vendor relationships, establish baseline metrics, report value to the executive committee. No line about building models. No line about Python. The company had spent a year learning, expensively, that its problem was never the technology, and now it was hiring the person whose job is to make sure that lesson never has to be purchased twice. Multiply that posting by every organization that lived through the failure record you studied in Chapter 1, and you get the subject of this chapter: a new role family is forming in the labor market, under half a dozen different titles, and the toolkit you have been assembling since the failure-mode checklist is precisely what it is hiring for.

The Failure Record Created a Labor Market

Every statistic from Chapter 1 implies a job. Read them again, this time as a hiring manager would.

MIT found that 95 percent of enterprise GenAI pilots delivered no measurable P&L return, and its autopsy blamed missing workflow integration, absent learning loops, and adoption without transformation. Each cause is an unstaffed responsibility. Somebody has to capture the baseline before launch, or nothing can ever be proven. Somebody has to redraw the workflow so the tool sits inside the process instead of beside it. Somebody has to sort the usage chart from the value metric and tell the steering committee which one it is looking at. In the organizations that landed in the 95 percent, nobody owned those jobs. That is not a technology gap; it is a vacancy.

The corroborating numbers each add a vacancy of their own. S&P Global's finding that 42 percent of companies scrapped most of their AI initiatives in 2025 implies someone who owns the portfolio: which pilots run, which are killed, and on what evidence, because scrapping "most initiatives" in one embarrassed sweep is what happens when no one held a stage gate. Gartner's finding that 63 percent of organizations lack AI-ready data practices, and that through 2026, 60 percent of AI projects without AI-ready data will be abandoned, implies someone who inventories the data before the pilot instead of during the post-mortem. Gartner's prediction that over 40 percent of agentic AI projects will be canceled by the end of 2027 implies someone who can tell an agent from a rebranded macro and design the guardrails before procurement signs. And BCG's 10-20-70 arithmetic, 10 percent algorithms, 20 percent technology and data, 70 percent people and process, is the budget's way of saying that most of the work of AI is work that operations, change, and process people already know how to do.

So organizations have started hiring for it. The titles are multiplying across postings: AI program manager, head of AI enablement, AI transformation lead, AI operations lead, AI governance analyst, AI readiness consultant. The titles are unstandardized because the role is young; the underlying job is remarkably consistent. It is the translator role: the person who stands between the business (which knows what it needs), the process (which determines what will actually work), and the technology (which is the easy 10 percent), and who owns the discipline that keeps the organization out of the failure statistics. This lesson maps that role family so you can see where you already fit.

The Role Family: Five Jobs, One Discipline

Strip the titles off and the postings sort into five recognizable jobs. They share a spine, the evidence-first readiness discipline this program teaches, but they differ in what you own day to day, and the difference matters when you decide which one to aim at.

The AI program manager

Owns the portfolio. The day-to-day is a pilot register with owners and dates, stage-gate reviews where initiatives present evidence or lose funding, vendor coordination across three or four concurrent contracts, and the steering-committee pack that reports value honestly. This person is the institutional answer to the 42 percent scrap rate: instead of one annual purge of embarrassing line items, a monthly discipline of scale, iterate, or kill, decided against pre-committed criteria. If you have ever run a PMO, a stage-gated product portfolio, or a multi-vendor implementation program, you have done most of this job under a different name.

The AI transformation or enablement lead

Owns the 70 percent. The day-to-day is change plans, role-by-role training that changes behavior rather than attendance, a champion network built from the enthusiasts a shadow-AI inventory surfaces, resistance mapping before the resistance organizes itself, and adoption measurement that distinguishes usage from value. This person exists because MIT's most seductive failure mode, adoption without transformation, is a change-management failure wearing a technology costume. Change managers, HR business partners, and L&D leads who can carry a KPI are the natural incumbents.

The AI operations or process lead

Owns the workflow. The day-to-day is process selection and triage, redesigning the swimlanes so the AI step has clean inputs and a defined destination, writing the verification step into the SOP instead of hoping for it, instrumenting the process with baselines and counters, and running pilots against those baselines. This is the most hands-on seat in the family and the one closest to the reason pilots fail: MIT's integration gap is repaired at exactly this desk. Six Sigma belts, Lean practitioners, BPM analysts, and operations managers who own cycle-time numbers are already doing the non-AI half of this job.

The AI governance or readiness analyst

Owns the inventory and the calendar. The day-to-day is a register of every AI system in use (sanctioned and shadow), policy that people can actually follow, vendor risk documentation, audit trails for AI-touched decisions, and the compliance calendar, which since the EU AI Act stopped being metaphorical: GPAI obligations have applied since August 2, 2025, transparency obligations for AI content arrive December 2, 2026, and high-risk obligations follow in 2027 and 2028. Compliance officers, internal auditors, quality managers, and risk analysts translate almost directly into this seat.

The fractional or consulting readiness advisor

Owns the assessment, for organizations too small to staff the other four seats. Mid-market companies face the same failure record with none of the internal machinery, so a market is forming for advisors who run a readiness assessment in two to four weeks, deliver a scored report with a remediation backlog, sit in on vendor demos with a due-diligence sheet, and design the first pilot with baselines and kill criteria attached. The deliverables are the program's artifacts, productized. This path suits consultants, fractional executives, and anyone building independence on top of an operations career.

Decoding the Postings: What They Ask For Under the Buzzwords

Open ten postings across these titles and the first lines will blur together: "define and drive AI strategy," "champion innovation," "shape our AI journey." Ignore the poetry and read the requirements the way you learned to read a vendor demo in Chapter 4: what is actually being asked for, operationally?

Five asks recur under nearly every title in the family:

• Process mapping. "Assess current-state workflows," "identify automation opportunities," "document business processes." The employer is asking whether you can find out how work actually happens, which, as Chapter 3 taught you, is the precondition for every AI decision worth making.
• Change management. "Drive adoption," "lead organizational change," "build training programs." This is the 70 percent, stated in job-description dialect.
• Vendor management. "Evaluate AI solutions," "manage vendor relationships," "lead RFP processes." The employer has read, or lived, the buy-versus-build record and wants someone who can run the Chapter 4 due-diligence discipline without being played.
• Measurement discipline. "Define success metrics," "establish KPIs," "demonstrate ROI." Translation: our last pilot had no baseline and we could not prove anything; never again.
• Stakeholder communication. "Partner with executives," "align cross-functional teams," "present to leadership." The translator function, named directly.

Now notice what is absent. Not model building. Not neural-network architecture. Not, in most of the family, any code at all. Where technical fluency appears, it is fluency of the kind Chapter 2 gave you: knowing what the four species of AI can and cannot do, what a hallucination is operationally, what RAG means in a vendor pitch. Say it plainly, because the market keeps whispering the opposite: these postings are won by operators, not engineers. The engineering is the 10 percent, and it is either bought from a vendor or staffed by a technical team the readiness role coordinates with. The scarce skill is the other 90: process, people, measurement, and the spine to kill a pilot in public.

The postings are written in the language of AI, but they are won in the language of process.

This is also your filter for postings to avoid. A posting that buries "5+ years building ML models in production" inside an "AI transformation lead" title is either a mislabeled engineering role or a company that has not decided what it is hiring; both are someone else's problem. The family described here asks for what you have.

Where the Role Sits, and Why the Seat Matters

Before you chase a title, look at the reporting line, because the same job succeeds or suffocates depending on where the org chart puts it. Four seats recur.

Inside operations. The role reports to a COO or VP of operations. Strength: proximity to the processes, the baselines, and the P&L, which makes evidence easy to gather and impact easy to prove. Weakness: reach; an ops-seated role can struggle to touch workflows in sales, finance, or legal without borrowed authority. The operations and process lead thrives here.

Inside a transformation office. The role reports to a chief transformation officer or program director. Strength: enterprise-wide mandate and executive air cover, which the program manager and enablement lead need. Weakness: distance from the work; transformation offices can drift into slideware if they do not keep one foot in a live process, and their mandates are only as durable as their executive sponsor.

Inside IT. The role reports to a CIO or IT director. Strength: control of the integration surface, the data, and the vendor stack, plus a natural home for the governance analyst's inventory. Weakness: framing; an IT-seated readiness role is forever fighting the assumption that AI is a technology project, which is the exact assumption the failure record convicts.

Inside a center of excellence (CoE). A small dedicated AI team serving the whole business. Strength: concentration of scarce expertise and consistent method across functions. Weakness: the ivory-tower failure mode; a CoE that assesses and advises without ever owning a live process number becomes a bottleneck other functions route around. The best CoEs staff themselves with people rotated in from operations, which is a door worth knowing about.

None of these seats is wrong, but in an interview, the reporting line is a diagnostic question you should ask: "Who does this role report to, and who owns the pilot budget?" A readiness role with no seat near the money and no path to the process is a title without a lever, and you have already studied, in Chapter 1, what happens to initiatives without owners.

The Credibility Problem, and What Hiring Managers Screen For Instead

Here is the awkward fact that shapes every hiring process in this family: the role is younger than the experience requirement. Nobody has five years of AI readiness experience, because five years ago the discipline did not have a name. Hiring managers know this. They cannot screen on tenure, so they screen on the only two things that exist: artifacts and stories.

An artifact is evidence you have done the work: a readiness assessment you ran, with the scored grid to show for it. A shadow-AI inventory with a triage of what it found. A pilot you measured against a baseline, including, and this lands harder than any success, a pilot you killed on evidence and documented honestly. A workflow you redesigned around an AI step, with the before-and-after process map and the verification step visible in the SOP. A vendor evaluation with the due-diligence sheet scored and the verbatim answers logged.

A story is the artifact narrated with its consequences: "we were about to sign a $180,000 contract, I ran the reprice worksheet from our due-diligence process, the true first-year cost came out at $310,000, and we negotiated the pilot to a success-gated contract instead." Sixty seconds, one number at the start, one decision at the end. Interviewers in this family are listening for exactly that shape, because it is the shape of the job.

Now connect this to what you have been doing since Chapter 1. The failure-mode checklist, the value-metric worksheet, the shadow-AI inventory, the Afternoon Triage, the data pre-check, the people-readiness pulse, the demo-conditions checklist, the reprice worksheet, the 20-question due-diligence sheet: the readiness portfolio this program has you build, lesson by lesson, is not homework. It is the interview. Every artifact you file is a screening question you have already answered, and by the L2 and L3 capstones you will have run assessments and measured pilots that most applicants for these roles have only described in the abstract.

The Artifact: The Role-Map Matrix

This lesson's artifact is the map you will use for the rest of Chapter 5: the five roles, what each one owns, the artifacts that prove you can do it, where this program builds those artifacts, and who the seat usually reports to. Use it in three directions: to pick the role that fits your background, to plan which artifacts to build first, and to decode any posting by matching its bullet points to a row.

Two honest notes on reading the matrix. First, the rows blur in practice: in a 400-person company one person may hold three rows at once, and in an enterprise each row may be a team. Second, resist the urge to pick the row with the grandest title. Pick the row whose "what you own" column describes work you have already done in another vocabulary, because that is the row where your first ninety days produce evidence instead of orientation.

Worked Example: How Priya Created Her Own Job

A composite, assembled from the pattern this lesson keeps insisting on, with realistic numbers. Priya Raman is a Six Sigma black belt at Meridian Fastener Works, a fictional 900-person industrial manufacturer. She owns continuous improvement for order-to-cash and has spent eleven years being the person who knows where the process bodies are buried.

In one year she watches two AI pilots stall from the bleachers. The first is a production-scheduling copilot: $95,000 in license and integration, launched with an all-hands demo and no baseline of current scheduling cycle time, so when the plant manager asks at month seven what it changed, the honest answer is that nobody can say, and "nobody can say" becomes "under review," which becomes a renewal nobody defends. The second is a quote-drafting tool for inside sales: the usage chart climbs for a quarter, then a customer receives a quote citing a volume discount that does not exist, and the tool is quietly turned off with no post-mortem. Two pilots, roughly $150,000 of direct spend, and the only organizational learning is a flinch. She recognizes both corpses from this program's Chapter 1: no baseline, no verification step, adoption charts mistaken for value.

What Priya does next costs her about twelve working hours and no permission. She runs a shadow-AI inventory across the office staff, amnesty framing borrowed from Chapter 1.5, and finds 38 of 120 respondents using unsanctioned AI tools, including a purchasing analyst who has quietly built prompt templates that save her about six hours a week on supplier correspondence, with confidential pricing data flowing through a free consumer account as the unpriced risk. Then she runs Chapter 3's Afternoon Triage on twelve candidate processes: two score 7 to 8 (ready now, both in the document-heavy back office, exactly where Chapter 1 said the ROI hides), five score 5 to 6 with named gaps, and five score 0 to 4, including, awkwardly, the production-scheduling process the first pilot had been aimed at. The dead pilot had been pointed at a process that a one-afternoon instrument would have disqualified for free.

She compresses all of it into a one-page readiness memo: what we spent, what we learned, what the inventory found, the triage scores, and a recommendation to pilot exactly one process (supplier-invoice matching, scored 8) with a baseline captured first and kill criteria in writing. The COO reads it twice, asks who told her to do this, and hears "no one." Three months later, Meridian creates an "AI process lead" role reporting to the COO, written substantially around what Priya has already demonstrated, and she takes it without a competitive interview, because the interview had already happened: it was the memo.

Draw the moral explicitly, because it is the most reliable career fact in this young field: the role was created by the artifact, not by a posting. Priya did not wait for a job description to authorize the work; she did the assessment before anyone asked, and the organization built the seat around the person already sitting in it. Talk to people holding these titles today and you will hear this origin story again and again: the inventory, the triage, or the memo came first, and the title followed. It is the most common on-ramp into the role family, it is available to you without anyone's permission, and it is precisely the sequence your Monday-morning steps have been rehearsing since Chapter 1.

What to Do Monday Morning

This lesson converts into action as a mapping exercise: the market on one side, your evidence on the other.

1. Collect ten live postings. Search the title family: AI program manager, AI enablement lead, AI transformation lead, AI operations lead, AI governance analyst. Save the ten most serious ones to a folder; this is your market sample.
2. Highlight the verbs, ignore the adjectives. In each posting, mark every concrete ask (map, measure, train, evaluate, govern, report) and strike the strategy poetry. Sort the marked asks into the five recurring categories: process mapping, change management, vendor management, measurement, stakeholder communication. Watch the pattern confirm itself.
3. Place each posting on the Role-Map Matrix. Match its bullet points to a row. Postings that match no row, or that demand production ML engineering under a readiness title, get discarded; that is the filter working.
4. Pick your row and audit your evidence. Choose the row whose "what you own" column you have already done in another vocabulary. Then list which of its proving artifacts you hold today and which lessons of this program build the missing ones; that list is your study plan for the rest of the certification.
5. Write one sixty-second story. Take the strongest thing you have already done (a process you stabilized, a project you measured, a vendor you held to evidence) and draft it in the interview shape: number at the start, decision at the end. File it with your portfolio; you will collect more of these deliberately from now on.

Key Takeaways

• Read the failure record as a hiring forecast: every Chapter 1 statistic (95 percent without measurable return, 42 percent scrapped, 63 percent not data-ready, 40 percent of agentic projects headed for cancellation) is an unstaffed responsibility that organizations are now creating roles to own.
• Map any posting in the family to one of five jobs: the program manager (portfolio and stage gates), the transformation lead (the 70 percent), the operations and process lead (workflow redesign and instrumentation), the governance analyst (inventory, policy, and the regulatory calendar), and the fractional advisor (assessments as a product).
• Decode postings by their verbs, not their strategy language: the recurring asks are process mapping, change management, vendor management, measurement discipline, and stakeholder communication, and these roles are won by operators, not engineers.
• Check the seat before you chase the title: operations gives proximity to the P&L, the transformation office gives reach, IT gives the integration surface but risks the technology-project frame, and a CoE concentrates expertise but can drift into an ivory tower; always ask who the role reports to and who owns the pilot budget.
• Solve the credibility problem the only way it can be solved: nobody has five years of AI readiness experience, so hiring managers screen for artifacts and stories, and the readiness portfolio this program builds is the interview, assembled in advance.
• Use the Role-Map Matrix in three directions: pick the row that matches work you have already done in another vocabulary, plan the artifacts that prove the row, and filter postings by matching their bullets to a row or discarding them.
• Copy Priya's sequence, not her circumstances: run the inventory and the triage before anyone asks, compress the findings into a one-page memo, and let the role be created around the demonstrated work; the artifact creates the role far more often than the posting does.
• Carry the thread into the next lesson: the family is real and the postings are multiplying, and the reason process professionals specifically keep winning these seats is the subject of the lesson that follows.