# Facilitator plan: from a campaign draft to your own process

90 minutes. Participants use ChatGPT or Claude on a phone or laptop. Every slide asks them to produce or check something. Keep the diagrams visible while they work; there are no discussion-only slides or hidden teaching steps.

## What everyone makes

Each participant chooses a real or invented product. They dictate a brief, improve the request, then run the same process: brief -> three emails -> fact check -> save three Gmail drafts -> human review in Gmail. The participant reads all three drafts and makes one judgement-based edit. Leave recipients empty and keep everything unsent.

This process runs once. The assistant stops after saving the drafts. Do not add scheduling, a review-request email, reply polling or automatic continuation. The human-owned final step is the participant reviewing the drafts in Gmail.

## The split at exercise 08

Participants with an existing business choose a different recurring process they actually do. They use the interview to map and approve it, mark the human steps on that same map in 09, check in with you, then connect tools, rehearse and schedule.

The activity for participants without an existing business is awaiting the facilitator's next instruction. Do not give them the campaign again or invent an automation exercise for them. Slides 08–13 currently specify the existing-business track; the other track and its closing evidence are still to be added.

For the business track, look for an approved map, a saved rehearsal output, tested human steps and a verified scheduled task. Test a matching reply and continuation only where automation continues after a human decision. If a capability is unavailable, record the blocker and distinguish a manual handoff from an automated step.

## Preparation

- Run the shared campaign on your account: product brief, three proposed emails, authorised Gmail draft writes and manual review in Gmail. Verify that your selected plugin or connector can create drafts; email read access alone is insufficient.
- Test one small recurring business process, including its actual tools, any human reply path and scheduling. Know how to pause the task.
- Prepare pairing or a demo account for blocked connections. Do not promise identical features across plans and organisations. Manual saving is a clearly labelled fallback.
- Have the sample product brief PDF and example emails available. The sample deliberately omits date, timezone, price and booking URL; keep unknown facts in brackets or ask for them.
- Slide 3 links ChatGPT and Claude to their official guides. `connect-tools.md` is the setup handout. Claude's screenshot shows an earlier directory layout; its caption says so.
- Participants may type instead of dictating. Use sample data and drafts throughout. Do not ask them to expose private inbox content or credentials.

## Run of show

| Exercise                      | Minutes | Facilitator instruction                                                                                                        | Participant action and evidence                                                                                                                                            |
| ----------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 01. Choose a product          | 3       | Have everyone open an assistant and choose something to sell.                                                                  | Name a real or invented product and its buyer.                                                                                                                             |
| 02. Genie and CEO             | 3       | Point to the CEO/genie roles while everyone writes. Take one concrete example.                                                 | Write the audience, offer and one decision to keep.                                                                                                                        |
| 03. Connect Gmail             | 7       | Demonstrate setup and permissions. Check draft-writing capability.                                                             | Connect Gmail, verify one chosen email read and identify available draft actions.                                                                                          |
| 04. Voice brief               | 5       | Dictate a short product description and correct its transcript.                                                                | Dictate their product, answer questions and correct the written brief. Keep this chat.                                                                                     |
| 05. Checkable request         | 4       | Leave the four-request visual visible while people adapt it.                                                                   | Write a request with audience, output, word limit, source check and draft-only boundary.                                                                                   |
| 06. Fill the gaps             | 4       | Use Andrew Rose's eight lenses to check the existing brief.                                                                    | Add a tone reference, claim limit and missing facts.                                                                                                                       |
| 07. Campaign and human review | 12      | Demonstrate the same process with Field Notes Studio, then open Gmail Drafts.                                                  | Use their own brief, review the proposed sequence, approve saving three unsent drafts, open all three and make one judgement-based edit. Record manual saving if required. |
| 08. Map a different process   | 12      | Split the group. Existing-business participants start a fresh interview; give the other group its separately planned activity. | Narrate an actual recurring process, correct the full map and explicitly answer yes/no. Stop before connections.                                                           |
| 09. Mark human steps          | 5       | Check in quickly with each person: which steps need a human, who owns them and why?                                            | Mark the same 08 map Agent / Human / Agent with approval. Report the split to you, then confirm the check-in in chat.                                                      |
| 10. Connect process tools     | 6       | Release people after check-in. Tie each connection to their marked map.                                                        | Verify necessary accounts, narrow reads, approved test writes and any continuing human reply path.                                                                         |
| 11. Rehearse                  | 12      | Ask to see outputs and actual tool results. Stop before retrying uncertain writes.                                             | Run sample data; test missing and repeated inputs. Test human steps and, if needed, revision, wrong-version reply and correct continuation. Record failures.               |
| 12. Schedule                  | 12      | Show the scheduling UI and pause control. Use this time to fix a failed rehearsal if needed.                                   | Save the runbook for their 08 process, review and approve the concrete task, then verify active status, access and next run.                                               |
| 13. Demonstrate               | 5       | Pair the business track. Give each person two minutes to show and answer questions.                                            | Show reviewed Gmail drafts, then process map, output, human steps and schedule. Name blockers and how to pause.                                                            |

Total: 90 minutes. Do not activate a process that has not passed its rehearsal. The non-business track's later activity and closing evidence remain open.

## Materials

- `/workshop/process-interview/SKILL.md`: reusable interview. The page's “Copy the workshop interview” button appends the 08 workshop starter, including the 09 facilitator gate; the download contains the reusable guide.
- `/workshop/campaign-brief.pdf` and `.md`: the same example product brief. Participants normally use their own product; the sample shows the process concretely.
- `/workshop/campaign-example.md`: three illustrative emails and the Gmail review checklist.
- `/workshop/connect-tools.md`: official setup links and verification steps.

The website presents instructions. Connections, writes and schedules happen in the participant's own assistant with its supported capabilities. Keep the workshop within ChatGPT or Claude; do not require coding tools or another automation platform.
