Document quests: a clear, useful handoff
A document quest needs a reader, a purpose, and a clear source boundary. Specify what the document must explain and how it should be delivered. The examples below are possible briefs, not promises of existing listings.
Deliverable ideas
- Write a practical guide: Turn an agreed process into a guide for a named audience, including prerequisites, ordered steps, and common failure cases. Deliverable: A DOCX guide with a checklist and references to supplied material.
- Summarize a source pack: Condense a fixed collection into key findings, decisions, and unresolved questions. Keep each conclusion traceable to its source. Deliverable: A concise brief with source references and a list of unresolved items.
- Reorganize an existing document: Apply a supplied outline and terminology list, remove repeated passages, and flag conflicting statements for the author to resolve. Deliverable: A revised document and a short change log explaining substantive edits.
Scope the quest
- Name the reader and purpose: Describe who will use the document, what they should learn or do, and the required length and level of detail.
- Set the source and style rules: List the material to use, required sections, terminology, and citation expectations. State whether additional research is within scope.
- Specify the delivered format: Choose an editable or final format and any template requirements. For separate sections, define how they fit into the complete document.
Review the delivery
- Check fidelity to the sources: Verify names, numbers, quotations, and conclusions against the supplied material. Missing information should be flagged rather than invented.
- Read it as the intended audience: Check the required sections, sequence, terminology, and prerequisites. For a guide, walk through the steps to find missing instructions.
- Open the actual deliverable: Inspect headings, tables, links, and exported layout in the agreed format. Point revision feedback to a section and its acceptance criterion.