Marketing and customer experience are where most leaders first meet AI, usually through a vendor demonstration. The demonstration shows what a tool can do. A better starting question is what job someone is trying to get done. Christensen, Hall, Dillon and Duncan's Harvard Business Review article "Know Your Customers' 'Jobs to Be Done'" (September 2016) argued that customers "hire" a product to make progress in a particular situation. The same lens works inside the firm: a marketer, a salesperson and a service agent each have jobs, and an AI tool earns its place only if it helps one of them get done faster or better.

Three families of job account for most of the value. Content and campaign production: generative AI drafts copy, variants and briefs, while predictive models decide which audience sees which version. Lead qualification and proposal drafting: predictive scoring ranks which prospects deserve a salesperson's time, and generative AI drafts the first version of a proposal. Service triage and agent assist: AI routes enquiries, answers the routine ones and gives human agents a suggested reply and the relevant policy for the rest. Amtrak's "Julie" is a long-running public example of the routine end: an automated assistant on the phone line and website that answers travel questions and passes callers to a person when they ask.

To see where each fits, this course uses its own five-stage customer journey: Discover, Decide, Buy, Use, Stay. Predictive AI tends to add most at Discover and Stay, where the questions are who to reach and who might leave. Generative AI helps most at Decide and Use, where customers need tailored explanations, proposals and answers. Agentic AI is emerging at Buy and Use, completing a booking or a change across several systems, and needs the tightest guardrails because it acts rather than advises.

Personalisation is the most common goal and the easiest to overdo. Segment-level personalisation tailors a message to a group; individual-level personalisation tailors it to one person's behaviour. Netflix and Spotify show the upside of individual recommendation at scale: the service becomes more useful the more it is used. The limit is the customer's sense of what you ought to know. Suggesting a next purchase from someone's own history feels helpful; revealing that you've inferred a life event they never told you about feels intrusive. A useful test: would the customer be comfortable if you explained how you knew?

For a professional services firm such as Meridian, the customer jobs sit mostly at Decide and Stay: choosing an adviser, and staying with one.

Operations and finance are where AI returns are easiest to measure, because the work is high-volume, the data is structured and outcomes are recorded. They are also where the change challenge is most often underestimated: a more accurate forecast that nobody trusts changes nothing.

In operations, AI increasingly meets the physical world. Warehouse robots pick and move stock, drones and cameras inspect assets, and autonomous vehicles work on controlled sites such as yards and mines. The robot is rarely the hard part for a leader. The decision logic around it is: what the system may decide on its own, what happens when it is unsure, and who is accountable when it is wrong.

Predictive maintenance shows that logic clearly. Scheduled maintenance services every vehicle at fixed intervals, whether it needs it or not. Condition-based maintenance uses sensor and operating data to service equipment when the data says failure is coming. Take Halden Freight, a fictional UK logistics operator whose lorries already send telematics data on braking, tyre pressure and temperature. A predictive model flags vehicles likely to suffer a brake or tyre failure. The leadership decision isn't about the algorithm; it is about two costs. A false alarm takes a lorry off the road for an unnecessary check. A miss means a roadside breakdown, a late delivery and a safety risk. Setting how sensitive the model should be is a business judgment about which error Halden would rather pay for.

In finance, three applications dominate. Financial close and reporting: AI reconciles accounts, flags exceptions and drafts variance commentary. Forecasting: predictive models combine sales, pipeline and external data into revenue and cash forecasts. Fraud and anomaly detection: models flag unusual payments, invoices or expense claims for review.

Before choosing any of these, put four questions to the process. Is it high-volume and repetitive? Is the data structured, digital and accessible, with a history of outcomes to learn from? Is there a clear right answer to measure the AI against? And what does an error cost, and can a person catch it before it lands?

If the process passes, redesign it as an AI-augmented workflow rather than bolting AI on. List the steps, give AI the ones that are repetitive and checkable, keep people on judgment, exceptions and sign-off, and mark the automation ceiling: the point beyond which errors are too costly, data too thin or rules too strict for AI to go further. In finance, sign-off on reported figures stays human; at Halden, so does the decision to send a flagged lorry back out.

HR, finance and IT share a pattern: a high volume of rules-based requests from inside the organisation. Where is the parental leave policy? How do I get my laptop set up? Is this expense claim allowed? Each answer exists somewhere, but finding it costs time on both sides. These business support functions are often the best place for an organisation's first internal AI, because the questions repeat, the answers are documented and a wrong answer can usually be corrected.

Start, again, from the job. Before choosing a tool, interview a handful of employees and managers about the moments HR is failing them: getting a straight answer to a policy question, getting onboarded quickly enough to do useful work in the first week, booking leave without three emails. Ask what they were trying to do, what they tried and what got in the way. The pain points you hear will be more specific, and more persuasive to a sceptical HR team, than any vendor's feature list.

