BETA This site is in beta. Information is still being added and reviewed.
Workshop overview
Deep dive. A companion to how AI works.

Which AI model you are using

The chatbot on your screen is one specific model, and most tools now offer several. The menu that says fast, or thinking, or a version number changes what the tool is good at, how long it takes, what it costs, and how much weight its answer can carry. Four differences cover nearly everything a practitioner needs. The names in that menu will keep changing every few months. These four will not.

Start activity

Audit the tool already on your screen

  1. Open the AI tool you actually use. Find the model menu and write down the exact model name and version.
  2. Find which plan you are on, and whether it is the free tier.
  3. Find the data setting: does the company say your chats are used to train the model? Fill one row per person and keep the table.

Before today, could you have answered those three questions about the tool you use every day?

The first difference

Fast models and reasoning models

Every model writes the same way, one token at a time. What differs is whether it does any work before it starts writing.

Two ways to answer

What happens after you hit send

Fast model
? A

Starts writing straight away. Fine for drafts, tone, and text you supplied yourself.

Reasoning model
? A

Writes hidden intermediate steps first, then answers. Slower, and better on rules and comparisons.

A reasoning model spends its extra time before the first word appears. The steps it shows you afterwards are its own account of the answer, and that account can leave out what actually drove it.
The default is the fast one

Unless you pick otherwise, a tool hands you a small, quick, low-cost model, because most questions do not need more. It starts writing immediately. For rewording an email, shortening a paragraph, or summarizing a document you pasted in, the speed is worth having and the quality is fine.

A reasoning model works the problem first

Models labeled reasoning or thinking write out a chain of intermediate steps before they show you anything. Working step by step measurably improves accuracy on problems that take several steps (Wei et al., 2022), which is what an eligibility rule with three conditions is, or a comparison between two documents. They are slower, sometimes by a minute, and they cost more to run.

Thinking is not checking

The steps a model shows you are not a record of how it reached the answer. Researchers planted a hint in the prompt that changed what the model answered, and the model then wrote a confident step-by-step explanation that never mentioned the hint (Turpin et al., 2023). A reasoning model makes fewer careless errors. It can still be confidently wrong, and you still verify anything you will act on.

When the wait is worth it

Use the reasoning model when a mistake would cost your client something, when the question holds more than one condition, or when you want the tool to check work instead of produce it. The fast model is enough for tone, for drafts, and for text you were going to read closely anyway.

Notice which mode you are in before you ask something that matters. A hard question handed to the fast model is how most practitioners end up with a confident, shallow answer.

The second difference

Model size and parameters

Models are described by size, usually a parameter count such as 8B, 70B, or 400B. That number is worth understanding, and so is what it leaves out.

What decides capability

Three inputs, one model

Training data Computation Parameters How capable the model is
Raise one alone and the other two waste it
Capability comes from the three together. Closed labs publish none of them, so a claim that one model is bigger or better trained than another is mostly unverifiable from outside.
Where it runs

Data center, laptop, or phone

Large, in a data centerStrongest, widest language coverage. Your text travels to the company that runs it.
Mid-size, the everyday defaultWhat most chatbots hand you first. Fast, and good enough for drafting.
Small, on your own deviceRuns offline, text stays on the machine, weakest in your clients' languages.
Size decides where a model can run, and therefore how far your text travels. The strongest models are the ones you cannot host yourself, and the ones you can host yourself are the weakest in the languages your clients speak.
A parameter is an internal dial

Training adjusts billions of internal numbers until the model's guess at the next token matches the text it is learning from. Those numbers are the parameters, and they are all the model keeps. Counting them, 8 billion or 400 billion, measures how much pattern the model has room to hold. It is not a count of facts, because the model stores none.

Data, computation, and size work together

Three inputs decide how capable a model turns out. How much text it learned from, how much computation went into training it, and how many parameters it has. Quality improves smoothly with all three, and raising one alone wastes the other two (Kaplan et al., 2020). Train a large model on too little text and a smaller model trained on more text will beat it (Hoffmann et al., 2022). Companies that sell closed models publish none of the three, so even the claim that one model is bigger than another usually cannot be checked from outside.

Large models and small models

A large language model, hundreds of billions of parameters, runs in a data center and reaches you over the internet. A small language model, a few billion parameters, runs on a laptop or a phone with no internet connection at all. Small models are cheap, fast, and private, and they are noticeably more limited. Both are built on purpose now, for different jobs.

