Elle Anderson

Field Notes · Free Guide

AI Glossary for Product Leaders.

Forty AI terms, explained in plain English for the people who have to make the call. Each one comes with an everyday comparison, the trap I see leaders fall into most and a question worth asking in your next meeting.

  • 40Terms
  • 5Chapters
  • 40Questions to Ask
  • 0Maths or Code
Showing all 40 terms
01

Foundations

The words you need before the meeting starts.

01

LLM

Also called Large Language Model, foundation model, base model

The engine under almost every AI feature you’ll be asked to sign off.

A large language model learns the patterns of language from an enormous body of text, then writes by predicting what should come next, one small piece at a time. Do that well enough and it can draft, summarise, translate and reason in plain English. Claude, GPT and Gemini are all examples, each built by a different company.

In Everyday Terms

Think of the most widely read colleague you’ve ever worked with, someone who has absorbed an enormous library and can talk fluently about almost anything in it. They’ve never lived any of it. Everything they know came from text, not experience.

The Trap I See Most

Vendor concentration is a board risk before it is a technical one. The moment your roadmap assumes one provider’s model, pricing power sits on their side of the table, so demand a switching test in the architecture from day one.

Ask This in Your Next Meeting

“Which model is this feature actually running on, and what happens to our product if that vendor changes pricing or availability overnight?”

02

Token

Also called token count, context length unit

The meter that’s always running.

Models don’t read words the way we do. They break text into small pieces called tokens, and in English a token averages roughly three-quarters of a word. Tokens set the price of every request and the limit on how much a model can take in at once.

In Everyday Terms

If a word processor charged by the character, you’d start writing differently. Tokens quietly shape how much a feature costs to run and how long a conversation can stay coherent before something gets dropped.

The Trap I See Most

Finance discovers tokens about three months after launch. Long system prompts and chat history mean you pay for the same words thousands of times a day, so the flabbiest prompt in the building quietly becomes a line item.

Ask This in Your Next Meeting

“What does this feature cost per interaction once real usage kicks in: not the demo number but the production one?”

03

Context Window

Also called context length, max tokens

Everything the model can see right now, and nothing more.

The model’s working memory for a single conversation. Your instructions, the chat so far, any documents and the reply itself all have to fit inside it. When it fills, something has to give, and the earliest material is usually the first to go.

In Everyday Terms

Picture a desk, not a filing cabinet. Everything the model is working with has to fit on the desk at once; anything that doesn’t fit gets swept onto the floor and forgotten.

The Trap I See Most

Bigger windows license lazy product design. Teams stuff everything in because they can. Quality sags in the middle of the pile and cost doubles, when curation would have beaten capacity.

Ask This in Your Next Meeting

“Does this use case need the model to hold a whole document, or a whole conversation, in mind, and does the model we’ve picked actually do that?”

04

Prompt / Prompt Engineering

Also called prompting, instructions

Better briefs, better answers. It really is that simple, and that hard.

A prompt is the brief you give the model. Prompt engineering is the craft of writing that brief so the answer comes back accurate, in the right voice and within scope, every time rather than once. A sharper brief often beats a pricier model.

In Everyday Terms

The same brief handed to two different agencies produces two different campaigns. A vague brief gets vague work back, no matter how good the agency is. Prompting works the same way.

The Trap I See Most

Prompts are product decisions dressed as text files. An unversioned prompt tweak changes behaviour for every customer overnight, which means you shipped a release with no release process.

Ask This in Your Next Meeting

“Who owns this prompt, and where is it version-controlled, so we know exactly what changed when quality shifts?”

05

Context Engineering

Also called context design, context management

Curating what the model sees, not just what you say.

The discipline that has grown up beyond prompt writing: deciding everything the model sees at the moment it answers. That includes instructions, examples, retrieved documents, memory, tool results and conversation history, all chosen and ordered to fit the context window.

In Everyday Terms

A great executive assistant doesn’t just write a good cover note. They decide which three papers go in the folder, which stay out and the order of the rest. The meeting goes well because of the folder.

The Trap I See Most

More context isn’t better context. Stuffing the window with everything you have makes answers slower, dearer and often worse, because the important signal gets buried.

Ask This in Your Next Meeting

“What exactly does the model see when it answers this customer, and who decided?”

06

Inference

Also called prediction, serving

The bit you pay for every time a customer clicks.

Training is school and inference is the job. Every time a live product sends a model a question and gets an answer back, that’s inference. Training is a large, occasional bill. Inference is a smaller bill that arrives with every single customer interaction, for as long as the feature lives.

