Too Much to Read? Turn a Long Document Into a Useful Guide

What do you need to do with all that information?

You have the handbook, the reading or the procedure. What you need now is something you can use: a preparation checklist, a project guide, or a short explanation for someone encountering it for the first time.

In the workshop, I took an employee handbook and worked toward an onboarding checklist. First we looked at what was in the source. Then we chose a job for that information. That second step matters. A summary can tell you what a document covers and still leave you wondering what to do next.

My example used the historical 2012 Valve handbook as practice material. A proposed onboarding schedule is an adaptation of that material; it is not a statement of Valve’s current procedures. Keep that distinction when you work with your own source, too.

Read the complete screenshot text

Using only the employee handbook uploaded to this notebook, give a new reader a practical breakdown of the document so they understand what is in it and what they can do with it.

1. Start with two sentences explaining the document’s purpose and intended audience.
2. Create a concise table following the document’s actual structure. Use these columns: Section or topic; What you will find; How a reader could use it. Cover the major sections, combining minor sections where helpful. Cite the relevant handbook sections.
3. Suggest three useful tasks a new employee or onboarding coordinator could ask this notebook to do. Give one ready-to-use follow-up prompt for each.
4. End with a short What this document does not establish note. Distinguish content supported by the handbook from your proposed uses; do not invent policies or treat missing information as proof that no policy exists.

Use plain language and keep the whole answer under 500 words. Label the handbook as a historical 2012 practice example, not verified current company policy. Do not create a mind map, Canvas app, or code.

Give the guide a reader and clear source boundaries

What to notice: Listen for the intended reader, the instruction to disclose missing source access, and the request for supporting passages. Those choices make a draft easier to check.

1:24. From The One-Person AI Business, 43:10.60–44:34.60.

Visual context: Joe discusses the handbook checklist prompt on a shared Gemini screen. The important source-access, audience and citation instructions are spoken.

Know what you are working from

Start with the title, date or version, intended audience and main sections. Check that these match the file you meant to use. If the source is out of date, incomplete or meant for a different audience, a beautifully formatted guide can carry that problem forward.

You can attach a permitted document in Gemini using Add files → Upload Files. Google notes that large files can produce answers that miss details or connections. If that happens, narrow the exercise to one relevant section and retain any exceptions it depends on. See Google’s file-upload guidance.

Ask for a brief breakdown before assigning the guide. If that first interpretation needs work, use the checks in AI Missing the Point? Then decide what the reader should be able to do after using the result.

Give the guide one clear job

A new employee preparing for a first day needs different information from a coordinator arranging that day. A student planning an assignment needs different help from someone revising for a test. Name the reader and the action.

For example: “Make a preparation checklist for a new volunteer’s first shift.” That gives you a way to judge the result. Does it help that person arrive prepared? A general introduction to volunteering would miss the job, however well it reads.

Ask for a small first version. You can inspect six checklist items more easily than a twenty-page manual. If useful steps are missing from the source, ask AI to put those suggestions in a separate area. You can consider them without mistaking them for requirements.

Ask for a guide you can check

This prompt develops the workshop’s source, audience, task and evidence approach. Replace the brackets with your own details. It is an authored practice prompt, not a transcript quotation.

Use only the attached [document title and version] for source claims.
Create a short [checklist or guide] for [reader] who needs to [action].

For each item:
- State the action in plain language.
- Identify the source section or passage that supports it.
- Preserve any conditions or exceptions.

Put your suggested additions in a separate “Proposals” section.
Put important missing information in “Questions to resolve.”
Do not invent deadlines, responsibilities, page numbers or rules.
If you cannot access the source, tell me before drafting.

References help you find evidence; they do not settle whether a claim is accurate. Open the indicated passage. If the source gives a condition, the guide needs to keep it.

See how a source becomes a practical checklist

The source and checklist below were written for this article. They are not organizational policy or a captured AI response.

Now suppose a draft says to arrive at 9 a.m. It sounds reasonable, but the source does not give that time. Replace it with the instruction to check the confirmation email. “Attend orientation during your first week” is another problem: it weakens the requirement to complete orientation before independent work.

The guide is useful because it preserves the sequence and the exception. Merely making the source shorter would not guarantee either.

Check what was added and what disappeared

Compare the draft with the original in both directions. First, can you support each instruction in the draft? Then look through the source: did an important requirement fail to make it into the guide?

• Facts: verify names, dates, amounts, contact details and locations.
• Conditions: look for words such as before, unless, only and if. Losing one can change the instruction.
• Authority: separate the source’s requirements from your proposed way of organizing them.
• Usability: can the intended reader tell what to do, in what order, and where to get missing information?

For a course reading, a comparable adaptation might be a discussion-preparation guide: identify the author’s main claim, find supporting passages and prepare a question about an unresolved issue. Label questions you add as study prompts. Do not present them as the instructor’s assignment unless the assignment actually requires them.

Finish one guide you would actually use

Choose one familiar section of a document you are allowed to share. Name the reader, request a short guide and verify every action against that section. Correct one unsupported addition or omission if you find one. Keep unresolved questions visible.

Save the guide with its source title and version so you can revisit it when the original changes. If most of the draft is good and one part needs work, continue with targeted editing that protects the rest of the document.

Your finished result should answer a practical question: could this reader use the guide to take the next step, and could you show where each requirement came from?

Questions that come up

About this lesson

First-person teaching adapted from Joe McKenna’s September 29, 2026 workshop transcript. Joe demonstrates a document breakdown followed by a project guide and source-based onboarding checklist. Historical 2012 Valve practice source retained as historical. Volunteer source, checklist, prompt, course-reading application and review criteria authored for this article. No direct spoken quotations or claims of audio verification. Tool instructions checked against Google’s official help on September 30, 2026.

Source passages: 18:20–19:37; 29:39–33:50; 41:25–44:34. Source: The One-Person AI Business, September 29, 2026.

Official guidance checked September 30, 2026. Product features can change.

• Upload & analyze files in Gemini Apps — Google Help

AI-assisted organization and supplementary examples. Prepared from Joe McKenna’s workshop.