Start with an answerable question
A useful research starts from a decision. “I want to learn about customer support” is broad; “which recurring doubts can be answered with the available catalog?” defines a question and a base. Also write what will not be addressed.
Define the audience, period, and depth. A summary for deciding the next improvement needs less length and more clarity than a long-term survey. The research tool should serve the question, and not define the work just because it offers many types of output.
Why learn
A bounded question makes it possible to tell when the research is done. It also makes visible the gaps that require new material instead of more text generation.
✓ Do
Open the excerpts that support the answer.
✗ Avoid
Accept references without checking the content.
Key concepts
Build a coherent document set
Organize documents by topic, date, and responsible person. Remove duplicates and identify conflicting versions. An old catalog and an updated one may show different deadlines; the research needs to recognize that discrepancy.
Tools like NotebookLM can support reading a document set. Start with the flow available in your account and confirm the current features. If you choose a CLI, check who maintains it, your authentication, and help commands; do not assume that any integration is official.
Why learn
The quality of the answer depends on the material consulted. A sophisticated tool does not automatically resolve contradictory, incomplete, or out-of-context documents.
A way to apply
- Bound the question and select documents.
- Build a matrix of claims and evidence.
- Generate an output, review it, and record gaps.
Key concepts
Require location for the claims
Ask that each central conclusion come with a location: document, section, or identifiable excerpt. Then open that location and verify that it supports the statement. A reference may exist and still not demonstrate the claim.
Separate quotation, paraphrase, and inference. A quotation reproduces words; a paraphrase restates an idea; an inference connects evidence to reach a conclusion. In the report, make it clear when you are inferring something that does not appear directly in the documents.
Why learn
Traceability reduces the chance that a fluent response hides a claim without support. It lets someone else verify the analysis without repeating the entire research.
Question: what deadlines can I tell the client?
For each claim, provide:
- document and section that support it;
- whether it is a rule, exception, or inference;
- what cannot be concluded.
Output: report in English with up to 300 words.
Key concepts
Treat divergences as information
When two documents diverge, don’t take an average or silently choose the most convenient value. Record both, their dates, and the rule used to decide which one applies. If there is no rule, keep the question open.
In a workshop, the catalog might say five days and a recent message might mention three. The message could be an exception for a specific request. Without that context, turning three days into a general promise would be a mistake.
Why learn
Conflicts help reveal that a rule depends on conditions. Recognizing those conditions produces better answers than trying to eliminate all uncertainty from the report.
✓ Do
Distinguish general rule from exception.
✗ Avoid
Promise a condition that appears as a possibility.
Key concepts
Choose the output according to the task
A report is meant to go deeper; a presentation helps steer a conversation; a quiz checks understanding. Producing all formats at once increases revision work. Choose first what the person needs to use.
Defining language, length/format, and audience can change what you deliver. Then compare each output against the same evidence matrix. A presentation shouldn’t add certainties that the report doesn’t have. If you generate audio or video in another step, preserve the same content discipline.
Why learn
Changing the format can alter the meaning through excessive simplification. A shared baseline allows you to reuse knowledge without reinventing the facts with each delivery.
| Criterion | Expected evidence |
|---|---|
| Support | Each central claim has a location. |
| Conflicts | The divergence is explained. |
| Limits | The missing data remains explicit. |
Key concepts
Practice: answer without filling in gaps
Use the two fictional exercise documents and write a short response. Identify the standard deadline, explain the exception, and state which information still needs to be confirmed. Don’t turn a possibility into a guarantee.
Include two checking questions for whoever reads the dossier. They should measure understanding of the difference between rule and exception, not memorization of a sentence. At the end, record which documents were sufficient and which data were missing.
Why learn
Practice shows how to produce a useful answer even when the base doesn’t resolve everything. The dossier can guide the next question instead of pretending the matter is closed.
Your exercise
Document A, Catalog, section Deadlines: “Catalog organization: five business days after the complete files.” Document B, customer support message: “Maybe we can deliver in three days if the material arrives reviewed.” Which deadline should we communicate?
Download practice sheetCheck the commented answer
The documented deadline is five business days after receipt of the complete files. Three days is a conditioned possibility, not yet confirmed. Before promising the exception, confirm capacity and that the material is reviewed. Checking questions: when does the deadline start? What makes delivery in three days different from the rule?
Check your understanding
Two sources diverge. What conduct preserves research quality?
Key concepts
What stays from this module
A short report with questions, evidence, and visible gaps.
- ✓ Each central claim has a location.
- ✓ The divergence is explained.
- ✓ The missing data remains explicit.
Progress records your reading. The practice is completed when you check the submission.