A small model can specialize

A small model will not be good at everything. Trained further on one narrow job it can hold its own against a much larger generalist on that job, and a large model can be used to teach a small one, a method called distillation (Hinton et al., 2015). It will not generalize past its lane. Inside that lane it often does the work at a fraction of the computation and the electricity, which matters for cost and for the footprint.

Size shows up first in your clients' languages

Tokenizers cut English into few pieces and many other languages into far more, up to five times as many for the same content, so the same request costs more, runs slower, and fills the model's working memory faster in your clients' languages (Ahia et al., 2023). Shrink a model and the languages it saw least are the first to suffer. A small model that reads well in English is often visibly worse in Vietnamese, Amharic, or Haitian Creole.

Size tells you what a model can hold and where it can run. It says nothing about whether a particular answer is true.

The third difference

Open models and closed models

This one is about who holds the model and whether anyone outside the company can run it.

Two arrangements

Closed cloud and open weights

Closed model, in the company cloud

Your text goes to the company and an answer comes back. Usually the strongest models and the widest language coverage. The company sets the terms, keeps the model, and can change it without telling you.

Open weights, on hardware you control

You download the model and run it yourself. The text can stay on the machine. It costs hardware, setup, and staff time, and the models you can realistically run are smaller and weaker.

The arrangement that protects client text the most is also the one that answers worst in your clients' languages. Most agencies end up on a closed tool with a written rule about what may be typed into it.
A closed model is rented access

The best known assistants are closed. The company keeps the trained parameters, and you reach the model through its app or its programming interface. You cannot inspect it, cannot run it yourself, and cannot keep it when the company changes or retires it. The company also does not have to tell you what the model was trained on, how large it is, or what changed in the last update, and mostly it does not. Your text goes to its servers to be answered.

An open-weight model can be downloaded

Other companies publish the trained parameters, so anyone can download the model and run it on their own computer or their agency's server. This is why a laptop with no internet connection can still answer you, and why a small vendor can build a product without renting a model from anyone.

Open weights is not open source

Published weights are the finished numbers. The training data and the training code that produced them usually stay private, so nobody outside can study the model or rebuild it, and the Open Source Initiative reserves the term open source for models that release enough to do that (Open Source Initiative, 2024). Licenses differ too. Some open-weight models carry standard permissive licenses, and others carry custom terms restricting who may use them and for what. Read the license before your agency builds on one.

Where this reaches your clients

A model running on hardware your agency controls is the only arrangement in which client text never leaves the building, and that is a real reason to care about open weights. It is also easy to overstate. An app can be built on an open model and still send every word to a cloud server. Ask where the text goes, and get the answer in writing.

Open and closed is not a quality ranking, and it is not a safety ranking. It decides who can run the model and how far your text travels, which is a question about your clients before it is a question about technology.

The fourth difference

Training data and cutoff dates

Two models of the same size can behave very differently. A model is made of the text it was shown and the tuning it was given afterwards.

Training data you cannot see

These models learned from an enormous amount of web text, along with licensed and purchased material. Most closed models never publish the list, so you cannot check whether the model saw anything good on the rule you are asking about. Web text is heavily English and thin in most of your clients' languages, and the language gap starts there.

A cutoff date, and a search bolted on

Training stops on a date and the model's trained memory stops with it. Many tools now run a live web search to reach past that date, which helps and moves the question. The answer is then only as good as the pages the tool happened to pull, so ask which sources it used and open them.

A long document is not read evenly

A fact placed at the start or the end of a long input is found far more reliably than the same fact buried in the middle, and accuracy falls as the input gets longer (Liu et al., 2024). Paste a forty-page policy, ask one narrow question, and the answer can miss a paragraph the model technically read. Quote the section you care about instead of handing over the whole file.

The tuning that comes after

Once a model can predict text, people tune it with human feedback so that it follows instructions, answers in a certain tone, and refuses certain requests (Ouyang et al., 2022). That stage, and not size, is why two models feel different in conversation. It also rewards agreement. Assistants trained this way tend to match the view a user states, and they will abandon a correct answer when the user pushes back (Sharma et al., 2024). Hand the model a wrong premise and expect it to build on it.

Versions change under you

