Memuat
Memuat
Watch every step above performed live, with English narration.
0 plays
Class book
Page 1 / 5
Cover: Claude from Zero to Expert Class #31: Building a Weekly Work Plan
Click a page or use ◀ ▶ to turn · swipe on mobile · to enlarge
Want to go deeper?
Join one of our courses or ask us directly on WhatsApp.
Picked from the software, topic, and level of “Claude from Zero to Expert Class #31: Building a Weekly Work Plan”.
Other ways we can help with Claude.
Learn with a mentor
Scheduled AI & Machine Learning courses with live guidance and a certificate.

Midjourney Course: Create Stunning AI Images from Text
★ 4.9

DALL-E Course: Creating Professional AI Images from Text
★ 4.9

Stable Diffusion Course: AI Art from Beginner to Professional
★ 4.9
Have it built for you
No time to learn Claude? Our team can do the project for you.

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production
★ 4.9

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business
★ 4.9

AI Image Creation with Midjourney — Cinematic AI Art for Business
★ 4.9
Get notified about new Claude classes
At most one email a week. Unfollow anytime with one click.
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Hi, and welcome to the Daily Productivity session. In the last session we built Artifacts. Now we use Claude to tidy up our everyday work routine. In this episode we build a weekly work plan: from a messy task list to a schedule that is realistic and easy to review.
Let's start with the problem. The first reason a work week feels chaotic is that tasks live only in our heads. We forget things easily, and our mind feels full all the time. The second reason is that tasks are scattered everywhere: in chats, in emails, in meeting notes, even on sticky notes stuck to the monitor. Third, everything feels urgent. Because there's no order, small tasks that pop up suddenly often eat the time meant for bigger tasks that actually matter more. Here's the first step: put every task in one place. Dewi, operations manager at Maju Bersama Co., writes all her tasks into Claude just as they are, with no order and no format. Claude groups the tasks into four types: reports and data, customers, meetings and presentations, and housekeeping. Notice that Claude also asks back about the stock report deadline. Dewi fills in the gap: the stock report is due Thursday noon. A follow-up question like this is actually a good sign, because a good plan is built on complete information. A small tip: don't filter tasks at this stage. Write everything down, including things that look trivial. Sorting is the job of the next step.
Step two is setting priorities. The simplest tool is the important-urgent matrix. The first box: important and urgent. The deadline is close and the impact is big, so do it first. The second box: important but not urgent. For example, writing an SOP or learning a new skill. These tasks are easily forgotten, so they need their own slot in the schedule. The third box: urgent but less important. Someone wants it fast, but another person could do it. Tasks like these are best delegated. The fourth box: neither important nor urgent. Just postpone them, or delete them from the list without feeling guilty. This matrix isn't new, but sorting a dozen or more tasks by hand is tiring. This is where Claude helps by making the first pass. Dewi asks Claude to sort her tasks into that matrix, with a short reason for each task. Claude builds a table. The stock report and the promo presentation go into the do-first box, while the attendance recap and the courier invoice check are suggested for delegation. But something is missing. The Sinar store complaint isn't in the table, even though Sinar is a big customer. Dewi corrects it, and decides the attendance recap goes to Andi. This is a healthy division of roles. Claude sorts quickly, but you know the office context best: which customers matter, who you can ask for help, and what your boss is watching right now.
In step three, the priorities move into a schedule. The prompt has four parts. First, the context: Dewi's working hours and her fixed meeting, the vendor meeting on Wednesday at ten. Second, the task: build a schedule from the do-first and schedule boxes. Tasks that were already delegated don't need to be included. Third, the constraints. This is the part that makes the schedule realistic: heavy work in the morning, one hour of buffer every day, and at most two big tasks per day. Fourth, the format: a table per day with the time, the task, and an estimated duration, so it's easy to move into the calendar. Dewi moves the schedule into her calendar. Monday morning opens with a reply to the Sinar store complaint, because a big customer shouldn't be kept waiting. The big stock report is split into three blocks: processing the data on Monday, analysis on Tuesday, and finalizing it Thursday morning, just before the noon deadline. The vendor meeting on Wednesday is fixed, so Wednesday is deliberately kept light. That's buffer room for the unexpected. The promo presentation is prepared Thursday afternoon and delivered Friday morning. Tidying the warehouse files goes on Friday afternoon, when energy usually runs low. Notice that this schedule isn't full. The empty space is on purpose. A plan that's packed too tight usually collapses by Tuesday.
In step four, the schedule becomes a checklist. Dewi asks Claude to build a weekly checklist as an Artifact, grouped by day with checkboxes. A summary appears in the right panel: seven tasks, two delegated, and the nearest deadline is Thursday at noon. Below it is a list per day that she can tick off. This checklist can be saved, printed, or pinned in the team's group chat. Every Monday, Dewi simply asks for a new version with that week's tasks. The same pattern works for a small business. Laras from Sunset Coffee uses four groups. First, stock and ingredients: buying milk and palm sugar every Monday and Thursday. Second, social media content: three posts this week and one gift hamper promo. Third, finances: a sales recap every day and a bank deposit every Saturday. Fourth, the tasks handed to Dimas, her admin: replying to order chats and checking the order form. Feel free to swap these four groups for the areas of your own work.
The last step, and the one people often forget, is the review. Every Friday afternoon, Dewi pastes her ticked checklist into Claude and answers five questions. First, which tasks were finished on schedule? Second, which tasks slipped, and why? Was it because of sudden requests, or simply because there was too much? Third, which time estimates were too optimistic? Many people think a report takes two hours, when it really takes five. Fourth, what needs to carry over to next week. Fifth, one thing you want to improve in the way you work. Claude can summarize these answers and give suggestions. But remember, this review is for you. Don't paste confidential company data or performance reviews of your coworkers. Here's an example. Dewi writes a short review: the stock report went out on time and the presentation went well, but the warehouse files weren't tidied because of a sudden order. The stock analysis also took five hours. Claude sums up the week and draws two lessons. Data analysis needs a budget of about five hours, and Friday afternoon is prone to sudden orders. The warehouse files move to Tuesday morning. Dewi agrees and turns those two lessons into new rules. Next week, she pastes them into the constraints part of her schedule prompt, so her plan becomes more realistic. So a review isn't just judging yourself. A review is how you train your next plan to be more accurate. To sum up, a weekly plan is a cycle of four moves. First, collect every task in one place. Second, sort them with the priority matrix, then correct Claude's result with your own knowledge. Third, schedule them as time blocks and leave some buffer room. Fourth, review at the end of the week, then repeat. After three or four weeks, your time estimates will be far more accurate, and Monday morning won't feel scary anymore.
We've built a weekly work plan: collecting every task, sorting with the priority matrix, scheduling with buffer room, making a checklist, and reviewing at the end of the week. In the next episode we tackle something that almost always shows up in the schedule: meetings. We'll learn to write meeting minutes and follow-ups with Claude. See you there!
Try these on your own after watching to lock in what you learned.
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
Notes are saved with the current video time and are only visible to you.
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.

Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
See our clients →