You have enough AI answers. Make something you can use.
Start with one source, give the work a purpose, and check it as it grows. This series takes you from a promising conversation to a result you can explain, improve and use again.
By Joe McKenna. Adapted from his September 29, 2026 workshop.
Keep the source, the task and your judgment connected. A notebook organizes material; a conversation develops the work; you decide whether the result is ready.
When the answer sounds good but the work is still unfinished
You ask AI a question. It gives you a lot of information. You ask it to change something, and now something else has changed too. By the time you get to the third version, you are checking details you thought you had already settled.
In my workshop, I start with three frustrations: the conversation loses its thread, an answer uses information you did not intend, and there is too much material to turn into something useful. The practical response is to give the work a better structure.
We used an employee handbook, asked about its contents, developed useful work from it, opened a draft for editing, and explored other formats. You can practice the same sequence with one short source you know. You do not need to recreate an entire workshop before you get a useful result.
From one source to a useful draft, then an edit
What to notice: Follow the sequence Joe previews: make useful work from the handbook, edit it, and prepare other ways to share the information. The historical handbook remains practice material.
1:01. From The One-Person AI Business, 18:20.84–19:21.44.
Visual context: Joe previews the handbook-to-document workflow beside the workshop lesson screen. He describes the planned document, editing and additional formats aloud.
Read the clip transcript
We're going to work with its tool notebook and first off, we're going to create a usable document from that. Real quickly, we're going to break down that document into important onboarding roadmap points. If you're in HR and you got this big document and you got a bunch of people coming on, you can go to your document and say, "Hey, give me a roadmap of day by day of the people that are coming on." But then when you get past that, we need to edit it. We need to be able to fix it, and so we can do that. Again, this has worked from this big document, so if normally I go to edit something or ask, I got to change something after it's built me something, it loses contacts of the resource and it starts rewriting and changing what I asked it to edit. Then from there, that partner application, that partner tool of Gemini is going to create assets for us that will help us share that information.
Automatically transcribed from this excerpt and aligned locally. Transcript accuracy and word synchronization still require a human listening review.
Follow the work from source to finished result
- Choose. Pick one relevant source and one person who needs the result.
- Understand. Ask what the source establishes and inspect the answer.
- Make. Request a small, useful output for that person.
- Check and edit. Compare the draft with the source, then change what needs changing.
- Reuse. Keep the confirmed material together and choose another format only when it serves a purpose.
These are checkpoints, not a promise that a particular tool will get everything right. You may go back to the source, narrow the task, or ask a person to resolve an uncertainty. That is progress: you are finding the boundary before handing someone a misleading finished product.
- Source
- The original material you can inspect, such as a brief, approved procedure or reading.
- Notebook
- A collection of material organized around a topic or project. Check which sources a particular task can actually access.
- Conversation
- The exchange in which you explain the job, question the answer and correct the direction.
- Draft
- A proposed result that still needs your review. Saving it does not make its claims true.
Try the whole process with one short event brief
This fictional brief and the outputs below were written for this article. They are a worked example, not a transcript of an AI test or a real CloudWise event.
Your source
A community group is holding a repair-information evening on October 15, from 6 to 7 p.m., in the library meeting room. Visitors can ask about local repair resources. They should bring a description or photograph of an item, not the item itself. Attendance is free. The room holds 20 people. Registration opens October 1. The brief does not give a registration link or promise that repairs will be performed.
Your job: prepare a volunteer to answer the first questions visitors are likely to ask. Start by asking for the event’s purpose, attendance instructions and missing information. Check the answer against the brief.
Using only the event brief, make a short volunteer preparation checklist. Separate confirmed facts from questions for the organizer. Do not invent a registration link or promise repairs. Keep it short enough to compare with the source.
| Draft item | Your check |
|---|---|
| Tell visitors the event runs October 15, 6–7 p.m. | The date and time match the source. No year was provided; confirm it before distributing the guide. |
| Ask visitors to bring a description or photograph, not the item. | Keep the restriction. Shortening this to “bring your item” reverses the instruction. |
| Confirm the registration link with the organizer. | Good: the draft has left missing information as a question. |
| Tell visitors their item will be repaired. | Reject this addition. The source promises information about resources, not a repair service. |
Now edit the checklist for its reader. Put the date and arrival instructions first. Keep the unanswered registration question in an internal preparation section. A public flyer should wait until that detail is confirmed.
If you later make a slide or an infographic, the same restrictions still apply. A shorter format cannot turn an unknown into a fact or quietly remove an important instruction.
Choose the lesson that matches where you get stuck
You can read the series in order or enter at the problem in front of you. Each lesson has a different job.
- AI Missing the Point? Start With a Better Conversation
Check the interpretation before assigning the finished task. This is the completed first article.
- When AI loses the thread
Identify missing, competing or stale context before adding another long instruction.
- Turn a long document into a useful guide
Move from understanding a source to a checked output for a particular reader.
- Keep a good draft while changing one part
Make a targeted revision and inspect what stayed the same.
- Reuse the material you keep explaining
Organize sources, bring them into a new task and maintain the collection.
- Explain one source in different formats
Choose slides, an infographic or a study aid according to what the reader needs to do.
- Get past the blank page
Ask for a manageable starting point and decide what deserves to survive.
- Judge training by what learners can do
Design an exercise with visible evidence of independent practice.
- Improve teaching materials without losing the learning
Evaluate a revision against the intended learning and your institution’s rules.
Use the tool that fits the next step
For a first exercise, a short pasted source may be enough. If you are using Gemini with a document, Google’s current instructions describe Add files and supported upload options. A school or work account may have administrator-controlled access. Check Google’s file guidance before planning around a feature or a large source.
A notebook becomes useful when you will return to a collection. An editor becomes useful when you want to work on the wording directly. An asset generator becomes useful when you already know what the new format needs to communicate. You can also copy a reviewed draft into an editor you already use.
My workshop uses the tools available on screen at the time. The detailed articles link current product guidance where their steps depend on a tool. Follow the purpose of the step if your account looks different. Getting a source attached and checking its use matters more than matching a screenshot.
Decide what “ready” means before you share it
Before you call the work finished, ask three questions. Can I show where the important claims came from? Can the intended reader use this without needing my explanation? Have I left any unknown looking like a settled fact?
For the event guide, that means checking the date, the no-items instruction and the registration gap. For a course reading, it may mean checking whether a summary preserves a qualification in the author’s argument. For a workplace procedure, ask the document owner about an unresolved rule instead of letting a draft decide it.
Keep the original source and the version you checked. Record any added recommendations as recommendations. When the source changes, look again at the outputs that depend on it. Reuse saves effort only if you know what you are reusing.
Questions that come up
Do I need every tool in the workshop?
No. Start with a source and a small output. Use a notebook when a collection needs organizing, an editor when a draft needs revision, and another format when it helps a real reader. You can practice the checks with pasted text.
Which article should I read first?
Begin with the completed article about checking what AI understands if you are new to the process. If you already have a draft or a source collection, choose the lesson that addresses your immediate problem.
Does organizing sources eliminate incorrect answers?
No. Sources make answers easier to inspect, but the AI may still omit, misread or add material. Check the claims that matter and repeat that check after substantial revisions.
Can I use this workflow for student assignments?
Use your instructor’s rules and the purpose of the assignment to decide which assistance is allowed. A student still needs to perform and explain the required learning. The examples in this series do not establish permission for a particular course.
15 Days of AI
Put this into practice with Joe.
Give AI useful context. Work with your own materials. Create something you can use. Explore the independent classes and choose the ones that fit your goals.
Explore the classesAbout this lesson
The first-person workshop explanation is an editorial adaptation of Joe McKenna’s September 29, 2026 teaching, not a verbatim quotation. The event brief, worked guide, workflow definitions and checks were developed for this article. No new audio quotations are presented. The source workshop’s historical 2012 handbook exercise is a practice example, not current company policy.
Source passages: 13:47–21:18; 33:50–45:18; 45:18–54:12; 54:12–1:02:24. Source: The One-Person AI Business, September 29, 2026.
Official guidance checked September 30, 2026. Product features can change.
AI-assisted organization and supplementary examples. Prepared from Joe McKenna’s workshop.