Models are retrained and updated, sometimes quietly, and the same name in the menu can point to different machinery than it did last month. Re-test a saved prompt after an update, along with the judgment you formed about what this tool gets right.

Training is the part you cannot inspect and cannot fix, and it decides how the model behaves in Vietnamese, on a county rule, and on last month's policy change. Assume it is thin exactly where your work is.

Rule of thumb

Which model for which task

What you are doing What to use Reword an email, shorten a paragraph, tidy up notes you wrote The fast default model. Speed is what you want, and you can see the input. Untangle an eligibility rule, compare two documents, check a form for contradictions A reasoning model, then verify the specifics against the official source. A local office, a deadline, a fee, a recent policy change Any model, with web search turned on, and open the sources it cites. Trained memory alone is not enough. Anything in a client's language that carries consequences A qualified interpreter or translator. No model, open or closed, large or small, replaces that. Anything holding a client's identifying information No cloud tool at all unless your agency has approved it in writing. Take the identifiers out first.
Two of these rows are not about models at all, and those two carry the most risk.
Good to know
  • The free tier of a tool is usually its lightest model. If the question is consequential, check what you are on.
  • A model labeled reasoning is not a model that checks facts.
  • Two products can run on the same underlying model and still behave differently, because the company wrapping it adds its own instructions.
  • Benchmark scores in a launch announcement are measured on tasks that are not yours, in a language that is probably not your client's.
  • An open model does not protect client data by itself. Only running it on hardware you control does, and most apps built on open models do not.
Try this

Find out which model you are on

Take five minutes and have everyone open the model menu in the AI tool they actually use, then write down the exact name and version. Now give the group one question with a rule inside it, something with an income limit and a deadline. Half the room asks the fast model, half asks the reasoning model. Read a few answers aloud. The difference in care is visible, and so is the fact that both still need checking.

Sources for this page
  1. Ahia, O., Kumar, S., Gonen, H., Kasai, J., Mortensen, D. R., Smith, N. A., & Tsvetkov, Y. (2023). Do all languages cost the same? Tokenization in the era of commercial language models. Proceedings of EMNLP 2023, 9904-9923. https://doi.org/10.18653/v1/2023.emnlp-main.614
  2. Hinton, G., Vinyals, O., & Dean, J. (2015). Distilling the knowledge in a neural network. arXiv:1503.02531. https://arxiv.org/abs/1503.02531
  3. Hoffmann, J., Borgeaud, S., Mensch, A., et al. (2022). Training compute-optimal large language models. Advances in Neural Information Processing Systems 35. https://arxiv.org/abs/2203.15556
  4. Kaplan, J., McCandlish, S., Henighan, T., et al. (2020). Scaling laws for neural language models. arXiv:2001.08361. https://arxiv.org/abs/2001.08361
  5. Liu, N. F., Lin, K., Hewitt, J., Paranjape, A., Bevilacqua, M., Petroni, F., & Liang, P. (2024). Lost in the middle: How language models use long contexts. Transactions of the Association for Computational Linguistics, 12, 157-173. https://doi.org/10.1162/tacl_a_00638
  6. Open Source Initiative. (2024). The Open Source AI Definition 1.0. https://opensource.org/ai/open-source-ai-definition
  7. Ouyang, L., Wu, J., Jiang, X., et al. (2022). Training language models to follow instructions with human feedback. Advances in Neural Information Processing Systems 35. https://arxiv.org/abs/2203.02155
  8. Sharma, M., Tong, M., Korbak, T., et al. (2024). Towards understanding sycophancy in language models. International Conference on Learning Representations (ICLR) 2024. https://arxiv.org/abs/2310.13548
  9. Turpin, M., Michael, J., Perez, E., & Bowman, S. R. (2023). Language models don't always say what they think: Unfaithful explanations in chain-of-thought prompting. Advances in Neural Information Processing Systems 36. https://arxiv.org/abs/2305.04388
  10. Vaswani, A., Shazeer, N., Parmar, N., et al. (2017). Attention is all you need. Advances in Neural Information Processing Systems 30. https://arxiv.org/abs/1706.03762
  11. Wei, J., Wang, X., Schuurmans, D., et al. (2022). Chain-of-thought prompting elicits reasoning in large language models. Advances in Neural Information Processing Systems 35. https://arxiv.org/abs/2201.11903