In Everyday Terms

Training is years of medical school. Inference is every consultation afterwards. The learning happened once, but the diagnosis is worked out fresh, every single time someone walks in.

The Trap I See Most

The demo is the cheapest this feature will ever be. Growth multiplies inference cost in a straight line unless someone owns caching, batching and routing, and that someone defaults to no one.

Ask This in Your Next Meeting

“As adoption grows, is our inference cost growing in a straight line, or have we found ways to cache, batch or route to cheaper models?”

07

Reasoning Models

Also called thinking models, extended thinking

Slower, pricier and far better at hard problems.

Models built to think before they answer, spending extra time working a problem through internally. They shine on maths, code, planning and knotty analysis. They’re slower and dearer per answer, so they earn their keep only where the question deserves it.

In Everyday Terms

It’s the difference between catching a colleague in the corridor and booking an hour of their time. For most questions the corridor answer is fine. For the knotty ones you want the hour.

The Trap I See Most

Teams switch reasoning on everywhere because the demo looked brilliant, then wonder why the wait and the bill both tripled. Decide which journeys genuinely need deep thinking.

Ask This in Your Next Meeting

“Which of our use cases genuinely need a reasoning model, and what does that choice add to cost and wait time?”

02

Building the Product

Where the product decisions actually live.

08

RAG

Also called Retrieval-Augmented Generation, grounded generation

An open-book exam for your AI.

Retrieval-augmented generation looks things up before it answers. The system searches a trusted source you control, such as your policies, product documents or knowledge base, then gives the best passages to the model as its source material. It’s how an assistant can quote this morning’s price list rather than whatever it learned in training.

In Everyday Terms

The difference between an analyst who answers from memory and one who pulls the actual file before briefing you. Same question, very different confidence in the answer.

The Trap I See Most

RAG quality is content operations wearing a technical costume. The model takes the blame while stale, duplicated and contradictory documents are the actual defect, so fund the librarians before the tuning.

Ask This in Your Next Meeting

“When this feature gets something wrong, can we trace it back to a specific source document, or is it answering from thin air?”

09

Fine-Tuning

Also called model fine-tuning, task-specific training

Changing what the model is, not just what it’s told.

Fine-tuning carries on training an existing model with your own examples, so a particular style, format or specialist skill becomes second nature to it. Because it changes the model itself, it’s powerful but slow to update, costly to run well and hungry for good-quality data.

In Everyday Terms

RAG hands someone a manual to consult on the job. Fine-tuning sends them on secondment for six months, until the way they actually think has changed.

The Trap I See Most

Fine-tuning is a puppy, not a project: it arrives with retraining, eval refreshes and hosting bills forever. Teams keep buying it for problems that three good examples in the prompt would have solved.

Ask This in Your Next Meeting

“Have we exhausted what a well-written prompt and good retrieval can do, before committing budget to fine-tuning?”

10

System Prompt

Also called system message, standing instructions

The house rules your customers never get to read.

The standing brief a product team writes once and the model reads before every conversation. It sets the persona, the tone, the rules and the red lines. Customers never see it, yet it quietly decides how every answer sounds and when the AI says no.

In Everyday Terms

It’s the induction and house rules a new starter reads before their first shift: invisible to the customer, but the reason every interaction feels consistent.

The Trap I See Most

Your system prompt is the model’s employment contract with your brand. If legal and brand have never read it, your company’s voice is being set by whoever edited it last.

Ask This in Your Next Meeting

“Who signs off changes to the system prompt, and is that treated with the same rigour as a change to the product spec?”

11

AI Agent

Also called agentic AI, autonomous agent

Give it a goal and it works out the route.

An agent is handed a goal rather than a question. It plans the steps, uses tools such as search, email or your own systems, checks the results and keeps going until the job is done or it gets stuck. The prize is genuine autonomy. So is the risk.

In Everyday Terms

The gap between asking a colleague one question and handing them a brief: draft, check pricing, chase a signature, log it. One is a lookup. The other is delegation.

The Trap I See Most

Autonomy is a dial, not a feature. Every step the agent takes without asking is a step you will answer for in an incident review, so set the permission points before the demo wows the exec.

Ask This in Your Next Meeting

“At which point in this workflow does the agent stop and ask permission, and what happens if it fails halfway through?”

12

Multimodal AI

Also called vision-language models, audio-language models

Show it, say it or type it.

Multimodal models take in more than text. They can look at a photo, read a scanned form, listen to a voice note or watch a short clip, then reason across all of it together. For product teams it opens up journeys that start with a picture or a conversation instead of a form.

