Frequent and reviewable
A recurring drafting, extraction, classification, research, or coordination task with a knowledgeable human reviewer.
Organization onboarding · Version 1.0
AI for Teams
Readiness Guide
Everything the buyer and workflow owner need to prepare for a useful, safe, and measurable workshop.
Fit
This workshop is ready when one operating problem is ready.
Policy is unclear
The team has not approved the tool, information, accountable owner, review method, or incident process.
Consequential autonomy
A task that independently changes safety, rights, employment, payment, regulated advice, external commitments, or access.
Named roles
Four responsibilities must be visible.
- Buyer
- Approves scope, commercial terms, participant time, and follow-through.
- Workflow owner
- Explains current work, approves the baseline, and owns the pilot decision.
- Review owner
- Checks outputs using the required expertise and evidence.
- Escalation owner
- Handles privacy, security, legal, employment, safety, or professional questions.
Seven days before
Prepare the work, not a sales demonstration.
- Choose up to three candidate workflows that occur regularly.
- Record the current steps, people, tools, wait time, review time, rework, and exceptions.
- Select one outcome measure and one risk or quality measure.
- Confirm approved AI tools and information classes.
- Sanitize examples or create fictional equivalents.
- Identify participant accessibility, language, device, and support needs.
- Name the people who can answer policy and process questions.
- Send participant preparation and the baseline check-in link.
Information boundary
Write the rule before anyone opens a tool.
| Question | Decision to record |
|---|---|
| Which tools are approved? | Name the exact service, account type, settings, and owner. |
| Which information can enter? | Define public, fictional, internal, confidential, personal, and prohibited classes. |
| What may the output influence? | Name the decision and the accountable human reviewer. |
| What evidence is required? | Name original sources, calculations, examples, or records used for review. |
| When must the team stop? | Define uncertainty, incident, exception, or consequence thresholds. |
After the workshop
Protect the 30-day experiment.
- Approve or reject the pilot brief before routine use.
- Keep the tool, information, workflow, and review boundary stable during the test.
- Record attempts, completion, correction time, exceptions, and incidents.
- Hold a short weekly practice and issue review.
- Compare the full cycle with the baseline—not merely model generation time.
- At day 30, choose expand, revise, stop, or another workflow and record why.