Your Team's First Month

In practice

In week one, the team chooses two tasks, one low-stakes and one moderate: drafting internal meeting notes, and summarizing client documents for account managers. For each, it writes the one-sentence use description and runs the twelve-risk scan, and it confirms which tool is approved for client material. In week two, it writes its rules: approved tools, what may never be pasted, forbidden uses, the review level for each task, and the logging rule, on two pages, with a named owner. In week three, it builds and tests prompts. For each task the team writes success criteria and collects real test cases, including an awkward one, then improves the prompts one change at a time. The prompts that pass go into a shared library with their test cases. In week four, it runs both tasks for real, logs every output as accepted, edited or rejected with a reason, and meets at the end of the month to read the log. Edits on the summaries are mostly for missing points, so the summary prompt gets a required-points list. The meeting notes need almost no edits, so their review stays light. The team agrees what to try next, and when to run the risk scan again.