In Everyday Terms

Earlier AI assistants were pen pals: text in, text out. Multimodal models are closer to a colleague sitting next to you, glancing at what’s actually on your screen.

The Trap I See Most

Every new modality multiplies your failure surface and your eval bill. Images and audio bring privacy, accessibility and moderation duties that text never had, and they are rarely priced into the business case.

Ask This in Your Next Meeting

“Would this feature genuinely improve if it could see what the customer sees, or are we adding modality because it’s available, not because it’s needed?”

13

MCP

Also called Model Context Protocol, tool protocol

Build the connection once and reuse it everywhere.

Model Context Protocol is an open standard, first published by Anthropic, for connecting AI applications to tools and data. Build one connection to the standard and any compatible AI app can use it, instead of a separate integration for every model and every tool.

In Everyday Terms

Before universal chargers, every device needed its own cable. MCP is the equivalent for AI integrations: one connector standard, many devices.

The Trap I See Most

Connectors are quiet security decisions. Each one extends what the model can read and do, so review the connector list like production access, not like a plugin store.

Ask This in Your Next Meeting

“Which of our existing systems already have an MCP-compatible connector, and how much integration work does that actually save us?”

14

Open-Weight vs Closed Models

Also called open source models, proprietary models

Rent the best or own the model.

Closed models are used through a provider’s service, and you never see inside them. Open-weight models publish the trained model itself, so you can run it on your own infrastructure, adapt it and keep data in-house. The trade is control against convenience and, often, raw capability.

In Everyday Terms

Leasing a car versus buying one. The lease is newer, maintained for you and easy to swap. The car you own goes wherever you like, and every repair is yours.

The Trap I See Most

Open isn’t free. Hosting, security, upgrades and evals all land on your team, and the licence may still restrict commercial use. Read it before the architecture is set.

Ask This in Your Next Meeting

“Do our data, cost and control needs justify running our own model, and who will look after it?”

15

Embeddings

Also called vector representations, semantic vectors

A map where meaning, not spelling, decides who sits together.

An embedding turns a piece of content into a long list of numbers that work like coordinates on a map of meaning. Things that mean similar things land close together, so “cancel my plan” sits right beside “end my subscription” even though they share no words.

In Everyday Terms

Imagine every customer review you’ve ever read, plotted on a map by theme, so every "delivery was late" complaint clusters together regardless of how each customer phrased it. Embeddings build that map automatically.

The Trap I See Most

Embedding choices fossilise. Switch models later and every stored vector needs regenerating, so the cheap decision made in week one becomes a migration programme in year two.

Ask This in Your Next Meeting

“When a customer searches and gets nothing back, is that a real content gap, or is our embedding model simply missing the connection?”

16

Vector Database

Also called vector store, embedding store

Search by meaning, at speed.

A database designed to store embeddings and find the nearest ones fast. Ask it a question and it returns the passages closest in meaning, which is why it sits underneath most RAG systems and most good semantic search.

In Everyday Terms

A normal database is a filing cabinet: you need the exact label to find the folder. A vector database is closer to a colleague who’s read everything and points you to what’s actually relevant, even when you didn’t use quite the right words.

The Trap I See Most

Teams procure vector infrastructure before proving retrieval value. For many products a boring database you already run would have done the job, so demand the evidence before buying the shelving.

Ask This in Your Next Meeting

“What happens to search quality as our content library grows tenfold? Have we tested that, or just launched it?”

17

Synthetic Data

Also called generated data, simulated data

Made-up data, used carefully.

Data generated to stand in for real data or to add to it, often created by an AI model. It’s useful for testing, for rare edge cases and where real records are too sensitive to use. It’s only ever as good as the assumptions behind it.

In Everyday Terms

A flight simulator. Pilots train for engine failures they’d never want to rehearse for real. The simulator is invaluable, as long as nobody mistakes it for the sky.

The Trap I See Most

Models trained heavily on generated data can drift towards blandness and lose the rare cases that matter most. Keep a set of real examples aside as your ground truth.

Ask This in Your Next Meeting

“Where are we using synthetic data, and how do we know it reflects our real customers?”

18

Structured Outputs & Tool Calling

Also called function calling, JSON mode, schemas

Where AI stops talking and starts doing, safely.

Structured outputs make a model reply in a fixed, machine-readable format, such as a form with named fields, so other software can rely on it. Tool calling lets the model ask your systems to do something specific, like raise a ticket or look up an order, with every input checked before anything runs.

