Week 3: Build out your org with agent teams
What am I doing this week, and what will my organization have by the end of it?
- Source
- Internal's lesson, src/sara-week3/internal/lessons/anw-w3-m0.md (Internal b518c35b, 2026-10-22 17:15), read by md_week3.py.
- Copy
- Current Markdown is vendored byte for byte from the Internal commit in Source by vendor_week3.py. Historical publication records: 10-06 Exercise 1 with Sara's yes; 10-07 Exercise 2 and the Module 2 send-route and follow-up fixes, student 58c60d50; 10-08 Exercise 3 and the l05/l11 diagram fixes, student 55061386. Those records do not qualify later Outlook changes. Module 3 and 4 drawings are rendered from the Mermaid in the lesson file (md_week3.py --figures).
- Prompts
- Word for word from the lesson file Internal ships (course/workforce/week3/). Not run end to end from Learn.
- Checked in the app
- Not checked in the app from Learn.
- Open to students
- Yes.
Staff only: source, checks, open points. Not student-facing.
Source. Sara's draft, 6 October (aibuild-lab/course-design PR #148, intake/week3-welcome-and-module1-fixes-2026-10-06.md, part A), in the shape of the Week 2 welcome. Sara's rulings: the End of Week 2 note is recommended, not required; no dates; Customize, Build, Delegate. Read only: no prompt file, nothing is saved.
Checked against the release (6 October).
- Times are the sums of the final lessons' own estimates. Module 1: l01 30 min + l13 33 min. Module 2 (Exercise 1): l02 90 to 150 min, l03 2 to 3 hours in three sittings, l04 40 min, l14 about 40 min plus up to 20 for the rerun, so 4 h 50 to 7 h 10. Module 3: l05 50, l06 40, l07 45, l08 30, l09 45, l11 45 min of the student's own time, about 4 h 15, plus agent time. Module 4 has no lesson files yet; its line is the spine's (1 h 05 plus the overnight run). Re-check when Module 4 is written.
- Changed from Sara's draft: "spread across two days" became "spread over at least a day" (l03 asks for three sittings across a day, rounds a few hours apart); "You'll hear in Slack when it opens" became a pointer to The Professor, because nothing in the release posts to Slack (restore Sara's line if the team commits to posting by hand); the mailbox line now matches l02 and its details page (Fastmail connects directly; Microsoft 365 needs one approval from whoever manages the organization's account; forwarding goes to a free AgentMail inbox and is paid on some providers); a line on checking for this week's course files was added, because l02's Before you start points here for it.
- Fisk Method and TOAST:
workforce/skills/aibl-fisk-method/SKILL.md(eight phases, Phase 6 Iterate runsaibl-toast-loop).
For Wade (Learn). "Soon" is Sara's word for a module that isn't open; check it matches what Learn shows.
Last week your organization learned your work. This week it gets agent teams: groups of agents that carry one piece of recurring work from start to finish.
You get three teams this week, and each time you hand over more:
- Customize. We give you an email team. You connect it to your inbox and your tools, teach it how you write, and watch it work.
- Build. You design a team for a piece of your own work with the Architect (Archie). The Operator (Gigawatt) builds what you approve.
- Delegate. You brief your Chief of Staff, walk away, and review the team it built the next day.
Every team gets the same check: an observational eval. You write down what you expect, watch what the team produces, and note what happened. Next week, in Week 4, you grade your teams from those notes.
A working email team on your own inbox, a second team you designed yourself, the method to design the next one, and your observational eval notes on every team.
One agent can do a task. A team can carry a whole piece of work: one agent reads, one researches, one writes, one checks, and you decide. Once you know how a team is designed and how to check it, you can build one for any recurring work, your own or a client's.
Four modules, in order. Each one uses what the one before it made.
You choose the work, write what you expect before each run, and approve every step that changes your organization. Nothing installs, sends or goes on the record without your yes.
How it works
| Module | What you do |
|---|---|
| 1 · The method | Learn how a team is designed: outcome, flow, roles, handoffs. Meet Archie and Gigawatt. Write a goal an agent can finish. |
| 2 · Customize: your email team | Set up the email team on your inbox. Run three observational evals. Plan its schedule and how it earns more freedom. Make one change and run it again. |
| 3 · Build: your own team | Design a team with Archie, approve it, and have Gigawatt build it. Test it, fix one thing, and put it on your organization's records. |
| 4 · Delegate: wake up to a team | Tell your Chief of Staff the outcome you want, decide what the agents may read, and review the team the next day. |
The Course Companion (The Professor) guides every lesson. A module that isn't open yet shows Soon. Ask The Professor any time which modules are open.
What to have ready
- This week's course files. Your workbench has the folder
course/workforce/week3/. If it's missing, ask The Professor what to do before you start. - Your end-of-Week-2 note, if you saved one: the work you still do yourself, and your idea for this week. The Professor reads it back in the first lesson. No note? You describe the work in your own words instead.
- Your work mailbox. Gmail, Microsoft 365 for work or school, and Fastmail connect directly. With Microsoft 365, whoever manages your organization's account approves the connection once. Other email is forwarded to a free inbox your agents can read (some providers charge for forwarding); the lesson walks you through it.
- Where your answers live. The places you'd look to answer an email: a shared drive, Notion, your calendar.
- A piece of recurring work you'd like a team for. Marketing works well: turning what's happening in your field into finished posts, or getting you booked on podcasts.
Set aside the time
| Module | About |
|---|---|
| 1 · The method | 1 hour |
| 2 · Customize | 5 to 7 hours, spread over at least a day, so new email can arrive between rounds |
| 3 · Build | 4 to 5 hours |
| 4 · Delegate | 1 hour in the evening, then your agents work overnight |
Your agents also need time to work. Start a run, then do something else while it finishes.
Next: Learn the method, and meet the agents that design and build your teams.
Words you'll meet this week
- agent team
- Customize, Build, Delegate
- observational eval, and TOAST: Take the output, Observe it, Analyze why, Stick one change back in the oven, Test again