One of the most challenging things about AI that no one talks about is not being able to talk about AI effectively. And I think that there's three main reasons for this. Number one, the tech changes faster than literally anyone can keep up with, even someone that talks about AI every day, like myself. Two, companies don't train their employees. And three, it's kind of the summation of those parts. There's a huge gap between what people know about AI and what the models are capable of and can actually accomplish. And so much of this can be solved by talking about it. But therein lies the problem. AI is a mystery wrapped up in ever-changing jargon. So we're kicking off volume two of our start here series, where we're gonna karate chop the AI jargon in the jugular and break down the basics of AI language and lingo that every business leader needs to know in 2026. All right, I'm excited. Let's get into it. Welcome to our start here series and everyday AI. So this brand new series is our essential beginner and advanced AI overviews to help you launch your year strong. So if one of your big goals is to double down or to just better learn AI, this new Start Here series is for you. All right. So if you haven't already, please go to starthearseries.com. Yeah, new URL. Uh so uh there you're gonna be forwarded straight to uh sign up page to get free access to our inner circle community. And not only will you get uh instant access to our Prime Prompt Polish Chat GPT prompt engineering course, but you will also get access to the Start Here series. So whether you're listening to this in mid-January or sometime in March, we're gonna be putting the recap of every single Start Here series um episode inside the community there, uh inside the community there, so you can listen to them all in order. All right. Uh, and if you are brand new, brand new, make sure you go listen to the first uh series of this, which was episode 691 or volume one in the start here series, which was generative AI, how it works and why it matters in 2026 more than ever. All right. If you're new, everyday AI, it's a daily live stream podcast and free daily newsletter. But I've done like 700 episodes, and the most common question I get is where do I start? That's the whole reason that we're doing this series. So let's cut the jargon down, shall we? Uh, we're gonna get straight into it. So don't worry, this isn't gonna be a super boring run through of random vocabulary words. Uh, one thing that I've realized that I kind of have a knack for uh over the years is almost being a translator, right? And uh, like literally, there is there's an instance. Um, I was working with a pretty big company, right? Doing like $20 billion in in revenue. And I was sitting with their C-suite and I was sitting with their their head of AI. And it seemed like sometimes these two sides weren't speaking the same language. And that's because there's so much jargon. And because, like I said, kind of that capabilities and understanding gap. And that's really what I've learned to do by doing this show over the last three years is connecting those two. So whether you are that highly technical person, you know, who understands all these terms, hopefully this will help you understand where the non-technical business leaders are coming from. And for our non-technical business leaders, hopefully this serves as a nice foundational look at the language and lingo you need to know to, you know, talk about it. Let's start. Start where we do. AI is not going anywhere, it's here to stay. All right. Uh, we went over that in the first episode, but it's worth repeating. ChatGPT, when it launched in November 2022, it was literally world-breaking technology. No one had ever seen anything like it before, uh, not just its capabilities, but also the sheer numbers. Uh, right, they had 100 million users within two months after launch, and ChatGPT now has nearly uh 900 million weekly active users. I think officially uh still at the 800 million weekly active users, and 40% of Americans use generative AI in just two years. Um, for comparison, it took the internet like five times as long to get that number of people actually using it. And I think honestly, ChatGPT's overwhelming popularity is one of the reasons that we have this huge capability divide, right? Do you know, as an example, you can give a single prompt to a large language model uh like Claude or uh ChatGPT, I think are probably the two best at it right now. And they can go research the web, they can uh, you know, personalize uh things for you. They can grab uh images, they can put together spreadsheets that you can actually download, PowerPoints that look really good, right? All in one prompt, right? Most people don't know that, right? Unless you listen to this show, then you probably do. Most people think AI is just a chat bot. It's not, it is something that is completing um economically valuable work at a rate higher than human experts. And recent benchmarks show that, according to blind studies. So essentially, yesterday's expert is today's beginner, and that is how quickly things change because your technical teams now are probably just spitting out things like tokens and you know, MCP and RAG and vector databases and Ralph Wiggins, right? Like it's this misunderstood jargon that just drives waste. It stalls pilots and the vocabulary shifts faster than anyone can track. To get it right, you require the right words. All right. There is a reason why this is volume two in our uh start here series. Because number one, we set the foundation. We said here is generative AI, here's why it's not going away, here's why you need to invest in it. And the next thing is you have to be able to communicate effectively about it. All right, because they require the right words. You can't evaluate vendors or manage risk alone. Uh, right. You need to bring your technical teams together with your people leading change management, you know, with your HR, with your marketing, with your sales. You all need to be able to speak the same language. Uh, and you, you know, this is the new business terms, right? Uh, you know, MCPs and and uh you know, A2As are the new KPIs. Uh, they are. Uh so you have to be able to translate AI phrases into things that move the needle for your company. This is ultimately, at least when we look at most large language models. And I'm assuming if you're listening to the show, you know, you're either using them on the front end or the back end or both. But this is all it comes down to. There's a prompt, there's an action, and there's an outcome. All right. So humans prompt a large language model. Hopefully, you're using our prime prompt polish context engineering way, right? So again, go to starthirseries.com, get free access to uh our new and updated PPP course that teaches you how to get the most out of a large language model. But it starts with the human prompting a large language model. Then the model will kind of go on with the task, uh, you know, it'll summarize, search, or draft, and the model will read the prompt inside of its context window and it works within the confines of its architecture, right? So much of the outcome is not even decided by the prompt. It's decided by you using the right model, the right mode for the right reason, for the right task, right? Uh, but essentially the model reads the prompt the human puts inside of its context window. Uh, you know, people, you need to understand things like context window. You need to understand tokens, and we're gonna be going over that today. Uh, then the model retrieves whatever data that it needs to be a helpful assistant and respond to your query, right? It's now models are agentic by nature, right? Agency, they make decisions on their own to accomplish a goal, which includes using different tools in their arsenal, uh, retrieving data on their own, you know, exploring multiple pathways and going back and saying, oh, this wasn't the right one. Um, and then they output a result. And then the humans hopefully observe what the model did, they trace uh the paths that it took, they verify the information, and then they use the outcomes. That's essentially right. If if you're like, well, how does AI even work? There you go, right? From prompt to action to outcome. And this is the foundation for every AI term out there. All right. And we did cover this last one. So this is the the 30-second uh refresher from volume one in this series. So generative AI systems, they generate something, right? Uh, whether that's text, images, code, video, music, right? Generative AI is not just chatbots. It is now everything. Uh large language models, which fall under uh, you know, kind of the generative AI umbrella, they generate responses by predicting the next word uh or token in a sequence. And they do that, you know, whether they're using uh the GPT technology, which is what a lot of today's most of today's large language models are built on top of. Uh, some of the you know, image models use diffusion technology, which is essentially they kind of fill in the dots, right? Where large language models use more kind of next uh next word or next token prediction. And most current AI products that you use, right, they're just wrapped around these other products, right? So essentially you have three big AI labs that dominate, right? You have Enthropic, you have Google, you have OpenAI and their models, Enthropic Claude, OpenAI's uh ChatGPT models, so the GPT models, and then you have the Google Gemini models. And you're like, oh wait, what about Microsoft Copilot? Uh well, they did just start making some of their own models, but for the most part, uh Copilot just uses uh the OpenAI models. They use a little bit of uh Anthropics models as well inside of their Microsoft, Microsoft Copilot 360. Uh or 365, sorry. Uh yeah, left out. That was Microsoft Xbox 360. Uh so the, you know, a lot of this other software that you use, most people don't know this, right? They're not out there creating their own models. They're not competing with OpenAI. For the most part, you know, if you're using any AI product and there's literally hundreds of thousands of AI products out there, right? Pieces of software, for the most part, they're using one of those three, probably. There's other smaller uh AI labs, but for the most part, those are the three that dominate. And essentially these models that we use, they don't technically understand our words, right? Um, the human who inputs the words, those words get translated to tokens. And the model itself, it doesn't think in words, it thinks and produces uh in tokens and then converts it back. So there's almost like a uh, you know, it's kind of like when you go into a new country, you have to convert your money. And then when you leave, you got to convert it back. It's the same thing, right? When I'm giving something to a large language model, it's can uh it's converting that to tokens, right? Which helps it truly understand what I'm trying to say because it doesn't understand words. It converts everything to tokens, right? Which is why sometimes, you know, how you communicate with a model in the same way of how you communicate with your teammates to get the most out of AI, how you communicate with the model is very important, right? Um, an example that I've given before, the word just, right? Um context matters. The word just can be tokenized by a model. Uh, just the single word just, seven different ways. The last time I checked, right? Something can be just. You can use just as a qualifier. I just want to talk. Um, right. There's like so many different meanings for words. Uh, in the same way that when you're young and you're learning whatever language that you learn, you learn, oh, different words can mean different things. And it's the words surrounding uh those words that give context and help us understand. So large language models, kind of the same thing, but uh instead of the words around, it's the tokens around. So let's talk about those tokens and context windows. This is important. Tokens are essentially text chunks, right? So they're about four characters each. So a word could be anywhere from one to, you know, uh up to a handful of tokens, and they're used to measure input and output length. So when you have a conversation with a large language model, like I said, everything gets put into tokens. And I like to think of, you know, an easy way to think about it is a hard drive, right? Um when you except let's think of a hard drive worked a different way, right? Right now, if you're trying to download a file and your hard drive's full, it just says, oh, it's full. A context window is like a hard drive. But the difference is it's automatically going to keep working. And instead of saying, hey, the context window is full, it's just gonna kick out the first thing that you put in, right? And a lot of times the first thing that you put into a large language model is the most important, right? It's saying, hey, here's the most important information. Here's what I want you to do for me. Then if you keep working with that, um, you know, keep spinning tokens back and forth with that large language model, eventually the hard drive is gonna get full. Except it's not gonna say hard drive's full, it's just gonna forget the first things you said. That's a context window. Um, and then parameters. Parameters are important to understand about large language models as well. Um, essentially, these are the neural network connections of a model. The more parameters it has, the more power, right? You can think of parameters uh kind of like horsepower of a car, uh right. There's more capability of these models that have more parameters, but there's higher computational costs in resource usage, right? So uh large, large language models, I think, are actually getting smaller. Uh, a lot of times companies don't say how many parameters there are, but you know, kind of the last widely reported uh one we knew about was the GPT-4 uh architecture from OpenAI that had about 2 trillion, uh reportedly 2 trillion parameters. So that's a lot. I've always said for a long time, large language models are going to get smaller. And in the long run, I think most people are gonna be using more small language models. We've even seen that a ton in the last week or two. Uh a lot of uh specialized models from the big companies, uh, right, for things like translation, uh, medical finance, right? The big AI labs are starting to put out very, very small models. I do think the future, uh, you know, there's gonna be, you know, open AI will have thousands or tens of thousands of models and they'll be spitting them out faster than we can even keep up with, right? Um, but anyways, parameters is capability. Now, let's talk about some dorky things. All right. And if you are a beginner, forgive me. Um, because for our more intermediate uh people or people who just need a reminder, um, we really have to understand data, right? So rag is probably a business term that you should know. And I think rag, traditional rag as we know it, is going to very much change, right? I'm not gonna say rag is going to go away, but rag is retrieval augmented generation. And that's where a model can retrieve relevant documents and then it grounds its responses using that retrieved content, right? So when, as an example, um, you know, before uh ChatGPT came out, the GPT technology was available and many businesses used it. And then they essentially uh used retrieval augmented generation uh to kind of wrap OpenAI's responses in their business data. Uh so embeddings are also something important to know. So these embeddings are it's kind of like group of data or turns uh text into vector embeddings, allowing for efficient similarity search in a vector database. All right. This one uh is a little bit more difficult to talk about, right? I'll probably uh in in the start here series uh in our community there, I'll probably put a couple graphics, uh, but it's it's a little hard to explain on a podcast without doing a deep dive, right? But essentially, text is split into smaller segments or chunks before the embeddings happen. And then the chunk size and the overlap settings control how it's done. So good chunking splits information logically. So answers include the right context and details, and bad chunking breaks up context or combines unrelated info, leading to wrong or incomplete answers. So this is pretty this is uh much more relevant for companies that are building with AP uh will building um with large language models on the back end, right? So when I say back end and front end, front end, if you're using a large language model on the front end, you're going to chat gpt.com and you're using that chat GPT interface. That's a front end user or claw.ai, right? A backend means that you maybe have a team of developers, or even now non-technical people are obviously using large language models on the back end, but you're using uh the company's API. And so essentially you're using their technology. And when you're doing that, a lot of times, then you might be working with RAG, uh, you know, these vector databases, chunking, all of that. So if you're a front-end user, you don't have to worry about that as much, but you should know what RAG is, right? RAG is what makes uh those queries uh kind of as they go off to the large language model, makes them much more accurate. It reduces the the likelihood and the prevalence of hallucinations when you are first interjecting um your company's data, your secret sauce, uh, how your company thinks, right? All that important stuff that helps new hires and uh, you know, people that have been at a company for a very long time make good decisions. It also helps large language models make good decisions. And large language models are obviously changing. Um, you know, they started as a helpful assistant in that little chat window, and there is nothing else they can really do. Now, models are agentic by nature. All right. Uh, I like to say we have our old school transformer models, and then we have our newer reasoning models, even though these reasoning models are still built for the most part on the transformer technology, the generated pre-trained transformer GVT technology, right? I like to say we had more of these, you know, old school transformer, helpful assistant chatbots. Now we have more autonomous workers, right? These models now, specifically, you know, anything from Claude in the 4.5 um family. So OBIS 4.5, Sonnet 4.5, Haiku 4.5. Um, and then with Google Gemini, all the Gemini's new models uh, you know, are hybrid or can think, right? So they can either give you that kind of next token prediction or they can think about it, right? They can be agentic in nature, or sometimes they think if they need to think about it, or they just think and they're like, all right, I'm gonna spit on an answer. And then with OpenAI's models, for the most part, uh, aside from the default one, right? But uh, you know, make sure that's why I always say if you're using uh a model, make sure you're using a model that thinks because these are models that can call tools, right? They can um decide, hey, this user is asking me about something that might be a little old in my training data or the data that the model is built on top of might be might give old or outdated or wrong answers. So an agentic model can decide I'm gonna call a tool. And it can trigger functions like search, uh, you know, going through your email, letting the uh agentic model interact with external uh services, right? You have these things called connectors, which, you know, it's kind of like rag mini, right? We're true blog meta generation, but a very simple version, uh, it used to take uh a lot of smart engineers and usually uh six, seven, eight figures to get rag. Now you can get a very simple version in a couple of clicks, you know. Most large language models on the front end call those something like connectors or apps, right? So you can connect things like your like your email, your calendar, uh, your you know, your SharePoint or your Google Drive, um, your OneDrive, things like that, Salesforce, Slack, right? And then all of that um invaluable, right? Like all of that data that your company needs and uses that you're like, man, two years ago, it was so hard to work with that. Now it's there almost automatically, right? With these connectors. You also have MCP. This is the model context protocol. Um and this is uh a technology that was first uh invented and popularized by Enthropic, but the rest of the industry has adopted it, which is great. You know, one thing about the AI industry, see like it's weird. They all kind of work together, right? So, even as an example, I was just talking about connectors. Uh, if if you're a Google organization and you use Gmail and Google Drive, you can technically use those connectors inside OpenAI's products. You can use it inside Microsoft products, inside Claude's products. So, in the same way that MCP is kind of this, it's kind of like uh um, you know, how the internet talks to, you know, websites can talk to each other with APIs. This is kind of how AI tools can talk with uh to each other with MCPs. Uh so the model context protocol is definitely the most popular one. There's a handful of other ones that are uh widely used and widely adopted. But for the most part, you know, these models have essentially languages that they can talk to each other. So you don't have to, you know, send it from an AI um system to a website. To use the website's API to go to another website to then send it to a model, right? So it's just a direct connection. The MCP connection allows different AI models to talk to each other or different AI tools. And then scaffolding. So if you've ever heard of the word scaffolding, I say it a little, I try not to, uh, just because I don't want to, you know, confuse any people. But that essentially defines the structure that agents use to chain together multiple steps or tools for more complex workflows. So, you know, uh, sometimes, honestly, like the models themselves can all be fairly similar, right? If you look at the benchmarks, they're, you know, 0.1% from you know each other. A lot of times it's the scaffolding, uh, right. It's it's how the model actually works and how it's able to successfully or unsuccessfully use all these different tools that it has at its disposal. So uh the large language models have largely gone from helpful AI assistants that were powered by older, slower models that hallucinated a lot. Now they're the models themselves are agentic by nature and they can use tools and you can connect to your business's dynamic data. But there's risks and you need to know them. Hallucinations, probably a word most people have heard of, but it's essentially a lie, uh right, or a false statement, or a half truth that's put out there very confidently, uh. But if you do know the basics of context engineering, so if you've taken our free uh prime prompt polish uh course and our free prime prompt polish, uh can't speak Prime Prompt Polish Pro course, you know the basics of context engineering and your hallucination rate is gonna go down. But if you're using the right model and if you know the basics of prompt engineering and uh sharing your company's context, hallucinations are, I'm not gonna say they're gone, but they're essentially gone, right? People overlook that. If you know what you're doing, if you're using the right model, if you're connecting in your company's data, if you're uh looking at the chain of thought, uh doing basic observability, uh, you know, human in the loop, even lazy human in the loop, hallucinations are down to about zero. Uh prompt injections, you have to look out for those, uh, especially as we have agentic browsers, right? So these are browsers that are run by an AI agent and they can go browse the web for you and interact uh with interfaces on the web with graphical interfaces, you know, click, you know, click drop downs and fill out forms for you. But there's prompt injections, but right? So there's prompt injections that get into training data, which impacts the models themselves. But on the agentic side, for agents or agentic browsers, there's prompt injections on web pages, right? And some of the earlier agents and agenc browsers didn't have great safeguards against those, right? So, you know, as an agent, right? A simple simple example, um, you know, I could put something on my website. Uh, so if an agent or an agentic browser was trying to use it and I could say, hey, you know, go uh, you know, go to this site and you know buy uh a hundred boxes of cereal, you know, put it in your Amazon cart or something like that. That's a very uh safe and happy prompt injection, right? It's it's not causing a lot of harm. I it just tricked the model uh or an agentic model into doing something that it didn't intend to, but there's obviously very harmful and unsafe uh you know prompt injections, just like there's you know, phishing emails and all these you know scams that have been going around uh you know with malicious links and all that. The same thing. Models have risks. So companies need to understand and talk about guardrails. That's when you combine uh human-made policies and filters to enforce safety and prevent misuse. All right. So this is kind of the translation playbook. All right. So in the future, we might be updating this, right? If we keep the start here series going on for a longer time. Uh so make sure I always say check the show notes of this show. So if you're listening on the podcast, we're gonna always keep the show notes updated and uh in the community in which you get free access to by going to starthearseries.com, uh, we're gonna keep the resources there updated as well. So there's always gonna be new terminology. Some of the terminology is gonna change, right? Like as an example, the definition of artificial general intelligence changes every month, right? By uh definitions from 10 years ago, we're well well past AGI, but you know, how people define it say maybe we're not there. So we're gonna keep the definitions up to uh up to date in our community. We're gonna have a little AI translation playbook, but you need to ask yourself these questions. All right. I'm gonna go back to how I started, the technical people and the non-technical business leaders. These are the questions that you need to be asking yourself out loud when it comes to using AI and understanding it and hopefully closing that capability and education gap. Number one, what's the problem we're trying to solve and what's our current costs associated with that solution? Right? People overlook that. I'm like, you know, when people are trying to, you know, calculate ROI on Gen AI, uh, right? I always ask, okay, what's your current cost on this? And they're like, okay, well, you know, uh, we have this piece of software. And no, how much time is spent? No clue. You have to understand what your current costs are. Uh, next questions what model, data, tools, and who approves? You have to go through those. Next, how can we responsibly run the fastest sprint possible with measurement and evaluation, with proper, uh, you know, proper QA? Um, you need to go fast. You have to be careful, but you have to go as quickly as possible while still being careful while you're implementing AI. Because if you're too slow and if you take a pilot slow and if you're not building modularly, right? Now all of a sudden you did a year-long pilot. Oh, wait, that original model you started with is that was the best model in the world, is now the 50th best model, and it's bad. And now you're putting yourself at a disadvantage. You can't treat AI implementation in the same way that we've treated tax uh tech implementation for the past few decades. You need to ask what are the hallucination risks, the security risks, and the costs. And then last but not least, you always need to require receipts, the observability, traceability, uh, expert-driven loops. We don't need human, uh lazy, human of the loop, uh, logs, defining the scope and getting your evaluations first. You have to understand what you're going after to be able to measure it uh and go and you know, understand the evaluations in the process. All right. So now that's it. You now have the foundation for the rest of the start here series. All right. We went over what the heck is generative AI, how do large language models work and why it's the future of work. And now you have the language and the lingo down. All right. So what I want you to do, sit down with your people. You need to get a 30-day plan. You need to be able to sprint, you need to understand how you're gonna deal with mistakes. Uh, and then later you can go into the RAG, deep dive, ROI, security scale, all this stuff. But you have to set here's where we are, here's where we want to go. Um, figure out what's gonna happen in between, but you have to keep up to date with the language and the lingo. Otherwise, your plan is gonna fall apart. All right, one way it's not gonna fall apart, go listen to episode 628, very much so related uh to this episode. So that is what's the best large language model for your team? Seven steps to evaluate and create ROI for AI. All right, I hope this was helpful. Now you know the AI without the jargon, the AI language every business leader needs to live by in 2026. All right, if this was helpful, please go to starthearseries.com. That's gonna take you and give you free access to our inner circle community, where not only can you go and check all of our Start Here series uh on the web, right? Or if on the mobile app, if that's what you want to do, uh, but you're gonna be signed up for our free daily newsletter as well. And you can go take our free prime prompt polish uh context engineering course. All right. Thank you for tuning in. I hope to see you back tomorrow and every day for more everyday AI. Thanks, y'all.