In Everyday Terms

A brilliant new hire who stops sending you rambling emails and starts filling in the actual form, every field, every time. Same brain, suddenly usable by the rest of the machine.

The Trap I See Most

Demos run on prose; production runs on schemas. Until outputs are validated against a contract, every downstream system is parsing vibes, and the first wrong-shaped reply finds your billing pipeline.

Ask This in Your Next Meeting

“Which of our AI features still pass free text between systems, and what happens downstream when it arrives wrong-shaped?”

19

Latency

Also called response time, time to first token, streaming

Every second of waiting is a design decision.

The pause between a customer asking and the answer appearing. In AI products it’s a three-way trade between speed, quality and cost, because bigger models and longer thinking take time. Streaming the words as they’re written makes the wait feel shorter even when it isn’t.

In Everyday Terms

The espresso bar versus the pour-over counter. Both make coffee; only one suits the morning rush. Choosing the brew method to match the queue is the job.

The Trap I See Most

Latency is a pricing decision in disguise. Teams pick the model that shone in the demo, then meet the late-afternoon traffic, and the fix (a smaller model or a shorter chain) was available all along.

Ask This in Your Next Meeting

“What response time does this moment in the journey actually need, and what is the cheapest model tier that meets it?”

03

Where It Breaks

The risk register, in plain English.

20

Hallucination

Also called confabulation, model error

Fluent, confident and wrong.

When a model states something untrue with complete confidence: a made-up figure, a policy that doesn’t exist or a reference to a paper nobody wrote. It isn’t lying. It’s doing what it was built to do, producing likely-sounding text, without any built-in sense of what’s true.

In Everyday Terms

A sharp colleague who’d rather improvise a convincing answer than admit they don’t know, and delivers the improvisation with exactly the same confidence as the truth.

The Trap I See Most

The costly hallucinations are the plausible ones. Nobody acts on the absurd errors; they act on the believable ones, so design your review for plausibility, not absurdity.

Ask This in Your Next Meeting

“If this feature hallucinates in front of a customer tomorrow, what’s the actual damage: inconvenience or something we’d have to disclose?”

21

Hallucination Rate

Also called factual error rate, grounding score

The honest number behind “it’s usually right”.

How often a model’s answers contain something invented or incorrect, usually measured against a set of questions with known answers, by people, by another model or both. There’s no universal safe number. What’s acceptable for a gift idea is reckless for a medicine dose.

In Everyday Terms

A colleague who’s right 98% of the time sounds excellent, until you realise the 2% is indistinguishable from the 98%, and it’s reaching customers unfiltered.

The Trap I See Most

A single accuracy number hides who pays. Two per cent wrong spread evenly is one product; two per cent concentrated on your highest-value segment is a very different product with the same score.

Ask This in Your Next Meeting

“What’s our acceptable error rate for this specific feature? Did we set that number before launch, or are we discovering it after?”

22

Bias

Also called algorithmic bias, model bias, training bias

Yesterday’s patterns, repeated at scale.

A consistent tilt in a model’s answers that favours some people, groups or ideas over others. It comes from the data the model learned from, which reflects the world’s history and habits, and it can quietly turn one unfair pattern into thousands of decisions.

In Everyday Terms

If every customer interview your team ever ran happened at one flagship store, your "customer insight" would carry that store’s biases without anyone noticing. A model trained on skewed data has the same blind spot, just harder to see.

The Trap I See Most

Bias findings arrive as headlines, not as tickets. The eval that would have caught it costs thousands; the headline costs the brand, and regulators read the headlines too.

Ask This in Your Next Meeting

“Have we tested this feature across the demographics and use cases that aren’t in the room when we decide it’s ready?”

23

Model Drift

Also called data drift, distribution shift, concept drift

Nothing broke. It just quietly got worse.

Over time the world changes and a model’s answers slowly lose their edge, because customers, products, prices and language move on while the model stays as it was. Drift rarely announces itself. You’ll only see it if you keep measuring.

In Everyday Terms

A pricing model built on last year’s market doesn’t stop giving confident answers when the market shifts. It just keeps confidently giving the wrong ones.

The Trap I See Most

Drift hides inside healthy dashboards, because usage holds while quality slides. Book the quarterly re-eval into the roadmap now; nobody volunteers for maintenance later.

Ask This in Your Next Meeting

“Who is watching this feature’s quality six months after launch, not just in the week we shipped it?”

24

Prompt Injection

Also called prompt hijacking, adversarial prompting

When the document starts giving the orders.

