Your AI Isn’t Dumb. It’s Missing Context.

Look, if you want the model to come up with the best insights possible based on whatever it is you're doing with that particular client, whatever kind of job you are, blah, blah, blah.

You need to make sure that there's a lot of things that are well defined when you're passing things off to a model.

Because a lot of people are asking things to a model, but they're asking in a way where there's a lot of things that are ambiguous.

And instead of the model being able to give really good feedback, it gives something that's more generic, right? And Peter McCarroll was fantastic when he was talking about what are the things that he does in his own business that creates that kind of separation.

And it's a context document, right? It's the, it's not just, you know, you're not just giving him the what, but you're giving the why.

You're building that out.

And in the example that we have here, we are a, you know, because you have to, you know, when we sat down and we talked about how we're going to be putting this episode together, there's a few things that you actually have to think about.

You have to think about who you are as a business.

So what it is you do as a business in order to properly put those things together and who's your client, because you need to, right.

You have to, those things need to get built out.

Now we're going to do a quick disclaimer here and that, you know, and in a lot of those professional settings, a lot of that information is going to be spread across different, uh, different buckets, whether it's a CRM, whether it's ticketing, whether it's ticketing, whether it's, you know, sometimes the CRM and the ticketing are bunched together in a lot of different instances.

But it's going to be ticketing, it's going to be CRM, it's going to be if they if they if they're using a specific product of yours, it's going to be details of usage details, it's going to be.

So in this specific instance, we are a cloud provider for storage.

So I want to give, you know, just give you guys context, right.

But you could do this with any business.

That's the beauty of this.

Right.

So, you know, we sat there, we spitballed and we, we just got to this cause you know, it's very straightforward where we're supplying storage to a business now, you know,

so, and, and, you know, the, If we want to step back and kind of think of why is so genius and is you know the moment when when Peter mentioned, this is because.

we've been doing this since we've been using Ai every time we build a project, meaning myself and Peter and hopefully most people that are that are building.

You know, the term was context engineering.

And, you know, one of the reasons why Peter hates the word vibe coding based on how products are built to production and not just the vibes.

Obviously, it has its place, but it was so far from how we started building probably what summer of last year is when we stopped maybe even sooner.

Because we realized the proper context allowed us to build out something that could go to production.

Specking it out, giving proper direction.