
In-Ear Insights from Trust Insights
In-Ear Insights: The Non-Techie’s Journey to Local AI
In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss how you will cut energy waste by shifting to local AI. You’ll discover how to structure your planning so you track tools after defining your goals. You’ll learn how to build a self-updating memory system that keeps every project organized without extra effort. You’ll walk away with a clear checklist to audit your routine and select the exact technology you need. 00:00 – Introduction 03:15 – The trap of picking platforms first 08:42 – Building a self-updating AI memory system 14:30 – Replacing heavy tools with simple scripts 21:05 – Balancing cost and environmental impact 27:50 – Call to action Press play now to uncover the practical strategies that will transform how you handle technology. Watch the video here: Can’t see anything? Watch it on YouTube here . Listen to the audio here: https://traffic.libsyn.com/inearinsights/tipodcast-the-journey-to-local-ai.mp3 Download the MP3 audio here . Need help with your company’s data and analytics? Let us know! Join our free Slack group for marketers interested in analytics! [podcastsponsor] Machine-Generated Transcript What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode. Christopher S. Penn: In this week’s In-Ear Insights, let’s talk about local AI and the reasons and, well, the implementation of it. We’ve talked in the past, and you’ve seen in the Trust Insights newsletter and on LinkedIn and all the places we post, about how local AI is one of the ways that you can reduce the environmental impact of generative AI by doing things on computers under your control, either on your literal laptop or maybe specialized desktop devices like the Nvidia DGX Spark. But either way, you don’t need a massive hyperscaler data center that vacuums up entire rivers and electrical power grids just to write email summaries. Katie, you’ve been on this journey for a bit now. What have you found and where are things going for you? Katie Robbert: It’s been interesting so far. One of the goals that I had when I started this journey was to document everything so I could share it in the Inbox Insights newsletter, which you can subscribe to at TrustInsights.ai/newsletter. Each week I plan on going through basically the big things that I’ve learned, which to be honest, is a lot. One of the first things that became very clear to me is that I was breaking my own rules when it came to the 5P framework by Trust Insights. And so if you’re not aware, you can go to trustinsights.ai/5p-framework. The 5Ps are purpose, people, process, platform, and performance. And so in this journey to understand what it looks like to migrate to local AI, I was leading with the platform. I was doing what we highly recommend everybody not do. And I was doing it. And I want to be very clear, and I want to call myself out because it’s such an easy trap to fall into. We’re like, oh, I should move to local AI because it’s going to be greener, it’s going to save the environment, it’s going to do this or that. I already chose the platform. I already chose the solution before really exploring the other P’s. And so, acknowledging that—I didn’t realize it until I was about partway through creating the first set of requirements. When I looked at it and said, I started with the platform. What am I doing? This is ridiculous. So all to say, this is why we talk about the 5P framework the way that we do. So where I started was with a user story. As a persona, I want to say that a user story is a simple three-part sentence: As the CEO and an environmentally conscious citizen, I want to figure out where I am negatively impacting the environment with my use of AI without losing productivity, so that I can feel good about the work that I’m doing. Kind of convoluted in my writing, it’s a little bit more clean, but that’s the gist of what I was trying to get. I don’t want to lose productivity, and I want to do better for bigger than my own little ecosystem. What I found out is it’s not an all-or-nothing. It’s not just migrate everything to local AI and you’ll be fine. I had to really dig in. So the first thing I did, aside from setting up the projects and the folders and all that good organizational stuff, was Chris. I borrowed your scaffolding from the Data Diaries, which is in the Inbox Insights newsletter, and you talked about the product requirements document. You talked about the technical specifications and you talked about the work plan, and you gave prompts for those. So as a user, I borrowed those and adapted what I needed to because I wasn’t coding; I was creating something different. And one of the things that you did in that prompt that was really helpful in the product requirements document was you gave the instruction to the AI that says, interview me until you have enough information. That’s where I’ve been spending most of my time. Because there are about twenty questions. The questions that came out were ones that I overconfidently thought I knew the answers to. And then when I really stepped back to think about it, they weren’t the case at all. For example, moving to local AI is going to be more environmentally sustainable. That might be the case. However, based on the nature of the work that I do in my process, that’s not the best move for me. And it’s something that I need to really consider. And one of the things that came up, and this is where I want to get your thoughts, Chris, is I rely really heavily on the memory that you can create within a project, specifically in something like Claude Desktop Co:Work. And then you have the projects, and you can actually commit information to memory to reference later. This is not true of every functionality of every iteration of every large language model. But this is something that I specifically use because one of the things that I’m trying to do is remember back in January, we had this great idea that we said we were going to do and then it died. And now it’s August, almost September. What are we going to do about it? I’m able now to go through lots of different files from different systems. Basically one of the good, solid use cases of generative AI is summarization and categorization of the data. So it’s not making decisions for me, but it’s taking everything from Slack, from transcriptions, from emails, from wherever—all these different places—and saying, I’ve summarized everything; here’s all the stuff. And I’m like, that’s amazing. Let’s commit that to memory so that tomorrow when I’m like, hey, let’s do this thing over here, it’s like, remember yesterday? Because I don’t remember yesterday, but the machine does. So that for me is such a big use case. And where I got blocked on my journey to local AI is how often the memory on the local version gets updated with things that are happening near real time. I want to kind of get your thoughts on that, so I’ll just stop there. That’s one of the learnings that I’ve had so far. Christopher S. Penn: Memory is writing things down, and that’s essentially one of the core functions that a lot of people don’t do with AI. Then they figure out, oh, these tools have no memory, and you constantly reinvent the wheel. And so there are a bunch of technical solutions for that when you’re using local AI that you can create. In fact, you can create a better memory with local AI than you can with the cloud-based ones because the cloud-based ones have pretty strict limitations in terms of how many resources you’re allowed to consume when you’re on your laptop. You can do whatever you want. There are some things you should not do, but the system will let you do them. So that’s one of those sort of bookmarks that you’d want to mentally say, okay, well what are the different options? In fact, Google just had a paper on this from DeepMind three days ago. Essentially instead of having things loaded in a project, you have your local tool create—in whatever folder you’re working—have it write a wiki with links to markdown files within itself. As you make changes to the project, it updates the wiki because it can traverse it and say, okay, I’m on the homepage of the wiki. And now I’m in Katie’s projects. And now I’m in Katie’s dog projects. And now I’m in Katie’s fence, the backyard project. It can keep just drilling down as though it were a person browsing a wiki until it gets to, oh, on August 26th, Katie decided we’re not going to fence the backyard with an electric fence. We’re going to use an old-fashioned vinyl fence for that. And the advantage of that kind of system is that it’s very human-readable so that you can browse your own wiki and go, I said that. Katie Robbert: And that’s what I’m doing with the cloud-based version right now. So the question for me as I’m making these decisions is what does my process of maintenance look like to make sure that the local version is staying as up to date as possible, since things are happening every single day that I’m trying to remember? I’m one person. And one of the things that I’ve been sort of thinking about is, I’m one person, one laptop, one project. What does this look like at an enterprise level when they’re trying to do something similar without getting too far into the weeds of that? Right now, a big consideration I have is, yes, I can create that on a local environment. How often am I keeping it up to date, and is that taking more time and more resources to do that than it is to do it in the cloud? And again, these are questions that you probably know the answers to, but I, as the person who’s trying to learn, don’t yet know what that looks like. And so for me, that’s been an incredibly helpful exercise because here’s the thing, I have a Chris Penn. I can ask Chris Penn questions all day long, but not everyone has access to a technical expert on their team to just ask questions. So they’re just kind of winging it and hoping for the best. And so I’m trying to really remove you, Chris, as a crutch of like, well, Chris will. Chris can tell me the answer. Chris can tell me the best way to do this. Yes, I have that safety net, but at the same time, I need to be able to figure it out on my own without you saying, do it this way. Like what you just shared with me about the wiki that hasn’t come up at all during my planning. Christopher S. Penn: And this is where, and we talked about this in previous episodes of the podcast, being well-read and looking at those edge cases and digging around in places you don’t normally read is so important because you will get vocabulary that you didn’t have previously. For example, when I’m working in Claude Code, there’s this concept in all the AI coding tools called hooks. And a hook is an automatic function that fires at a certain point in the system. So there are hooks for when you start a session, there are hooks when you run a compaction, and there are hooks when you complete an action. And one of the things that is in my Claude Code is I use not a wiki, but I use a knowledge graph. In mine, I have a hook that says post-task hook, update the graph. So I don’t have to remember to update my knowledge graph. I don’t have to remember to update the wiki. The system is built into the system to say, hey, I just finished a task; I better update the knowledge graph so that the next time I look at this, it’s fresh. So part of those requirements would be to say, yeah, the system has to maintain itself. I don’t want to be doing that. The system had better do it for me. Katie Robbert: But in your example, so you’ve completed a task, what about those external documents, that external context, that external data? Is that part of what gets updated into it? Christopher S. Penn: Yeah, you have to take notes to say, hey, you’re going to take notes and put the notes in the notes folder wherever your notes folder is in your project, and it will update its notes and say, okay, hey, today it looks like Katie had to nag Chris again about updating his expense reports. And then in the next day’s notes, Katie has to nag Chris again. Day 71. Chris still hasn’t done his expense reports, but it’s in the journal. If we take away all the technical language, it really is just journaling. It’s like every project has a journal, and the AI is responsible for doing the journaling. Katie Robbert: Okay, all right, offline I’m going to ask you more questions about that. But one of the other big learnings, and this I think was really eye-opening to me but also kind of like a duh moment—which I’m a little embarrassed about, but I’m sharing it because I’m trying to be transparent and accountable—is that a lot of what I’m trying to do and where I think I’m saving resources and environmental impact has nothing to do with AI. I’m using AI to do things that can be done with a script. So for example, I’ve built an App Script into a Google Sheet that pulled from a different API. Like, I’ve built it, I now know how they work. Maybe it wasn’t the most efficient thing, but it worked because I was brand new to it. And we were on a call with a client a couple of weeks ago where the person was sharing this entire process and it was very copy-paste heavy. There was a lot of moving pieces in spreadsheets. And you, Chris, sat back and said, have you looked at the VBA scripts? Do you have access to that? And they were like, well, I think we do. And you’re like, yeah, you just need a script for that. And for me, like the light bulb—if you could see it go off above my head—I was like, oh, damn. Yep, there’s a lot there that I’m doing that doesn’t need AI to be doing it. And that has nothing to do with cloud-based or local. It has everything to do with being aware of the kind of work that you are doing repeatedly and what is the best solution for it. That for me was one of the biggest learnings in going through this requirements-gathering process, which is why we always stress doing the requirements before you start building anything. So Chris, I’m aware of the App Script and the VBA scripts in Excel, but what are some of the other examples of scripts that people who aren’t overly technical can build and aren’t using? Christopher S. Penn: If you’re doing this on your computer, which presumably a lot of people are, your computer—whether it’s Windows or Mac—has a command line, a terminal, and in that terminal you can install Assoft Corporate. It allows you lots of little extra utilities. And these utilities are free and open source. Many of them are proven; many have been around forever. And one of the things that I do, which is actually part of my project setup, whenever I set up a project on my computer, this text file goes in it and lists all those utilities that I have installed on my specific computer. So this is not universal to everybody. A lot of these things you would have to install. But this is, hey, AI, don’t invent. If you’re working on a task and I tell you, hey, we need a database, don’t write one from scratch. Here’s a long list of everything that’s already installed on this computer so you don’t have to reinvent the wheel. And these are really like one level up from scripts. These are apps, right? These are text-based apps like FFmpeg, which is an incredible video editing tool. Another one is yt-dlp for downloading YouTube videos and captions. Another one on here is SQLite Local Database, right? Which is, by the way, once you get started. Doing the wiki thing is a really important tool because it’s an actual database. Pandoc is for converting data from one form to another. There are all these different tools that I have installed on my machine. They’re all free and they’re not right for everybody because you’d want to ask maybe your existing system, hey, for this project, what free open-source command-line applications are the best fit so you don’t have to reinvent the wheel. There are thousands of these things. There’s another one here: ImageMagick. I use this one all the time. Whenever you see my You Ask, You Answer videos on YouTube, all those title cards are programmatically generated by ImageMagick and a Python script. I’m not going to sit there manually typing out every show title. That’s ridiculous. I give the show titles to the script. The script just has a template, fills in the template with text, and spits out 10 or 20 image files at a time. This is where you will find a lot of extra savings. Another one that’s super important for Trust Insights is the Google Workspace command-line tool. Right. So Claude or ChatGPT whoever can use a terminal script to talk to Google Sheets, Google Docs, and Google Slides without having to reinvent the wheel or use an MCP, which is very resource-intensive and very token-intensive. When there’s a command-line tool that says, hey, here’s how to update a Google Doc, that one is one of my workhorses. I can say, when John sends over a proposal or scope of work, okay Claude, you’re going to use the GWS CLI to read this doc and here’s my criteria for how I want you to review it. It will now add comments to this doc, redline this, or whatever, and it’s all built into that tool. Zero tokens, zero AI because it’s just a command-line tool. Katie Robbert: This breaks my heart because I fought learning command lines for so long, and yet if I’m really committed to reducing my use of AI where it’s not appropriate, then I really do have to learn them. And so I will go on record and say I’m going to start exploring the command-line apps that make the most sense for me based on the work that I’m doing, which is what is coming out of my requirements gathering. And so I have a very strong use case where I had the methodology clear and I was generating report after report about more than a dozen of them. They were all identical, just with different data inputs. And then I had to change something in every single one of those reports, and I regenerated them again. And when I was doing the requirements, it very clearly flagged that should have been a script. Why are you using AI for that? And it’s just… For me, it was just my lack of education around what was possible. But now I’m looking at everything that I do and I’m like, could that be a script? Could that be a script? Could that be a script? Could that be a script? And that is the third category of how to save on AI use that I wasn’t expecting. I was looking at it very binary: local or cloud. And that was it. And now there’s this whole other category that I’m like, well, that just changes the game altogether. Christopher S. Penn: This is something I wrote about on LinkedIn not too long ago. One of the best uses of AI is to make tools, scripts, or applications so that you don’t have to use AI at all, because these tools are the best coders in the world. And as long as you’re good at following the SDLC, you can say, we’re going to make this piece of software, and then I’m going to install it on my machine and then I’m going to use it.