An attack that hides instructions inside content the AI is asked to read, such as an email, a web page or an uploaded file. If the model treats those hidden words as commands, it can leak data or take actions its owner never intended.

In Everyday Terms

It’s a social-engineering call to your helpdesk, except the "caller" is a paragraph buried inside a PDF the AI was simply asked to summarise.

The Trap I See Most

Any feature that reads untrusted content is taking instructions from strangers. If the AI can both read the outside world and act on your systems, you have built an open window next to the safe.

Ask This in Your Next Meeting

“If this feature reads content we don’t control (emails, uploads, the open web), has anyone actually tried to break it?”

25

Data Leakage

Also called sensitive data exposure, PII leakage

When a helpful answer gives away too much.

Private or confidential information ending up somewhere it shouldn’t: pasted into a public chatbot, shown to the wrong user by an assistant or swept into the data used to train a model. With AI, the leak often comes from a helpful answer rather than a hack.

In Everyday Terms

A keen new starter who’s been handed the keys to every filing cabinet and wants to please. Ask the right question and they’ll cheerfully read out a colleague’s salary.

The Trap I See Most

Your AI assistant inherits every permission mistake already sitting in your shared drives. Fix access before you switch it on, not after the first awkward screenshot.

Ask This in Your Next Meeting

“Can this assistant see anything a given user shouldn’t, and how have we tested that?”

26

Guardrails

Also called safety filters, content filters, output constraints

Lane markings for your AI.

The checks around a model that keep its output safe and on brief: topic limits, content filters, privacy masking and policy rules. They won’t make a model wiser. They make it fit to put in front of your customers.

In Everyday Terms

A cycle lane doesn’t make the rider faster or better. It just makes sure everyone on the road knows where they’re allowed to be.

The Trap I See Most

Your funniest customer stress-tests the guardrails within a week of launch. Overblocking legitimate users does more quiet revenue damage than the rare bad output the rails were bought to stop.

Ask This in Your Next Meeting

“What actually happens when a guardrail fires? Does the customer get a helpful redirect, or a dead end that erodes trust in the whole product?”

27

Red-Teaming

Also called adversarial testing, jailbreak testing

Break it yourself before someone else does.

Inviting skilled people to attack your AI on purpose before launch. They try to make it leak data, break its rules, say something harmful or embarrass the brand. Every weakness they find is one a customer, a journalist or a criminal won’t.

In Everyday Terms

Hiring a locksmith to break into your house before you move the valuables in. Far cheaper to learn about the weak window from someone on your own payroll.

The Trap I See Most

Your customers will red-team you for free within days of launch, and they publish their findings on social media. The internal version costs a workshop; the external version costs the brand, and screenshots never expire.

Ask This in Your Next Meeting

“Who has seriously tried to break this feature before launch, and what did we change because of what they found?”

04

Proving It Works

The evidence that turns opinion into a decision.

28

Evals

Also called evaluation framework, LLM evaluation

Proof, not vibes.

Evaluations are repeatable tests for AI quality. A good set checks answers for accuracy, tone, safety and completeness, and runs automatically whenever a prompt, a model or the data changes. They turn “it seems better” into evidence.

In Everyday Terms

Ordinary QA checks whether the button works. Evals check whether what the AI said was actually true, sensible and safe, at scale, without a human reading every single output.

The Trap I See Most

An eval nobody updates is a mirror of last year’s product. Feed it real logged failures every month, or you are measuring your ability to pass your own old test.

Ask This in Your Next Meeting

“If we swapped the underlying model tomorrow, would we know within an hour if quality had dropped, or would we hear it from complaints?”

29

Grounding & Citations

Also called source attribution, grounded answers

Every claim, with its receipt.

Grounding ties an answer to specific sources, such as your documents or a search result, rather than the model’s general memory. Citations show the reader which source supports which claim, so they can check it in a single click.

In Everyday Terms

A good analyst’s report has footnotes. You might never read them, but you trust the report more because you could.

The Trap I See Most

A citation proves a source was retrieved, not that it says what the answer claims. Test that the quotes genuinely match, or the footnotes become decoration.

Ask This in Your Next Meeting

“When the assistant cites a source, how often does that source actually support the claim?”

30

Precision & Recall

Also called positive predictive value, sensitivity

Choose which mistake hurts less.

Two ways of scoring a model that flags things. Precision asks how many of its flags were right. Recall asks how many of the real cases it found. Turn one up and the other usually comes down, so the real decision is which mistake costs you more.

In Everyday Terms

