# Ch 16: Daily/weekly loop and success criteria
Creator: Nate Herk (@nateherk)
Transcript of Nate Herk's 2h33m 'Build your own AI operating system' course, split into its chapters. All content and credit: Nate Herk (@nateherk), https://x.com/nateherk/status/2101656269056610682. Transcribed locally with faster-whisper; names may be misheard.

[2:27:00] You want to build something that's super easy and it's lightweight enough that it proves yes or no. Don't waste time, don't waste money, investing into something that might not be proven yet. So prove the concept first, lightweight, cheap, build a cloud artifact, if you like it, if the concept is proven, then you can dedicate some more resources towards building a custom solution. Because honestly, what I've realized is I don't really need that much data visualization, at least in that sense, because of the fact that I can just message my assistant and I can get answers instantly. And if I ever wanna generate trends and I wanna see what's going on, I just say, hey, can you pull data from these five sources from the past month and generate me a dashboard or generate me a report? because that way I'm able to get stuff when I need it on demand, rather than having to spend time building and maintaining some sort of dashboard. All right, so now let's say we're at a really good spot. We've got a bunch of contacts, we've got a bunch of connections, we've got a ton of capabilities and cadence. What does it look like on the day to day and on the week to week? Well, first of all, obviously, trying to do as as much work as you can, just in Claude Code and not leaving and switching between different tabs and context switching. But on top of that, let's talk about the daily-daily loop. So what I would start to do is every morning, go into Claude Code and say, hey, help me plan my day. If it's helping you plan your day in a really good way, meaning it can look at your priorities and look through messages and look through your calendar, that's really good, keep doing that. But if it doesn't, note down why not. What might it be missing? What context might it need in order to plan your day better? And then at, the end of the day, look back at it. What skills did you use today? What did you a have to correct your assistant on?

[2:28:30] What did you, you know, copy and the paste in in? And then tomorrow, you can sort of patch some of that stuff up and just make small iterations as you go. Of course, you can use the audit. Maybe every single Friday you run an audit and you see what you need to do. Think about how many skills got used. Think about which ones got used daily daily. If they're getting used so often, why not just automate them. And the other thing to think about is sometimes when you actually decide I need to build an automation, it might be overkill to go with an agentic skill. What you might actually need is more Boring is Beautiful workflow automation because workflows, the Kermanistic workflows beat AI agents nine times out of 10. businesses were just automations. We barely even used AI sometimes. And hardly did we ever, fully autonomous AI down by task, you know, automate one chunk at a time. Then basically just ask Claude Code to help you build that. And then you can say, Hey, I need to push this into trigger or modal so that it can actually run 24 seven. It's really, really easy. It literally just takes that natural language in order to actually do. So let's talk about some of the success criteria that I think about when I try to understand is my AI, OS actually providing me value and is it working?

[2:30:00] And I wanted to call these KPIs, but I didn't because KPIs usually indicate that there's something objective. There's an objective metric that you're looking for. And we're not looking for really objective metrics here. We're just looking for kind of subjective success criteria. So the first thing is that your team could reach out to the AI OS, meaning ultimately it'd be great if they could just message your AI OS instead of you. Because if the AI OS knows more info than you or has better memory than you and can pull the exact source and it never sleeps, it would actually be more efficient for people to message that instead of you. And I started to realize when someone would ask me a question, I would take their question and I would just paste it into my AIOs and then paste the answer back to them. Because once again, my AIOs had more data than I did. Number two is that you stop opening new tabs. You don't have thousands of browser tabs open. You don't have thousands of desktop apps open because you're doing as much of your work as possible right from Claude Code itself. Number three is that knowledge leaves your head. So you stop having to worry so much about all these little things you have to remember. You stop having a million post-it notes everywhere. You just have all of your knowledge And, once again, just wanted to hit this one more time. This is personal.

[2:31:30] The whole point of me building this course was for your personal gain, for your personal productivity. It's great to be able to think about, okay, my whole team needs to adopt this, or I want to start teaching other people how to do this. That's great. But you have to start with yourself. You can't scale a system if you haven't lived in it yourself. You can't help your team connect to all these different data sources. If you haven't connected to them yourself. And once you've set up your own personal AI OS, your whole company can start to build around your AI OS. A company where in every operator runs a personal AI OS is a company that is truly AI ready and all the data is AI ready. Because think about it, if I didn't realize that I needed to do everything through my Google workspace, then I wouldn't have realized the benefit of having a shared drive. And I wouldn't have been able to communicate to everyone else to use GWS CLI to get all of their stuff into the shared drive and organized. And now all of us are benefiting from that. All right, so I've been standing here. Yeah. I've been to you guys for way too long now. I really hope you guys enjoyed. I hope that this gave you some structure and it gets you really excited about what you can actually do and where you can take this thing.

[2:33:00] way more hopefully, you're gonna need to really start to think about context management. So I'm gonna highly recommend you check out this video next where I talk about how to make sure you're not hitting your session limit super super quick and I'll see you guys over there. As always, thanks for making it to the end of the video and See you in the next one.