Why this module exists
You cannot govern what you cannot picture.
Executives are routinely asked to fund, approve and defend systems described to them entirely in metaphor. The model "understands" the contract. It "thinks" about the options. It "learns from your data." Every one of those words is doing damage, because each imports a set of expectations that the machine does not meet — and the gap between the expectation and the machine is exactly where projects fail.
This module replaces the metaphors with a mental model that is accurate enough to make decisions on and simple enough to hold in a meeting. There is no mathematics and no code. There is one idea per lesson, and each one has a direct managerial consequence.
1.1 Prediction, not retrieval
Here is the whole thing in one sentence: a language model produces a likely continuation of the text it was given.
It is not looking anything up. There is no document inside it that it consults, no database of facts it queries, no index it searches. It has been exposed to an enormous quantity of text and has settled into a very large set of numerical parameters that encode statistical regularities in that text. When you give it a prompt, it produces what tends to follow text like that — one fragment at a time, each choice conditioned on everything before it.
Almost every surprising behaviour follows from that single fact.
Why it hallucinates. A plausible continuation and a true continuation are different things that usually coincide. When they diverge — an obscure fact, a case citation, a part number — the machine produces the plausible one, because plausibility is the only thing it is optimising. It is not lying and it is not broken. It is doing exactly what it does.
Why it is fluent. Fluency is the easiest property of text to learn, because it is the most regular. Fluency arrives long before accuracy, which is why output sounds authoritative at capability levels far below the ones that make it reliable. This is the single most expensive confusion in enterprise AI.
Why it struggles to say "I don't know." Refusal is a rare continuation in most text. Confident answers are common. The model reproduces that distribution unless something in the system deliberately corrects for it.
Why the same question gives different answers. Selection among likely continuations involves deliberate variation. Two identical requests can produce different outputs. This is not a defect to be reported; it is the technology. It is also why any process that requires the same input to yield the same output must not have a model at that step — a point Module 3 turns into a test.
1.2 Training, context and memory are three different things
This is the distinction most often collapsed in planning meetings, and collapsing it produces expensive plans.
| What it is | Timescale | Who controls it | Typical cost | |
|---|---|---|---|---|
| Training | The parameters formed by exposure to a very large corpus | Months, done once by the provider | The model provider | Enormous, already spent |
| Fine-tuning | A modest adjustment of an existing model on your examples | Hours to days | You | Moderate, and repeated whenever your data changes |
| Context | The text you supply at the moment of the request | Milliseconds, every request | You | Paid per request, forever |
| Memory | What a system stores between requests and chooses to re-supply as context | As long as you keep it | You | Ordinary storage |
Three consequences worth stating to a board:
"We'll train it on our data" is usually the wrong plan. What people almost always want is for the system to know things about their business. Retrieval delivers that: keep your documents where they are, find the relevant ones at the moment of the question, and put them in the context. Fine-tuning does not reliably install facts, it is stale the moment your data changes, and it turns a content problem into a machine-learning project.
Fine-tuning is for form, not for facts. It is the right tool when you need consistent structure, house style or a narrow output format, and the wrong tool when you need the system to know today's price list.
A model has no memory of you. Anything that feels like memory is a system storing something and re-supplying it. That is a design decision with retention and deletion consequences — which is precisely why Module 6 treats it as a governance control rather than a feature.
1.3 Model, workflow, agent
These three words are used interchangeably in the market and mean quite different things. The course uses the distinction Anthropic draws, because it is the one that maps to cost and risk:
| What it is | Predictability | Where it fits | |
|---|---|---|---|
| A model call | One request, one response | High for a fixed prompt | A single judgement step |
| A workflow | Models and tools orchestrated through predefined code paths | High — you wrote the path | Most enterprise work |
| An agent | The model directs its own process, choosing tools and steps | Low by construction | Open-ended tasks where the path cannot be known in advance |
Agency is a dial rather than a switch, and every notch along it trades predictability for flexibility while adding latency and cost. Anthropic's own guidance is unusually direct about this, given their commercial interest: find the simplest solution possible, and increase complexity only when needed.
The managerial version: an agent is what you use when you genuinely cannot enumerate the steps in advance. If you can draw the flowchart, build the flowchart. A system that decides its own steps will also decide steps you did not anticipate, and you will discover them in production.
Most enterprise value sits in workflows. Most enterprise disappointment comes from buying agents.
1.4 The economics that should shape your plan
Two forces set the terms of every AI decision you will make, and they point in opposite directions.
Capability rises unevenly and unpredictably. Nobody, including the labs, can tell you reliably what will be possible in eighteen months. Plans that depend on a specific future capability are bets, and should be labelled as such.
Price falls fast and predictably. This is the more useful half. At a fixed quality bar, the cost of inference has been falling by roughly an order of magnitude per year — an analysis widely cited since 2024, and one that has broadly held since. Concretely: capability comparable to the frontier models of 2023, which cost tens of dollars per million units of input text, is available in 2026 for a small fraction of that. Three forces compound to produce it: algorithmic efficiency, cheaper hardware, and aggressive competition including open-weight models.
This asymmetry — unpredictable capability, predictable price — also tells you how to sequence. Build the parts that do not depend on future capability (the data movement, the integrations, the governance) now, because they are the slow parts and they do not get cheaper on their own. Defer the parts that depend on capability you do not yet have.
1.5 The jagged frontier
The most important research finding for a manager in this field is not about what models can do. It is about the shape of what they can do.
Fabrizio Dell'Acqua and colleagues at Harvard ran a field experiment with more than seven hundred Boston Consulting Group consultants. On tasks inside the model's competence, consultants using AI produced work of substantially higher quality — up to around 40% better on some measures — and produced it faster. On a task that looked similar but sat outside the model's competence, consultants using AI performed worse than the control group without it.
The researchers named the boundary the jagged technological frontier: capability is not a straight wall with everything easy on one side and hard on the other. It is an indented coastline. Tasks that appear equally difficult to a human sit on opposite sides of it, and there is no reliable way to tell from the outside which is which.
Set that beside a second finding. Brynjolfsson, Li and Raymond studied more than five thousand customer-support agents given an AI assistant. Average productivity rose about 14%, but the distribution is the story: the largest gains, above 30%, went to the least experienced workers, while the most experienced gained little. The tool distributed the tacit knowledge of the best performers to everyone else.
Read together, the two studies give you a delegation rule:
You cannot delegate to AI by category. You can only delegate by tested task.
"Use AI for marketing" is not a decision — it is an aspiration that will straddle the frontier and produce both of the results above at once. "Use AI to produce the first draft of product descriptions, reviewed by a category manager, measured against last quarter's conversion" is a decision, and it can be evaluated.
The second consequence is subtler and matters for how you staff: because AI compresses the gap between novice and expert, the scarce skill shifts. It moves away from producing the work and towards specifying what good looks like and detecting when the output is wrong — which is judgement, and which is where Module 9 picks the thread up.
1.6 What to stop saying
A short list of phrases worth retiring from your meetings, because each hides a decision:
| Instead of | Say | Because |
|---|---|---|
| "The AI understands our contracts" | "The system retrieves the relevant clause and drafts a summary" | Names what is retrieved and what is generated |
| "We'll train it on our data" | "We'll retrieve from our documents at query time" | Different cost, different staleness, different project |
| "It learns from our corrections" | "We store corrections and feed them back as examples" | Makes the storage and its retention visible |
| "It's autonomous" | "It acts within these limits and escalates beyond them" | Turns a claim into a specification |
| "It's 95% accurate" | "95% on this test set, which was built like this" | A number without its test set is decoration |
Exercise — Explain it to a sceptic
Time: 45 minutes. Produces the artefact for this module.
Write one page explaining your organisation's main proposed AI use case to an intelligent, sceptical colleague who does not work in technology — your CFO, a clinician, a plant manager.
Constraints, each of which enforces something from this module:
- No metaphors of understanding, thinking or learning. If you need one, you have not identified the mechanism.
- Name what goes in and what comes out. Precisely. Which text, from which system, producing what.
- Say where the knowledge comes from — training, retrieval, or the context you supply.
- State where this task sits relative to the frontier, and what evidence you have for that placement.
- Name one thing that would make it fail, and what would happen next.
If you cannot complete point 5, you do not yet understand the use case well enough to fund it. That is a useful thing to discover on one page rather than in month four.
Self-check
- A colleague reports that the system "made up a customer reference number." Which property of the technology explains this, and why is "make it stop hallucinating" not an actionable instruction?
- Your team proposes fine-tuning a model on five years of support tickets so it can answer questions about current policy. What is wrong with the plan, and what would you propose instead?
- Give an example from your own work of two tasks that look equally difficult to a person but probably sit on opposite sides of the jagged frontier.
- A vendor's proposal describes an "autonomous agent." What single question tells you whether an agent is warranted?
- A use case is rejected today because inference costs five times what the process is worth. What should happen to it, and when?
Further reading
- Anthropic, Building Effective Agents, 2024 — the workflow/agent distinction and the case for simplicity.
- Fabrizio Dell'Acqua et al., Navigating the Jagged Technological Frontier, Harvard Business School Working Paper 24-013, 2023.
- Erik Brynjolfsson, Danielle Li and Lindsey R. Raymond, Generative AI at Work, NBER Working Paper 31161, 2023.
- Martin Zinkevich, Rules of Machine Learning, Google, 2016 — written for engineers, but Rules 1 to 3 are management reading.