Pick one recurring piece of work to use your agent for
Over five weeks you built an agent that knows your work, sounds like you, uses your information securely, follows your process and supports a business result. This week’s upgrade is “It becomes part of how I work.” The last rung isn’t another file. It’s using what you built.
People who stop using AI after building something useful rarely stop because it can’t do the work. They fall back into old habits or forget it’s there, and some have real doubts about accuracy, effort or whether it’s helping. Person B in the session used what they built, checked the result and did it again the next time that work came around.
So start with one recurring piece of work, not everything. Choose something already in your normal responsibilities that comes around often enough to try several times in the next 30 days.
Download the 30-Day Agent Action Plan. Print it, type on it in a PDF editor that lets you add text, or copy its questions into a document, and keep it in My Agent Files, or another folder you’ll find again.
YOUR RESOURCE
30-Day Agent Action Plan
Download fileRaymond's two-page worksheet from Session 6. Pick one recurring task, decide how you'll know it worked and where you check the work, log about ten minutes a week for four weeks, then review at day 30.
If you can’t decide, start a new chat, copy Help me choose my first use, attach whichever of your Agent Profile, Safety & Security Rules, Reusable Workflow Card and Business Results Workflow you have, and send it. Pick one of its suggestions and write the plan in your own words. The plan is for you, not another set of instructions for your agent.
Help me choose my first useUse the files I have attached or pasted below. I'm filling in a 30-Day Agent Action Plan. The plan is for me, not instructions for you. Help me choose ONE recurring piece of my work to use my agent for over the next 30 days. Give me suggestions only. I'll choose one and write the plan myself. MY FILES [paste the text of your Agent Profile, Safety & Security Rules, Reusable Workflow Card and Business Results Workflow here, or attach the files and write their names here. Write "not provided" for a file you don't have yet.] Suggest up to three recurring tasks from my files that: - come up often enough that I could use them several times in the next 30 days - my files already support - my Safety & Security Rules, if I've provided them, allow me to use AI for For each one, give me: - the task - the moment in my work that would trigger it, written as an event, such as "Every Friday, when I'm preparing my weekly status update" - the business result it supports - one success measure I could actually observe, counting my own review and editing time - where I must check the work before anyone uses it If I haven't provided any files, ask me about my regular work first. Don't invent figures. If you don't know how long the work takes me today, write "not established". If you need to know more, ask me one question at a time before you suggest anything.
Under 1. Pick your first use, write the recurring task, the moment in your work that triggers it and the business result it supports. Make the trigger an event, such as “Every Friday, when I’m preparing my weekly status update,” rather than “I’ll use AI more,” because an event is what reminds you. The work your Week 4 Workflow Card or Week 5 Business Results Workflow covers is often the best choice, because your agent already knows it.
Decide how you’ll know it worked and where you check it
Under 2. Define success and boundaries, decide how you’ll know the workflow helped and where you stay in charge.
- One success measure you can observe, such as less total time to a reviewed update, fewer corrections or clearer owners for follow-ups. Count your reviewing and editing too. If AI drafts an update in two minutes and you spend twenty correcting it, you only know whether you saved time once you compare the total work.
- Where it stands today. If you know how long the work usually takes, write it down. If you don’t, write “not established” rather than guessing.
- Where you must check the work: the human checkpoint before anyone uses the result, such as verifying dates, owners, commitments and decisions. An approval still belongs to the person authorized to give it.
Then tick one box. Choose Tool and information are approved only once you’ve confirmed both. If either is uncertain, choose Permission / readiness check still needed and verify it before your first use.
Plan your four weeks and your day-30 review
Part 3 turns the plan into a habit. You don’t need to use AI every day. Use the workflow at the next appropriate opportunity, then take about ten minutes a week to log what happened.
- Week 1, Start & observe: use it at the next permitted opportunity, and note what happened.
- Week 2, Repeat & improve: use it again and fix one issue you saw evidence of. Make the smallest useful correction, not a rebuild.
- Week 3, Make it a habit: treat the workflow as part of doing that work, not a separate AI task, and check how much effort it takes. The recurring work is the reminder.
- Week 4, Evaluate & decide: look at the actual results, then go to the day-30 review.
Leave What happened / What I changed blank today, because you haven’t done the work yet. If the work doesn’t come up one week, skip it rather than inventing work. A calendar reminder for each weekly check-in and for day 30 can help.
Don’t fill in 4. Review at day 30 yet either. Read its questions now so you know what to watch for. On day 30 you’ll decide to continue, adjust or pause, and set your next review.
Keep your agent current, and keep learning
Your agent isn’t built once and left alone. When your role, your preferences, a policy or a process changes, an agent still following the old instructions won’t help you. The quick reference lists your five reusable assets and the Context Sandwich, what each holds and when to update it. It calls your Agent Profile your Personal AI Profile. Keep it beside your plan.
YOUR RESOURCE
Week 6 Quick Reference Guide: Your Agent Assets
One page on your five reusable assets and the Context Sandwich: what each holds, when to review or update it, and the Find, Update, Check, Retest routine for keeping your agent current.
When something changes, put it in its one best home. New responsibilities go in your Agent Profile and a new approval step in your Workflow Card, while this week’s dates go in your Context Sandwich, the briefing you give for one task: Task, Context, Constraints and Output Check. Then Find the right asset, Update it with a version and date, Check the related assets and Retest with permitted information. If company policy or permissions change, stop any affected use and verify first. And if your agent says something was approved but you can’t find the approval, check the source. A confident answer isn’t evidence.
To keep building, each week on the Field Guides page starts with its Agent Workshops, which set up what you built inside your own tool. Then try these Field Guides with your agent files attached. Each works better once your agent knows your role and priorities:
- Problem Solving With Your Agent
- Learning with Your Agent
- From Brain Dump to Action Plan
- Find What’s Missing Before You Start
- Write the Ask Your Boss Can Say Yes To
This week’s upgrade, How AI Helped Build This Bootcamp, shows how an agent and the first two of these Field Guides helped build this bootcamp, with one thing to try on a recent meeting.
You started this bootcamp with the human, not the tool, and you finish the same way. Your agent prepares the work, and you decide how to put it to work and keep it working.
Confirm your result
Confirm the outcomes below to finish this guide.
Final checks
You have a 30-Day Agent Action Plan with parts 1 and 2 filled in for one recurring piece of your own work: when you’ll use it, one success measure you can observe and where you check the work.
Your plan and the quick reference are saved together in My Agent Files, or another folder you’ll find again at each weekly check-in.
Provide Feedback
Thanks. That went straight to the people who write these guides.