HR also holds some of the highest-stakes applications in any organisation. Candidate screening ranks applicants; performance analytics scores employees; workforce planning shapes who is hired, moved or let go. These affect livelihoods, can reproduce bias in historical data and are hard for the person affected to challenge. That is why the EU AI Act lists AI used for recruitment and selection, and for decisions on promotion, termination, task allocation and monitoring or evaluating performance, among its high-risk uses in Annex III. Those obligations were due to apply from 2 August 2026; the Digital Omnibus on AI (Regulation (EU) 2026/1744) moved the date for stand-alone Annex III systems to 2 December 2027. The delay buys preparation time; it doesn't remove the obligation. Module 5 will cover what high-risk status requires in detail.

So separate the two kinds of HR AI clearly. An onboarding chatbot that answers policy questions supports employees and decides nothing about them. A screening or evaluation tool makes, or shapes, a decision about a person. The first needs accurate content, a clear statement that the user is talking to an AI, and an easy route to a person. The second needs all of that, plus evidence that it doesn't disadvantage particular groups, an explanation the affected person can understand, and a named human who reviews every outcome and can override it.

A short responsible AI policy for any HR application should answer three questions. How will you test for and monitor bias? What will employees and candidates be told, and when? Who can override the system, and how quickly?

A shortlist ranked by score is not yet a deployment plan. The top two candidates may land on the same overstretched team, or the third may depend on data that won't be ready for a year. Function sequencing decides which functions go first and why, so the organisation learns as it goes rather than absorbing everything at once.

Run four tests on every shortlisted deployment. Data readiness: is the data the use case needs consolidated, clean, accessible and permitted, or is there work to do first? Change capacity: is the function already absorbing a system migration, a restructure or a peak season? A good tool launched into a team at its limit will be ignored. Executive sponsorship: is there a function head who wants it, will defend it and will own its measure? Interdependency: does this deployment need something else first, such as shared data, an integration or a governance decision, and will its success make the next one easier?

The tests sort the shortlist from Module 2 into three waves. Months 0–6 take the readiest quick wins: off-the-shelf tools, ready data, a willing sponsor and visible results. Months 6–12 extend to functions that need integration work or a cleaner data source. Months 12–18 carry deployments that depend on consolidated data or a redesigned workflow. Each wave ends with a go/no-go gate: did the previous wave's measures move, and is the next function ready?

Most delays come from four blockers, and all four are prerequisites you can schedule. Scattered data: records sit in several systems or spreadsheets and must be consolidated. Access permissions: assistants that search internal documents, such as Microsoft 365 Copilot, can surface anything the user is permitted to see, so loosely set permissions become an oversharing risk on day one. System integration: the tool must read from and write to the systems people already use. Unclear ownership: nobody is accountable for the content or data the AI relies on, so nobody fixes it when it is wrong. Start each prerequisite as early as its lead time demands, usually a wave before the deployment it serves.

Use the cost structure from Module 3 to allocate budget across waves. Early waves are mostly licences and change effort; later ones carry more data preparation and integration. Watch change fatigue too: spread launches so that no single team carries two at once.

The AI Function Deployment Planner captures each function's plan in one place: owner, data readiness, dates, success metric and change plan.

Individual deployments add up to something larger only if the organisation builds capability as it goes. A maturity model helps a leader see where the organisation stands and what the next step requires.

This course uses the MIT CISR Enterprise AI Maturity Model, set out by Peter Weill, Stephanie Woerner and Ina Sebastian in a research briefing published in December 2024. It describes four stages. Stage 1, Experiment and Prepare, is about education and policy: training the workforce, setting acceptable-use rules, making data accessible and deciding where humans stay in the loop. Stage 2, Build Pilots and Capabilities, is about business cases and pilots: simplifying and automating processes, creating use cases, sharing data and using large language models to augment work. Stage 3, Develop AI Ways of Working, is about scale: shared platforms and dashboards, wider process automation, test-and-learn practices and designing for reuse. Stage 4, Become AI Future Ready, embeds AI in decisions and processes and in what the firm sells.

The briefing's headline finding is that financial performance rose with each stage: firms in the first two stages performed below their industry average on growth and profit, and firms in stages 3 and 4 performed above it. Treat that with care. The stages come from a survey of 721 firms in October 2022, before generative AI spread, so the AI being measured was mainly analytical. And the finding is an association, not proof that maturity causes performance: stronger firms may simply invest more in AI.

The direction of travel is towards zero-touch processes, which run end to end without human handling except for exceptions. They make sense where volume is high, rules are clear and errors are cheap and reversible: routing an invoice, resetting a password, answering a standard policy question. They don't make sense where a mistake is costly, hard to reverse or affects someone's rights, which is why client advice and employment decisions stay with people. The goal is rarely zero-touch everywhere; it is knowing which processes should get there.

Moving up a stage also needs an operating model. A central AI team concentrates scarce skills and sets standards, but can become a bottleneck. Hub-and-spoke keeps platforms, standards and governance in a central hub while functions own their use cases. A federated model puts capability in each function with light central coordination, and suits organisations already well advanced. Many start central, move to hub-and-spoke as functions build confidence, and federate only when practice is mature.

To place your own organisation, collect evidence rather than impressions. Is there an AI policy? Have people been trained? Are pilots measured against shared metrics? Is any AI working at scale inside a process?