Give readers a map, not a diary
A methods explanation helps readers judge how much confidence to place in a finding. It does not need to recount every search, revision or spreadsheet adjustment. Start with the decisions that shaped the answer: what you examined, how you selected it and how you analyzed it. Readers can then connect your conclusion to the work behind it.
The right level of detail depends on the setting. A slide presentation may need two sentences and a note about limitations; a report may need a fuller methods section. In either case, aim to answer a reader’s likely questions: “Where did this information come from?” and “What did you do to reach this conclusion?” Include enough detail for someone to understand your approach, while keeping procedural detail that does not affect interpretation out of the main explanation.
Start with the question and scope
Before naming tools or techniques, state what the method was designed to investigate. Define the subject and the boundaries of the material you considered. For a project about how a school communicates deadline changes, for example, you might say that you examined announcements sent to students during one academic term. That is more informative than saying only, “We reviewed communications.”
Scope also includes what you left out when that omission affects the claim. If your review covered email announcements but not messages sent through a student portal, say so. This keeps a narrow examination from sounding like a complete account of every communication. You do not need to list every possible exclusion; focus on boundaries a reasonable reader might otherwise miss.
Explain selection and analysis in plain language
Next, describe how the material entered your study. Did you include every item that met a rule, choose examples to illustrate different cases or invite people to respond? Selection matters because a conclusion based on a defined set of records supports a different claim from one based on a few memorable examples. State the rule rather than relying on a label such as “sampled” or “reviewed.”
Then give the main analytical step. In the school example, a concise account might read: “We collected email announcements about deadline changes sent during the term, grouped them by the type of change and compared how prominently each message stated the new deadline.” This tells readers what was collected and how it was interpreted. If the grouping required judgment, add how you handled unclear cases—for instance, whether you set criteria before reviewing the messages or checked disputed classifications with another reviewer.
Name the limits that change the interpretation
A brief methods explanation should make room for its most important limitation. You might have incomplete records, a small number of interviews, inconsistent definitions across documents or responses from people who chose to participate. Such limits do not automatically make the work useless. They tell readers which conclusions are supported and which would require more evidence.
Be specific rather than offering a blanket disclaimer. “This review covers email announcements, so it cannot show whether students received the same information through the portal” is more useful than “Results may vary.” Match the strength of your conclusion to your method: a document review can describe what the documents say, but on its own it cannot establish what every recipient noticed or understood. Stating that distinction clearly can make a short presentation more credible.
Use a short template, then edit for relevance
When drafting, try this sequence: “To answer [question], we examined [material and scope]. We selected [items or participants] using [rule] and analyzed them by [main steps]. This approach can show [supported insight], but it cannot establish [important limit].” Treat it as a checklist, not a script. If a part is obvious from the surrounding presentation, you may not need to repeat it.
Finally, read the explanation beside the finding it supports. Check that terms such as “all,” “typical” or “caused” do not promise more than your methods can deliver. Replace vague verbs like “looked at” with a concrete action, and remove details that do not help a reader assess the result. The goal is not to make the work sound elaborate. It is to let someone see the path from question to evidence to conclusion.
