Agentic AI
Session Slides
All slides from the session with speaker notes. Expand any slide for the full script.
Slide 1
2 minutes
The Time Waste
Agentic AI Essentials | Micro Session
Cowork + Calendar: Let AI Prep Your Week**
Every Monday you spend 30 minutes figuring out what the week looks like. That is 26 hours a year. Let us get them back.
Think about what you do every Monday morning. You open your calendar. You read last week's meeting notes. You check your task list. You try to figure out what actually matters this week and what can wait. You do this manually, every single Monday, and it takes forever. The math is brutal: 30 minutes times 52 weeks equals 26 hours per year that you are spending on work that an AI can do perfectly in under a minute. Today we are going to show you how to hand this off to a machine and never do it manually again.
Slide 2
3 minutes
What a Weekly Briefing Workflow Is
A workflow has three parts:**
INPUT -> PROCESS -> OUTPUT
Inputs: calendar, notes, tasks
Process: AI reads and connects them
Output: one document, every Monday morning
A workflow is not complicated. It is just data flowing through a system and coming out the other side in a new form. For a weekly briefing, your inputs are the things you already have: calendar events, meeting notes from last week, your task list, any project documents that matter right now. The process is what the AI does: it reads all that, understands what matters, and figures out what your week actually looks like. The output is what you get: one clean document that arrived in your inbox while you were sleeping. This is not hypothetical. This is something you can build today.
Slide 3
4 minutes
What to Include in Your Briefing
Minimum four inputs:**
1. Calendar - all events for the coming week
2. Meeting notes - from last week or this month
3. Open tasks - things you committed to but haven't done
4. Priorities - what your manager or team thinks matters this week
Each input tells a different part of the story.
Calendar tells you the structure of your week: when are the big meetings, when do you have focus time. Meeting notes tell you what got decided recently that you might have forgotten about. Open tasks tell you what is at risk of slipping. Priorities tell you what actually matters versus what just feels urgent. When you combine these four inputs, you get a complete picture of what your week looks like. Most people keep these things in different places and never connect them. The workflow connects them automatically.
Slide 4
5 minutes
Exporting Your Calendar
Your calendar has to be a file Cowork can read.**
Formats that work:
ICS file (from Google Calendar or Outlook)
CSV spreadsheet (clean list of events)
Plain text (date, time, title, attendees)
Steps:
1. Open your calendar app
2. Export this week and next week as a file
3. Save it to a place Cowork can access
Most calendar apps have an export feature. In Google Calendar, you right-click on your calendar name and hit settings, then find the export option. In Outlook, it is similar. For CSV, you might have to format it yourself, but it is just columns: date, time, title, location, attendees. Plain text works too if you just write it out neatly. The key is that Cowork is going to read this file, so it has to be formatted in a way an AI can understand. If your calendar app does not export easily, just copy your week into a text file. Format does not have to be fancy as long as it is consistent.
Slide 5
6 minutes
Writing the Cowork Instruction
Your instruction has to be specific enough to always produce the same structure.**
Weak instruction:
"Summarize my week."
Strong instruction:
"Read the attached calendar, meeting notes, and task list. Produce a document with these sections: 1) This Week in Brief (2-3 sentences), 2) Meeting Prep (for each meeting this week, list attendees and context), 3) Open Items at Risk (things I said I would do but haven't), 4) Key Priorities (what my manager said matters most). Keep each section short."
The difference between a weak and strong instruction is specificity. A weak instruction lets the AI decide what format to use. A strong instruction locks down the structure so it is the same every single Monday. When you write your instruction, you have to think about what you actually need to see in your briefing. Do you need a list of who is attending each meeting? Yes, write that. Do you need context for each meeting, like what you are supposed to discuss? Yes, write that. Do you need a summary of your entire week? No, keep it short. The more specific you are about the structure, the less the AI has to guess about, and the more useful the output is.
Slide 6
5 minutes
Building It in Cowork
In Cowork:**
1. Create a new file or scheduled task
2. Attach or reference your calendar file
3. Attach or reference your meeting notes
4. Paste your instruction
5. Let it run once manually to see what you get
6. Adjust the instruction if needed
7. Schedule it to run every Monday at 7 AM
Cowork is designed for exactly this workflow. You set up your inputs once, write your instruction once, and then it runs automatically. The first time, run it manually and look at the output. Does it match what you wanted? If not, change the instruction. Does it miss something important? Add it. Once you have it dialed in, schedule it to run every Monday morning before you wake up. Then on Monday, you open your inbox and your entire week is already briefed out. No more 30 minutes of research.
Slide 7
4 minutes
From You to Your Team
Once it works for you, hand it to your team.**
1. Document your workflow (inputs + instruction + output)
2. Share the instruction template
3. Let each person customize the input sources
4. Have them test it
5. Schedule it for everyone
You have just created a team capability that did not exist before.
This is the leadership upgrade that most people never take. You build something that works, you hand it to your team, and suddenly everyone walks into Monday briefed and ready. This is not micro-optimization. This is structural advantage. When your team is already prepared at the start of the week, they work faster, they catch problems earlier, and they spend less time in sync meetings figuring out what is happening. The template is reusable. Other team members can use the exact same instruction with their own calendar and task list.
Slide 8
1 minute
What This Gets You
What you get back:**
26 hours per year (just for you)
Consistency (same structure every week)
Preparation (you are never caught off guard)
Multiplier (your team can use the same template)
A system is better than a skill.
The insight here is that preparation is not a skill you develop, it is a system you build. An AI Officer who has this workflow has a structural advantage. Everyone else spends their Monday morning figuring out the week. You already know. That is not luck. That is a system working for you while you sleep.