A smoke alarm tuned to catch every fire will also go off every time you make toast. Tune it to ignore the toast, and it might miss a genuine but small fire. No setting is right for every kitchen.

The Trap I See Most

Whoever sets the threshold sets the P&L. This is a commercial trade-off wearing a statistics costume, and it belongs in the product review, not buried in a data science notebook.

Ask This in Your Next Meeting

“For this feature, is a missed case or a false alarm the more expensive mistake, and have we actually tuned for that?”

31

Benchmarks

Also called leaderboards, model scores

Good for a shortlist, never for a decision.

Standard public tests used to compare models on things like reasoning, coding, maths and general knowledge. They’re handy for a first shortlist. They tell you very little about how a model will handle your customers, your data and your edge cases.

In Everyday Terms

Exam results on a CV. They’ll get someone an interview. They won’t tell you how that person handles your toughest client on a Friday afternoon.

The Trap I See Most

Popular benchmarks leak into training data, so scores can flatter. Build a small benchmark from your own real cases and trust it more than any leaderboard.

Ask This in Your Next Meeting

“How does this model score on our own test set, rather than the vendor’s slide?”

32

Chain-of-Thought

Also called CoT, step-by-step reasoning

Show your working.

Asking a model to work through a problem step by step before giving its answer. Like showing your working in a maths exam, it tends to improve accuracy on harder questions. It costs more time and tokens, and the steps shown aren’t always a faithful record of how the answer was really reached.

In Everyday Terms

The teacher who insisted you show your working wasn’t just making marking easier. Writing the steps out catches your own mistakes before you hand the answer in.

The Trap I See Most

Visible reasoning reads as confidence and audits as theatre. The steps shown are not guaranteed to be the real computation, so do not sell explainability to a regulator on the back of it.

Ask This in Your Next Meeting

“Is the extra latency and cost of stepwise reasoning earning its keep here, or is this a task simple enough not to need it?”

33

Temperature

Also called randomness, creativity setting

Steady or surprising: you choose.

A dial that controls how adventurous a model is when choosing its next words. Turn it down for consistent, predictable answers, such as pulling data from forms. Turn it up for variety and fresh ideas, accepting that it will stray further from the obvious.

In Everyday Terms

It’s the difference between briefing someone to "stick to the script" versus "have some fun with it". Both are valid instructions, just for very different jobs.

The Trap I See Most

Teams demo at one temperature and ship at another. Lock the setting per use case and write it down, or support will spend weeks chasing bugs that are just dice rolls.

Ask This in Your Next Meeting

“Does this feature need to be identical every time, or is some variation actually part of what we’re offering?”

34

Zero-Shot & Few-Shot Prompting

Also called zero-shot inference, in-context learning

A good example beats a long explanation.

Zero-shot means giving the model an instruction and nothing else. Few-shot means adding a handful of examples of exactly what good looks like. Two or three well-chosen examples often fix tone or format faster than any amount of extra instruction.

In Everyday Terms

Zero-shot is asking someone to write a client email with no reference. Few-shot is showing them three you’ve actually sent and saying "that voice, please". The examples do most of the teaching.

The Trap I See Most

Your examples are silent policy. The three samples pasted into the prompt define tone and edge cases more than the spec does, and nobody reviews them after week one.

Ask This in Your Next Meeting

“Before we escalate this to an engineering fix, has anyone simply tried adding two or three good examples to the prompt?”

05

The Board Conversation

Framing AI for governance, money and law.

35

Human-in-the-Loop

Also called HITL, human review, human oversight

The AI drafts. A person decides.

A person checks, edits or approves the AI’s work before it reaches the real world. It isn’t simply on or off. You might review every output, a random sample or only the ones the system is unsure about, and the right level depends on the harm a mistake could cause.

In Everyday Terms

It’s tracked changes on a document the AI drafted: the model does the first pass, a person decides what actually goes out. Speed from the machine, judgement from the human.

The Trap I See Most

Review queues rot into rubber stamps. When the human approves 99 per cent of outputs, attention dies exactly where the risk lives, so measure reviewer disagreement, not reviewer throughput.

Ask This in Your Next Meeting

“What’s the cost of a wrong AI output reaching a customer unreviewed, and does that justify the review step we’ve built, or skipped?”

36

Shadow AI

Also called unsanctioned AI, bring your own AI

Your people are already using AI. The question is where.

AI tools used across the organisation without approval or oversight, usually by well-meaning people trying to work faster. It brings real productivity and real risk, from confidential data in free tools to decisions nobody can explain afterwards.

