How to run an AI workshop on your own work

Pick a task the team already does

Marketing, operations, sales, or any team can use this shape, as long as there is a real task. If there is no task, do not book the session. A workshop is for the people in the room. It is not a keynote, and it is not a workflow handed over afterward.

Bring the material and the people

• A real task the team already does.
• The material that task uses: the report, the inbox, the tickets, or the pages.
• The people who do the job, including whoever has to trust the output.

Work from the messy source

A demo company teaches the wrong habit. People remember the example and then cannot find the same shape in their own files. Start from the report, the inbox, or the ticket list. If the source is missing, the draft should say so.

Bring the awkward version of the task, not the tidy one. The messy source is where the check matters. If the team learns to notice a missing citation on their own material, they can notice it next time.

Stop before a send

A person stays in the room when the output has to be trusted. Stop a step that tries to send, publish, or change a record on its own. The point of the session is judgment, not a race to automate the last click.

Leave with the material you used, the checks a person applied, and a clear line between what the model drafted and what someone still has to decide. Do not leave a binder of prompts that only works on a sample company.

This is not the workflow guide. A workflow is the job written down so someone can run it later. A visibility check is a sample of AI answers with the dates written down. This page is the session.