WEBVTT 00:00:06.219 --> 00:00:08.679 You know the feeling? At 8 in the morning, your 00:00:08.679 --> 00:00:10.660 day looks clean, calm and perfectly arranged. 00:00:10.919 --> 00:00:13.140 By noon, it looks like someone picked up your 00:00:13.140 --> 00:00:16.100 calendar, shook it like a snow globe and put 00:00:16.100 --> 00:00:19.539 the pieces back down wherever they landed. You 00:00:19.539 --> 00:00:21.679 promised yourself that you would protect a long 00:00:21.679 --> 00:00:24.879 focus block. You were sure that you would send 00:00:24.879 --> 00:00:28.859 those six important emails. You were even going 00:00:28.859 --> 00:00:32.619 to squeeze in a quick workout. Then what teams 00:00:32.619 --> 00:00:36.049 happened? Microsoft Teams. Then slack happened. 00:00:36.869 --> 00:00:40.869 A meeting got moved. An urgent email arrived 00:00:40.869 --> 00:00:42.909 with six question marks in the subject line. 00:00:43.869 --> 00:00:47.469 By lunch, your beautiful plan had become a museum 00:00:47.469 --> 00:00:50.729 piece from a timeline that never even existed. 00:00:50.969 --> 00:00:54.450 Well, today I want to fix that tiny AI agents 00:00:54.450 --> 00:00:58.250 that make daily planning simple enough to do 00:00:58.250 --> 00:01:02.229 and sturdy enough to survive contact with reality. 00:01:03.280 --> 00:01:06.420 We're not going to build a grand system or even 00:01:06.420 --> 00:01:08.620 a perfect template that takes an hour to maintain. 00:01:09.200 --> 00:01:13.140 We're going to build a few small helpers that 00:01:13.140 --> 00:01:17.079 capture what is on your mind, help you choose 00:01:17.079 --> 00:01:20.579 what actually matters, place those tasks onto 00:01:20.579 --> 00:01:23.819 your calendar with sensible buffers, and then 00:01:23.819 --> 00:01:27.060 close the loop with a two -minute evening reflection 00:01:27.060 --> 00:01:32.079 so that the tomorrow that you have Benefits from 00:01:32.079 --> 00:01:35.980 what you learned today. Welcome to Data and AI 00:01:35.980 --> 00:01:38.680 with Mukundan, where you learn AI by building. 00:01:39.659 --> 00:01:43.700 I'm Mukundan. Each week, we build a real -life 00:01:43.700 --> 00:01:46.459 problem and ship a practical workflow that you 00:01:46.459 --> 00:01:49.540 can copy tonight. This episode is a build -along. 00:01:50.260 --> 00:01:53.579 By the end of it, you will have a notion -based 00:01:53.579 --> 00:01:57.680 OS that uses three simple, small agents for capture, 00:01:57.900 --> 00:02:01.959 prioritization, and timeboxing. You can add an 00:02:01.959 --> 00:02:05.379 optional micro agent for evening reflection Now 00:02:05.379 --> 00:02:07.659 if you want more power, I will also walk you 00:02:07.659 --> 00:02:12.620 through cross device capture on iOS or Android 00:02:12.620 --> 00:02:16.419 and With a calendar orchestration that respects 00:02:16.419 --> 00:02:20.879 your deep work time a weekly review agent That 00:02:20.879 --> 00:02:24.159 clears open loops and a tiny metrics dashboard 00:02:24.159 --> 00:02:27.719 That keeps you honest without turning your life 00:02:27.719 --> 00:02:32.590 into a spreadsheet to start We should agree on 00:02:32.590 --> 00:02:37.469 what an AI agent really is. An agent is not a 00:02:37.469 --> 00:02:40.830 chatbot that simply answers questions. An agent 00:02:40.830 --> 00:02:44.289 plans steps, remembers context, and adapts when 00:02:44.289 --> 00:02:47.569 you give it feedback. If a tool only does one 00:02:47.569 --> 00:02:50.870 of those things, it is just a script. Scripts 00:02:50.870 --> 00:02:54.550 are useful, but they are brittle. The moment 00:02:54.550 --> 00:02:57.930 your day changes, the script breaks, and you 00:02:57.930 --> 00:03:00.750 have to manually fix the mess. We are going to 00:03:00.750 --> 00:03:03.830 build agents that propose sensible actions, ask 00:03:03.830 --> 00:03:05.610 for your approval before they write anything 00:03:05.610 --> 00:03:09.710 to your system, and then learn over time which 00:03:09.710 --> 00:03:14.050 choices you prefer. This is what makes a routine 00:03:14.050 --> 00:03:17.930 stick when life gets loud. Let me describe the 00:03:17.930 --> 00:03:20.629 stack. We will use Notion for lists and Google 00:03:20.629 --> 00:03:24.629 Calendar for time. We will create three agents. 00:03:25.349 --> 00:03:29.110 The first agent captures anything you throw at 00:03:29.110 --> 00:03:32.840 it. within 30 seconds and routes it to the right 00:03:32.840 --> 00:03:36.560 place. The second agent looks at the pool of 00:03:36.560 --> 00:03:39.020 things that you could do today and helps you 00:03:39.020 --> 00:03:42.379 choose a small realistic set that you can finish 00:03:42.379 --> 00:03:46.539 today. The third agent places those chosen tasks 00:03:46.539 --> 00:03:50.620 on your calendar in three clear blocks with buffers 00:03:50.620 --> 00:03:53.680 and it gives you a 60 second kickoff ritual that 00:03:53.680 --> 00:03:55.860 helps you start instead of thinking about starting. 00:03:56.419 --> 00:03:59.199 At the end of the day, a tiny reflection agent 00:03:59.979 --> 00:04:03.080 Ask you about your wins, your misses and one 00:04:03.080 --> 00:04:05.800 improvement for tomorrow. That is the entire 00:04:05.800 --> 00:04:09.599 system. It is light, it is quick and it is sturdy. 00:04:09.819 --> 00:04:14.099 Let's build the capture agent first. Your brain 00:04:14.099 --> 00:04:17.779 is not supposed to store everything. It is supposed 00:04:17.779 --> 00:04:21.160 to decide. The capture agent gives you one simple 00:04:21.160 --> 00:04:25.519 input on any device. You open the input, type 00:04:25.519 --> 00:04:30.100 what you want to remember and press send. The 00:04:30.100 --> 00:04:33.259 agent examines what you wrote and decides whether 00:04:33.259 --> 00:04:37.899 it is a task, an event or just an idea. If there 00:04:37.899 --> 00:04:42.079 is a date in the text, it extracts it. If there 00:04:42.079 --> 00:04:45.160 is a link, it fetches the title so that you can 00:04:45.160 --> 00:04:49.040 recognize it later. It then proposes a destination. 00:04:50.439 --> 00:04:53.439 You get a preview of what will be saved and you 00:04:53.439 --> 00:04:57.019 approve the move. The agent then logs the time. 00:04:57.480 --> 00:05:00.579 the source and the original text so that you 00:05:00.579 --> 00:05:03.639 can always trace what happened if the agent is 00:05:03.639 --> 00:05:07.360 unsure it keeps them in your inbox with a small 00:05:07.360 --> 00:05:10.379 needs review tag so that you can decide later 00:05:10.379 --> 00:05:14.600 the important thing is that you can get something 00:05:14.600 --> 00:05:18.019 out of your head and into the system in under 00:05:18.019 --> 00:05:22.480 half a minute that speed is what makes you actually 00:05:22.480 --> 00:05:26.339 use it when your day is messy well now that you 00:05:26.339 --> 00:05:29.350 have a place to put everything you need a weight 00:05:29.350 --> 00:05:32.790 to decide what deserves your attention today 00:05:32.790 --> 00:05:36.209 this is where the prioritizer agent helps the 00:05:36.209 --> 00:05:38.569 agent looks at the tasks that are due soon the 00:05:38.569 --> 00:05:42.009 goals you already care about and anything that 00:05:42.009 --> 00:05:44.529 you're marked as important it gives each task 00:05:44.529 --> 00:05:48.550 a simple urgency score and a simple effort estimate 00:05:48.550 --> 00:05:53.529 then it proposes a today list that only includes 00:05:53.529 --> 00:05:58.209 three tasks The list is short on purpose because 00:05:58.209 --> 00:06:00.750 when you try to do 8 or 9 things, you usually 00:06:00.750 --> 00:06:05.129 finish none of them and go to bed feeling like 00:06:05.129 --> 00:06:09.009 you failed. But when you choose 3, you finish 00:06:09.009 --> 00:06:11.670 most days with a clean slate and a quiet mind. 00:06:12.490 --> 00:06:15.550 If you try to add a fourth task, the agent asks 00:06:15.550 --> 00:06:18.870 which one you want to remove. It records the 00:06:18.870 --> 00:06:21.410 trade so that your future self does not wonder. 00:06:21.870 --> 00:06:24.129 why half your day disappeared the result is a 00:06:24.129 --> 00:06:26.649 today list that fits into the day you actually 00:06:26.649 --> 00:06:31.990 have not the day you wish you had now once you 00:06:31.990 --> 00:06:35.589 have your three tasks the time box agent turns 00:06:35.589 --> 00:06:38.730 them into a schedule that you can follow the 00:06:38.730 --> 00:06:42.069 agent proposes three blocks the first is a morning 00:06:42.069 --> 00:06:45.850 block which is a morning deep work block that 00:06:45.850 --> 00:06:49.910 lasts 90 to 120 minutes so an hour and a half 00:06:49.910 --> 00:06:52.959 to two hours The second block is an afternoon 00:06:52.959 --> 00:06:56.699 administrator block that lasts 45 minutes to 00:06:56.699 --> 00:06:59.939 90 minutes. The final block is a small buffer 00:06:59.939 --> 00:07:03.220 near the end of your day for spillovers and cleanup. 00:07:04.199 --> 00:07:07.560 Between blocks, the agent keeps 10 minute margins 00:07:07.560 --> 00:07:11.319 so that you can breathe, stand up and transition. 00:07:12.500 --> 00:07:16.000 Before each block begins, the agent gives you 00:07:16.000 --> 00:07:19.360 a 60 second kickoff. You read the task out loud. 00:07:20.000 --> 00:07:23.019 You define what done means for this block in 00:07:23.019 --> 00:07:26.660 one simple sentence. You open the exact file 00:07:26.660 --> 00:07:30.240 or link you need. You start a 25 minute timer 00:07:30.240 --> 00:07:34.899 and then you type the first sentence. Those five 00:07:34.899 --> 00:07:38.100 steps, they may sound small, but they slam the 00:07:38.100 --> 00:07:42.220 door shut on delay and drift. They are the difference 00:07:42.220 --> 00:07:44.980 between thinking about the work and actually 00:07:44.980 --> 00:07:48.579 doing the work. And AI agents specifically are 00:07:48.579 --> 00:07:51.860 only helpful when they are trustworthy. So we 00:07:51.860 --> 00:07:55.000 give them guardrails. The agents always ask before 00:07:55.000 --> 00:07:58.899 they move, edit or schedule anything. They show 00:07:58.899 --> 00:08:01.040 you what will change before they make the change. 00:08:01.899 --> 00:08:05.500 If something fails to parse, they do not guess 00:08:05.500 --> 00:08:09.740 wildly. They show you a small form with their 00:08:09.740 --> 00:08:13.660 best attempt and ask you to confirm. They log 00:08:13.660 --> 00:08:18.189 what they did. when they did it and why. If you 00:08:18.189 --> 00:08:20.410 ever needed to audit, the record is right there. 00:08:21.370 --> 00:08:24.269 When privacy matters, they keep sensitive text 00:08:24.269 --> 00:08:27.250 out of the log and store it locally or in a safe 00:08:27.250 --> 00:08:31.430 field. These small choices, they create a feeling 00:08:31.430 --> 00:08:34.330 that you can trust. Because when you trust your 00:08:34.330 --> 00:08:36.950 tools, you actually use them. To make sure the 00:08:36.950 --> 00:08:40.110 day closes well, we add the evening reflection 00:08:40.110 --> 00:08:44.690 microagent. After dinner, you spend two minutes 00:08:44.690 --> 00:08:47.809 with the prompt. You list three wins, two misses, 00:08:47.870 --> 00:08:51.529 and one improvement. The agent pulls entries 00:08:51.529 --> 00:08:54.789 from your calendar and your today list to help 00:08:54.789 --> 00:08:59.009 you remember the details. You write short, honest 00:08:59.009 --> 00:09:02.210 sentences. You're not making a diary. You're 00:09:02.210 --> 00:09:04.230 just building a bridge from today to tomorrow. 00:09:04.769 --> 00:09:07.549 And this small loop keeps the system alive because 00:09:07.549 --> 00:09:10.309 you adjust it based on what is real, not what 00:09:10.309 --> 00:09:13.779 you hoped would happen. Now, let's walk through 00:09:13.779 --> 00:09:16.080 a live example so that you can hear how it feels. 00:09:17.580 --> 00:09:21.600 Imagine it is a Monday. You plan to finish your 00:09:21.600 --> 00:09:26.120 Q3 deck. You want to reply to six emails that 00:09:26.120 --> 00:09:29.179 matter. You also want to draft a job application. 00:09:29.960 --> 00:09:32.799 Here you open the capture input and dump the 00:09:32.799 --> 00:09:36.340 three items. The capture agent classifies them 00:09:36.340 --> 00:09:40.850 as tasks, eliminates the... Estimates the effort 00:09:40.850 --> 00:09:44.509 and proposes destinations. You approve in seconds. 00:09:44.750 --> 00:09:47.590 The prioritizer notices that the deck has a higher 00:09:47.590 --> 00:09:52.049 urgency because of a looming review. It notices 00:09:52.049 --> 00:09:55.009 that the job application is important but medium 00:09:55.009 --> 00:09:57.570 effort. It notices that the emails are a small 00:09:57.570 --> 00:10:01.450 chunk of work that helps other people move. It 00:10:01.450 --> 00:10:05.470 proposes your today list. Finish the deck, reply 00:10:05.470 --> 00:10:10.090 to those emails and draft the application. And 00:10:10.090 --> 00:10:13.090 you accept. The Timebox agent creates three blocks. 00:10:14.029 --> 00:10:16.990 It places the deck in the morning deep work block. 00:10:17.769 --> 00:10:20.730 It places email and the start of the application 00:10:20.730 --> 00:10:24.370 in the afternoon admin block. It keeps a small 00:10:24.370 --> 00:10:26.809 buffer in the late afternoon in case anything 00:10:26.809 --> 00:10:30.389 runs long. Now, when the first block begins, 00:10:30.629 --> 00:10:34.009 the kickoff prompt appears. You read the task 00:10:34.009 --> 00:10:37.450 out loud. You define done for this block. You 00:10:37.450 --> 00:10:40.740 open the deck. and you set a timer type one sentence 00:10:40.740 --> 00:10:44.879 that forces you to start that is it the rest 00:10:44.879 --> 00:10:48.419 of the day unfolds with fewer decisions and less 00:10:48.419 --> 00:10:51.120 friction now that you have the core routine let's 00:10:51.120 --> 00:10:53.860 extend it so that it works across every device 00:10:53.860 --> 00:10:56.559 you use if capture only works on your laptop 00:10:56.559 --> 00:10:59.279 the system will fail the minute you leave your 00:10:59.279 --> 00:11:03.580 desk on ios you can create a simple shortcut 00:11:03.580 --> 00:11:07.090 called quick inbox When you run it, the phone 00:11:07.090 --> 00:11:10.009 asks you for a line of text. If the line includes 00:11:10.009 --> 00:11:12.610 a link, the shortcut fetches the page title. 00:11:13.529 --> 00:11:16.909 It packs the details into a tiny payload with 00:11:16.909 --> 00:11:20.070 a timestamp and the word iOS as the source. Then 00:11:20.070 --> 00:11:23.470 it sends the payload to your Notion inbox via 00:11:23.470 --> 00:11:27.889 a webhook or to a special email address that 00:11:27.889 --> 00:11:31.210 forwards into Notion. The phone buzzes with a 00:11:31.210 --> 00:11:34.700 small captured message. and a tap of haptic feedback 00:11:34.700 --> 00:11:37.700 so that your brain knows that the item is safe. 00:11:37.879 --> 00:11:40.980 On Android, you can use the share sheet and a 00:11:40.980 --> 00:11:44.779 lightweight HTTP request app. When you share 00:11:44.779 --> 00:11:48.019 any text or link to Quick Inbox, the app sends 00:11:48.019 --> 00:11:51.659 the same payload to your webhook. If you're somewhere 00:11:51.659 --> 00:11:55.679 without good app support, you can set up a unique 00:11:55.679 --> 00:11:59.340 email address like inbox at your domain and forwards 00:11:59.340 --> 00:12:02.740 to your Notion worker. The subject becomes the 00:12:02.740 --> 00:12:06.539 title. The body becomes the raw text. If you 00:12:06.539 --> 00:12:09.879 attach a file, the system stores a link to it. 00:12:10.919 --> 00:12:14.000 The system stores a link to it. The capture agent 00:12:14.000 --> 00:12:16.059 will classify and route everything the next time 00:12:16.059 --> 00:12:19.360 it runs. The entire point is that capture is 00:12:19.360 --> 00:12:22.279 always one gesture away, whether you're walking, 00:12:22.480 --> 00:12:27.019 commuting, or waiting in line for coffee. Scheduling 00:12:27.019 --> 00:12:30.549 deserves a small upgrade too. Time boxing collapses 00:12:30.549 --> 00:12:35.730 when meetings collide. The calendar orchestration 00:12:35.730 --> 00:12:38.970 piece teaches your agent to negotiate space like 00:12:38.970 --> 00:12:43.330 a courteous assistant. You can mark your morning 00:12:43.330 --> 00:12:47.649 deep work block as a hard hold. That means it 00:12:47.649 --> 00:12:51.070 can only move for an interview, a medical appointment 00:12:51.070 --> 00:12:54.549 or a hard deadline. You can leave your admin 00:12:54.549 --> 00:12:58.009 block as a soft hold that can flex. is something 00:12:58.009 --> 00:13:01.289 important appears now if you commute your agent 00:13:01.289 --> 00:13:04.389 adds a short padding before and after off -site 00:13:04.389 --> 00:13:07.990 blocks if you have long video meetings the agent 00:13:07.990 --> 00:13:10.690 keeps a five minute buffer before and after those 00:13:10.690 --> 00:13:13.409 meetings so that you're not sprinting from one 00:13:13.409 --> 00:13:16.590 call to the next if the calendar is truly packed 00:13:16.590 --> 00:13:18.870 and there is no 90 minute space for deep work 00:13:18.870 --> 00:13:22.450 the agent splits that block into two 45 minute 00:13:22.450 --> 00:13:26.330 chunks and labels the log with fragmented focus 00:13:27.049 --> 00:13:29.289 so you understand why it felt harder to get traction. 00:13:29.509 --> 00:13:32.029 When it proposes a schedule, it shows you two 00:13:32.029 --> 00:13:35.169 options and asks you to approve one before anything 00:13:35.169 --> 00:13:38.750 is written to the calendar. This keeps you in 00:13:38.750 --> 00:13:40.750 charge while the agent does the heavy lifting. 00:13:40.929 --> 00:13:43.610 Your day is smoother when your week has a rhythm. 00:13:44.049 --> 00:13:47.210 So let's add a weekly review agent that runs 00:13:47.210 --> 00:13:49.730 either on Friday afternoon or on Sunday evening. 00:13:50.750 --> 00:13:54.590 This agent reads your calendar, your tasks, and 00:13:54.590 --> 00:13:57.090 your recent reflections it produces a short summary 00:13:57.090 --> 00:14:00.909 of open loops that still need attention such 00:14:00.909 --> 00:14:05.029 as tasks that are overdue meetings that happened 00:14:05.029 --> 00:14:09.809 without any attached notes and decisions that 00:14:09.809 --> 00:14:12.789 you promised to make but did not it proposes 00:14:12.789 --> 00:14:16.110 a roll forward plan where unfinished items are 00:14:16.110 --> 00:14:18.710 moved to the right place or archived with the 00:14:18.710 --> 00:14:23.360 reasons you suggest three themes for the upcoming 00:14:23.360 --> 00:14:26.899 week so that your attention is not spread across 00:14:26.899 --> 00:14:31.779 eight unrelated goals then it offers a skeleton 00:14:31.779 --> 00:14:35.399 calendar with a few deep work blocks a couple 00:14:35.399 --> 00:14:38.659 of admin windows and one recovery slot for life 00:14:38.659 --> 00:14:41.779 maintenance the agent asks for your approval 00:14:41.779 --> 00:14:45.340 first and then writes your choices into next 00:14:45.340 --> 00:14:48.059 week's when you start monday you're not just 00:14:48.059 --> 00:14:51.440 staring at a blank page You're stepping into 00:14:51.440 --> 00:14:55.139 a shape that already fits your goals. Because 00:14:55.139 --> 00:14:58.100 we want to stay honest without drowning in numbers. 00:14:59.259 --> 00:15:03.159 We add a small metrics dashboard. We only track 00:15:03.159 --> 00:15:06.240 three things. First, you measure habit adherence, 00:15:06.340 --> 00:15:08.600 which is simply the percentage of days where 00:15:08.600 --> 00:15:10.720 you completed the six -minute planning routine. 00:15:11.559 --> 00:15:16.679 Second, we measure estimate accuracy by comparing 00:15:16.679 --> 00:15:20.379 how long tasks actually took. against how long 00:15:20.379 --> 00:15:23.860 you thought they would take now when a task takes 00:15:23.860 --> 00:15:27.720 more than twice your estimate we label it as 00:15:27.720 --> 00:15:31.240 underscoped so that you can split similar tasks 00:15:31.240 --> 00:15:36.779 next time third we measure scope creep by counting 00:15:36.779 --> 00:15:39.100 how many tasks were added after you finished 00:15:39.100 --> 00:15:41.820 your plan and dividing that by the number of 00:15:41.820 --> 00:15:45.720 tasks you completed if scope creep climbs you 00:15:45.720 --> 00:15:48.899 will feel it in your stress Now once a week you 00:15:48.899 --> 00:15:50.899 glance at these numbers and choose one adjustment. 00:15:51.960 --> 00:15:54.440 Once a month, if a metric is not helping you 00:15:54.440 --> 00:15:59.419 change your behavior, you retire it. The dashboard 00:15:59.419 --> 00:16:03.360 is a mirror, not a judge. Its only job is to 00:16:03.360 --> 00:16:05.600 help you tell yourself the truth and make one 00:16:05.600 --> 00:16:08.139 better decision. Every system fails in predictable 00:16:08.139 --> 00:16:11.860 ways. So let's talk through a troubleshooting 00:16:11.860 --> 00:16:15.940 clinic and fix the most common problems. Sometimes... 00:16:16.399 --> 00:16:19.779 the today list balloons when you see that happening 00:16:19.779 --> 00:16:23.519 keep the rule of three sacred if you try to add 00:16:23.519 --> 00:16:25.879 a fourth task the agent pops up and asks which 00:16:25.879 --> 00:16:29.799 agent you want to remove when meetings eat your 00:16:29.799 --> 00:16:32.340 deep work time mark the debug block as a hard 00:16:32.340 --> 00:16:35.279 hold and give the agent permission to automatically 00:16:35.279 --> 00:16:38.840 propose a respectful schedule with two choices 00:16:38.840 --> 00:16:43.360 now when capture becomes noisy with low value 00:16:43.360 --> 00:16:47.620 items teach your agent to tag those items and 00:16:47.620 --> 00:16:50.600 every friday let it suggest a small batch archive 00:16:50.600 --> 00:16:53.340 so that you can clear the noise without thinking 00:16:53.340 --> 00:16:57.399 when the evening reflection turns into a journal 00:16:57.399 --> 00:16:59.340 especially a long journal that you can avoid 00:16:59.340 --> 00:17:04.240 return to the tiny three two one structure and 00:17:04.240 --> 00:17:06.920 capture it at two minutes when you keep skipping 00:17:06.920 --> 00:17:11.380 the kickoff ritual put the script on your phone's 00:17:11.380 --> 00:17:15.160 home screen and tie it to a single button that 00:17:15.160 --> 00:17:17.680 starts your 25 minute timer. These small fixes 00:17:17.680 --> 00:17:21.019 take minutes to implement and they restore the 00:17:21.019 --> 00:17:23.279 calm quickly. Now let me bring this back to the 00:17:23.279 --> 00:17:26.960 feeling that we all want. You do not need more 00:17:26.960 --> 00:17:29.579 willpower. You need a system that moves with 00:17:29.579 --> 00:17:33.420 you. When tiny agents capture the chaos, it helps 00:17:33.420 --> 00:17:37.039 you choose wisely. Place the work onto your day 00:17:37.039 --> 00:17:40.079 with buffers and it reminds you to start and 00:17:40.079 --> 00:17:42.640 your plans begin to stick. When you close the 00:17:42.640 --> 00:17:45.400 loop with an honest reflection, Tomorrow becomes 00:17:45.400 --> 00:17:48.099 smarter all this without you trying very hard. 00:17:48.200 --> 00:17:50.119 You can build the smallest version of this tonight 00:17:50.119 --> 00:17:53.980 Open a blank notion page and create an inbox 00:17:53.980 --> 00:17:57.839 table Create a task page with a simple today 00:17:57.839 --> 00:18:01.220 checkbox and a due date connect Google Calendar 00:18:01.220 --> 00:18:05.980 Add three small prompts for capture prioritization 00:18:05.980 --> 00:18:09.700 and time boxing Turn on confirmations before 00:18:09.700 --> 00:18:13.480 anything is saved or scheduled put the 60 -second 00:18:13.480 --> 00:18:17.619 kickoff on a sticky note by your keyboard. Run 00:18:17.619 --> 00:18:20.119 the routine tomorrow morning and again tomorrow 00:18:20.119 --> 00:18:22.839 evening. You'll feel the difference in a day. 00:18:22.920 --> 00:18:26.460 Before we close, here is how you can keep your 00:18:26.460 --> 00:18:28.420 momentum. If you want my starter kit with the 00:18:28.420 --> 00:18:30.880 Notion pages and prompts I use, send me a note 00:18:30.880 --> 00:18:34.819 on my discussion page on my website. It says 00:18:34.819 --> 00:18:37.740 LifeOS and I will send it. If today's episode 00:18:37.740 --> 00:18:39.640 helped you, please rate the show on Spotify or 00:18:39.640 --> 00:18:42.059 Apple Podcasts. It takes only a moment of your 00:18:42.059 --> 00:18:44.359 time and it helps other people who need this 00:18:44.359 --> 00:18:48.680 kind of calm find it. I record this show on Riverside, 00:18:48.799 --> 00:18:52.220 I host on rss .com and I used cider .ai for research. 00:18:52.740 --> 00:18:54.480 Those links are in the show notes and if you 00:18:54.480 --> 00:18:56.079 buy through them I may earn a small commission. 00:18:56.599 --> 00:18:59.519 I only recommend tools that I actually use. Now 00:18:59.519 --> 00:19:01.880 next time we take this daily system and extend 00:19:01.880 --> 00:19:03.799 it into a weekly review that you will actually 00:19:03.799 --> 00:19:07.119 do. We will build tiny metrics that you can trust 00:19:07.119 --> 00:19:12.029 and a simple habit rhythm. that forgives interruptions. 00:19:12.630 --> 00:19:15.450 For now, remember this. A plan that takes six 00:19:15.450 --> 00:19:17.670 minutes to set is a plan that you will actually 00:19:17.670 --> 00:19:21.549 keep. Build the smallest version tonight. Make 00:19:21.549 --> 00:19:24.630 it pretty later. Thank you for listening to Data 00:19:24.630 --> 00:19:27.170 and AI with Mukundan, where you learn AI by building. 00:19:27.589 --> 00:19:28.430 I'll see you next time.