In Everyday Terms

Shadow IT all over again, only faster. A banned tool doesn’t remove the need. It just moves the work somewhere you can’t see.

The Trap I See Most

Banning AI rarely works. Giving people a safe, approved tool that’s genuinely good brings the work back into the light.

Ask This in Your Next Meeting

“Which AI tools are our teams actually using today, and what are we offering them instead?”

37

Deterministic vs Probabilistic

Also called rule-based vs statistical

Why AI can’t be tested like the rest of your software.

Ordinary software is deterministic: give it the same input and you’ll get the same output, every time. AI is probabilistic: it makes a well-informed guess, so the same question can produce different answers, and a wrong answer can look exactly like a right one.

In Everyday Terms

A calculator is deterministic: two plus two is always four. A forecaster is probabilistic: tomorrow’s prediction is the best guess based on the pattern, and tomorrow is still allowed to surprise you.

The Trap I See Most

The org chart stays deterministic even when the product does not. QA, legal and support all assume repeatable behaviour, so the change programme is for them, not just the codebase.

Ask This in Your Next Meeting

“Are we still testing this feature with a pass/fail mindset built for deterministic software, or have we actually adapted QA for something that behaves like a forecast?”

38

EU AI Act

Also called AI regulation, risk-based AI rules

Rules that follow the risk, not the technology.

The European Union’s law on artificial intelligence, which sorts AI uses by risk. A few uses are banned outright, high-risk uses such as hiring or credit decisions carry strict duties and many everyday tools need transparency. It applies to anyone offering AI in the EU market, wherever they’re based, and its duties are phasing in over several years.

In Everyday Terms

Like product safety law, it cares less about how a thing is built and more about what could go wrong once it’s in people’s hands. A toy and a pacemaker face very different checks.

The Trap I See Most

Legal often learns about the hiring screener after it’s live. Keep a simple register of every AI use case and its risk level, and you’ll answer the regulator’s first question in minutes.

Ask This in Your Next Meeting

“Which of our AI features would count as high risk, and who owns that list?”

39

LLMOps

Also called AI observability, ML operations for LLMs

Keeping a live AI feature healthy, week after week.

The day-to-day running of AI features in production. It covers logging requests and answers, watching cost and speed, running evals continuously, managing prompt versions and spotting quality slipping before customers notice.

In Everyday Terms

Standard operations tools tell you if the server’s down. LLMOps tells you if the AI has quietly started giving worse answers, costing more than expected or failing in ways nobody’s flagged yet.

The Trap I See Most

The tooling is the easy purchase; the rota is the hard one. Someone must own model quality on a Tuesday in month nine, and if that name is not written down, you bought dashboards, not operations.

Ask This in Your Next Meeting

“If quality on this feature degraded 15% over the next month, would we see it on a dashboard, or find out from a support queue?”

40

Model Routing & Unit Economics

Also called model cascades, right-sizing, cost per interaction

Where AI features make money or lose it.

Routing sends each request to the smallest model that can handle it well, saving the big, expensive models for the hard cases. Unit economics means knowing what each interaction costs and earns. Together they decide whether an AI feature grows your margin or eats it.

In Everyday Terms

A triage nurse. Most cases are handled at the desk, a few go through to the consultant, and nobody sends a paper cut to surgery. The expensive time is protected for the work only the expensive time can do.

The Trap I See Most

One model for everything is the most expensive sentence in AI product. Routing routinely halves serving cost without customers noticing, and if nobody can quote your cost per interaction, the margin surprise arrives with the invoice.

Ask This in Your Next Meeting

“What does one interaction cost on this feature today, and which slice of the traffic genuinely needs the expensive model?”

Nothing matches that just yet. Try a shorter word, or ask me on live chat and I’ll happily add it.

Forty questions that make you the most useful person in the room.

Meeting Mode strips the guide back to the questions alone. Keep it open on a second screen, or copy the lot into your notes.

01Foundations

  1. LLMWhich model is this feature actually running on, and what happens to our product if that vendor changes pricing or availability overnight?
  2. TokenWhat does this feature cost per interaction once real usage kicks in: not the demo number but the production one?
  3. Context WindowDoes this use case need the model to hold a whole document, or a whole conversation, in mind, and does the model we’ve picked actually do that?
  4. Prompt / Prompt EngineeringWho owns this prompt, and where is it version-controlled, so we know exactly what changed when quality shifts?
  5. Context EngineeringWhat exactly does the model see when it answers this customer, and who decided?
  6. InferenceAs adoption grows, is our inference cost growing in a straight line, or have we found ways to cache, batch or route to cheaper models?
  7. Reasoning ModelsWhich of our use cases genuinely need a reasoning model, and what does that choice add to cost and wait time?

