Less wondering.
More doing.
Build a useful AI workflow in 90 minutes.
Bring your curiosity. We'll bring the structure.
One task.
One workflow.
A new skill.
- A clear, reusable AI instruction
- A reviewed practice output
- Your personal quality checklist
- A workflow you can repeat
Pick one useful task
Choose a task you repeat and understand well. For this workshop, use our fictional meeting notes or a low-risk example you are permitted to share. Your aim is a reliable result you can inspect, not a fully automated system.
Fictional sample meeting notes
Monday project check-in — fictional practice notes Maya: The customer onboarding checklist is approved. Theo: I will draft the welcome email by Wednesday. Maya: We should aim to launch Friday, but legal review is still pending. Sam: I can review the email after Theo sends it. I have not confirmed a review date. The group agreed to keep the pilot to 20 customers. Nobody was assigned to follow up with legal. Next meeting: Thursday at 10 a.m.
Record your normal completion time, including checking and revisions. If you have no baseline, leave it unknown and measure it later.
Understand what AI needs
An AI assistant generates outputs from its training and the context available to it. It may produce plausible but unsupported details. Supplying notes does not guarantee a faithful summary: your instructions and review still matter.
In the sample, Friday is a proposed launch date. Sam has not committed to a deadline. The legal follow-up has no owner.
Write a useful brief
Give the assistant a task, audience, source, constraints, and output format. Use the sample instruction below, then adapt it. Open your approved AI tool separately; this workshop does not send your notes to an AI service.
Fictional sample meeting notes
Monday project check-in — fictional practice notes Maya: The customer onboarding checklist is approved. Theo: I will draft the welcome email by Wednesday. Maya: We should aim to launch Friday, but legal review is still pending. Sam: I can review the email after Theo sends it. I have not confirmed a review date. The group agreed to keep the pilot to 20 customers. Nobody was assigned to follow up with legal. Next meeting: Thursday at 10 a.m.
Turn the supplied notes into an action table for our project team. Separate decisions, actions, proposals, and open questions. Use only the notes. Do not infer owners or deadlines. Mark missing information as not confirmed. Include a short evidence excerpt for each item.
Copy your instruction and the sample notes into an approved AI tool. If you do not have a tool, practice by creating the table manually.
Make a first attempt
Run your brief with the sample notes. Keep the original output so you can compare it with your revised version. Watch for details the tool adds without evidence. A neat table is only useful if its contents are trustworthy.
Fictional sample meeting notes
Monday project check-in — fictional practice notes Maya: The customer onboarding checklist is approved. Theo: I will draft the welcome email by Wednesday. Maya: We should aim to launch Friday, but legal review is still pending. Sam: I can review the email after Theo sends it. I have not confirmed a review date. The group agreed to keep the pilot to 20 customers. Nobody was assigned to follow up with legal. Next meeting: Thursday at 10 a.m.
Expected facts: onboarding checklist approved; Theo drafts the email by Wednesday; pilot limited to 20 customers; launch date and Sam’s review date unconfirmed; legal follow-up owner unassigned.
Check and improve
Compare every important claim against the source. Use the checklist below to review the result. If an item fails, make a specific revision to your instruction or output. An unchecked box is a useful signal to investigate, not a score to hide.
A strong revision preserves uncertainty and includes the missing legal owner. Ask a colleague to review a consequential result before using it.
Keep what works
Try a second short example: “Nina will prepare the draft budget. No deadline was set. A $500 cap was suggested but not approved.” Your workflow should not convert the suggestion into a decision. Then document the recipe you can use next time.
Compare total time and quality with your baseline. Save your workbook, choose one task to repeat this week, and review the workflow after three uses.
You have a starting point worth keeping.
Download your workbook to keep your notes and checklist. This is a self-guided practice record, not a verified certification.