Fundamentals

This page sets the vocabulary the rest of the playbook builds on: what AI, machine learning, and generative AI actually mean, how they relate to each other, and how to tell them apart from automation and analytics - two things people frequently confuse them with.

AI, Machine Learning, and Generative AI

These four terms nest inside each other. Getting the nesting right avoids two common mistakes: calling a rule-based script "AI," and treating "AI" and "generative AI" as synonyms.

  • Artificial Intelligence (AI) - the umbrella term for any system that performs a task normally associated with human judgement: recognising a pattern, making a prediction, understanding language, or planning a sequence of actions. This includes machine learning, but also older, non-learning approaches such as rule-based expert systems and search/planning algorithms.
  • Machine Learning (ML) - a subset of AI where the system learns its logic from data instead of being explicitly programmed with rules. This covers classification, regression, clustering, and forecasting models, and it is the foundation both traditional data science and generative AI are built on.
  • Deep Learning - a subset of ML that uses multi-layer neural networks to learn from large datasets, which is what makes image recognition, speech, and language modelling work at all.
  • Generative AI - a subset of deep learning where the model learns to produce new content (text, code, images, audio) rather than just a label or a number. Large language models (LLMs) are the generative AI systems most relevant to this playbook.

AI versus machine learning versus deep learning versus generative AI, each a subset of the one before it

Every generative AI system is deep learning, every deep learning system is machine learning, and every machine learning system is AI - but the reverse is not true at any level. A deterministic pricing engine built from if/then rules is sometimes marketed as "AI." It isn't; it's automation, covered below.

AI vs Traditional Automation vs Traditional Analytics

Three terms get used interchangeably in scoping conversations and shouldn't be: automation, analytics, and AI answer different questions and fail in different ways.

DimensionTraditional AutomationTraditional Analytics / BIAI
Logic sourceHand-coded rules (if/then, workflows, RPA scripts)Fixed queries and aggregations over historical dataPatterns learned from data (statistical or model-based)
Question answered"Do X when Y happens""What happened, and how much?""What is likely to happen" or "what does this mean"
DeterminismFully deterministic - same input, same output, every timeDeterministic - same query, same resultProbabilistic - same input can produce a different output
Handles unseen inputNo - breaks or misfires on cases outside the coded rulesNo - only describes what's already in the dataYes, within limits - generalises, at the cost of occasional errors
Time orientationPresent - reacts to a triggerBackward-looking - reports on what already occurredForward-looking (predict) or generative (synthesise new content)
Typical failure modeRule doesn't cover an edge case; silent wrong branch or hard crashRight numbers, wrong or stale questionHallucination, drift, biased or overconfident inference
Best fitStable, well-defined, high-volume repetitive tasksReporting, trend analysis, dashboardsAmbiguous input, language understanding, pattern recognition, prediction

The practical rule: if you can write the complete decision logic as a flowchart today, that's automation, not AI. If you're aggregating and displaying data that already exists, that's analytics. AI earns its place when the input is too varied, too unstructured, or too uncertain for either of those to work.

Benefits, Limitations, and Misconceptions

This is the honest version, meant for scoping conversations rather than pitch decks. Three things in order: what AI genuinely adds over rule-based systems and fixed queries, the constraints that have to be designed around up front rather than discovered in production, and the assumptions that most often derail a project before it starts.

Benefits

  • Handles unstructured input - free text, scanned PDFs, images - that rule-based systems and fixed queries cannot process
  • Generalises beyond explicitly programmed cases, at the cost of occasional error
  • Removes repetitive cognitive work (reading, extracting, summarising, first-draft writing) rather than just repetitive keystrokes
  • Makes tacit, hard-to-document expertise reusable once a model or prompt is well tuned

Limitations

Be honest about these in scoping conversations

Every limitation below is a design constraint, not a reason to avoid AI. Plan for them up front rather than discovering them in production.

  • Hallucination - generative models produce fluent, plausible, and sometimes entirely false output, with no built-in signal that anything is wrong. Retrieval grounding and citation reduce this; nothing eliminates it.
  • Non-determinism - the same prompt or input can produce a different output on different runs. This breaks the assumption of reproducible, unit-testable behaviour that most engineers rely on.
  • Cost that scales with usage - generative AI is billed per token, on both input and output, so cost grows with prompt size, context length, and call volume rather than being fixed at build time. See Tokens for the mechanics.
  • Evaluation overhead - there is no compiler-equivalent correctness check for a generated paragraph or a model's prediction. You need labelled evaluation sets, human review loops, and ongoing monitoring, and that overhead persists after launch, not just during build.
  • Data dependency - output quality is capped by the data the model was trained or grounded on. Poor source data produces confidently wrong output, not an error.
  • Limited explainability - some model classes are difficult to justify to auditors or regulators, and an LLM's stated reasoning can be a post-hoc rationalisation rather than the actual basis for its output.

Misconceptions

  • "AI replaces the data platform." It doesn't. A model or an agent is only as good as the data foundation underneath it - ingestion, modelling, quality - and building AI on a weak foundation just automates the production of bad answers faster.
  • "More AI is a better outcome." The mechanism has to match the problem shape. Using an LLM to forecast a number a regression model would predict more accurately, cheaply, and reproducibly is a worse solution, not a more advanced one.
  • "AI can be tested like normal code." Deterministic unit tests don't apply to non-deterministic output. You need evaluation harnesses with acceptance thresholds, not pass/fail asserts.
  • "One model fits every use case." Model selection and routing matter - a small, cheap model handles classification and extraction well; save the largest, most expensive model for tasks that need deep reasoning.
  • "AI understands the request." A language model predicts a likely continuation given its training and context - it doesn't have goals, common sense in the human sense, or accountability for the outcome. Human review stays in the loop for consequential decisions.

Key Takeaways

  • AI is the umbrella term; machine learning is a subset of AI; generative AI is a subset of machine learning. Not everything marketed as "AI" is even machine learning.
  • AI is not automation and not analytics. Automation runs fixed rules on defined triggers; analytics describes historical data; AI infers patterns from data and generalises to new input.
  • The real limitations - hallucination, non-determinism, token-driven cost, evaluation overhead - are design constraints to plan around, not reasons to avoid the technology.

Next: Core Concepts - with the terms straight, the core concepts are the parts every AI solution is built from.