02Building the Product

  1. RAGWhen this feature gets something wrong, can we trace it back to a specific source document, or is it answering from thin air?
  2. Fine-TuningHave we exhausted what a well-written prompt and good retrieval can do, before committing budget to fine-tuning?
  3. System PromptWho signs off changes to the system prompt, and is that treated with the same rigour as a change to the product spec?
  4. AI AgentAt which point in this workflow does the agent stop and ask permission, and what happens if it fails halfway through?
  5. Multimodal AIWould this feature genuinely improve if it could see what the customer sees, or are we adding modality because it’s available, not because it’s needed?
  6. MCPWhich of our existing systems already have an MCP-compatible connector, and how much integration work does that actually save us?
  7. Open-Weight vs Closed ModelsDo our data, cost and control needs justify running our own model, and who will look after it?
  8. EmbeddingsWhen a customer searches and gets nothing back, is that a real content gap, or is our embedding model simply missing the connection?
  9. Vector DatabaseWhat happens to search quality as our content library grows tenfold? Have we tested that, or just launched it?
  10. Synthetic DataWhere are we using synthetic data, and how do we know it reflects our real customers?
  11. Structured Outputs & Tool CallingWhich of our AI features still pass free text between systems, and what happens downstream when it arrives wrong-shaped?
  12. LatencyWhat response time does this moment in the journey actually need, and what is the cheapest model tier that meets it?

03Where It Breaks

  1. HallucinationIf this feature hallucinates in front of a customer tomorrow, what’s the actual damage: inconvenience or something we’d have to disclose?
  2. Hallucination RateWhat’s our acceptable error rate for this specific feature? Did we set that number before launch, or are we discovering it after?
  3. BiasHave we tested this feature across the demographics and use cases that aren’t in the room when we decide it’s ready?
  4. Model DriftWho is watching this feature’s quality six months after launch, not just in the week we shipped it?
  5. Prompt InjectionIf this feature reads content we don’t control (emails, uploads, the open web), has anyone actually tried to break it?
  6. Data LeakageCan this assistant see anything a given user shouldn’t, and how have we tested that?
  7. GuardrailsWhat actually happens when a guardrail fires? Does the customer get a helpful redirect, or a dead end that erodes trust in the whole product?
  8. Red-TeamingWho has seriously tried to break this feature before launch, and what did we change because of what they found?

04Proving It Works

  1. EvalsIf we swapped the underlying model tomorrow, would we know within an hour if quality had dropped, or would we hear it from complaints?
  2. Grounding & CitationsWhen the assistant cites a source, how often does that source actually support the claim?
  3. Precision & RecallFor this feature, is a missed case or a false alarm the more expensive mistake, and have we actually tuned for that?
  4. BenchmarksHow does this model score on our own test set, rather than the vendor’s slide?
  5. Chain-of-ThoughtIs the extra latency and cost of stepwise reasoning earning its keep here, or is this a task simple enough not to need it?
  6. TemperatureDoes this feature need to be identical every time, or is some variation actually part of what we’re offering?
  7. Zero-Shot & Few-Shot PromptingBefore we escalate this to an engineering fix, has anyone simply tried adding two or three good examples to the prompt?

05The Board Conversation

  1. Human-in-the-LoopWhat’s the cost of a wrong AI output reaching a customer unreviewed, and does that justify the review step we’ve built, or skipped?
  2. Shadow AIWhich AI tools are our teams actually using today, and what are we offering them instead?
  3. Deterministic vs ProbabilisticAre we still testing this feature with a pass/fail mindset built for deterministic software, or have we actually adapted QA for something that behaves like a forecast?
  4. EU AI ActWhich of our AI features would count as high risk, and who owns that list?
  5. LLMOpsIf quality on this feature degraded 15% over the next month, would we see it on a dashboard, or find out from a support queue?
  6. Model Routing & Unit EconomicsWhat does one interaction cost on this feature today, and which slice of the traffic genuinely needs the expensive model?

Want This Landed in Your Team?

I help senior leaders turn AI from a slide into a product decision, with the evidence, guardrails and economics to back it. If that sounds useful, I’d love a chat.

Book a Consultation

© 2026 Mrs Elle Anderson. Share freely with credit, not for sale or adaptation, under CC BY-NC-ND 4.0. More Free Tools