Methodology vs. methods in a research paper

Make design, procedure, and rationale traceable

1. Confirm section task and convention. Check prompt, field, journal, supervisor, and project stage; “methodology” may cover whole section or distinct rationale.
2. Re-state question and design boundary. Write precise question, objective, analytical focus, and design. Design must be capable of addressing question.
3. Identify materials, data, participants, or cases. State what was or will be examined, setting, eligibility, origin, selection route, and scope record.
4. Describe procedure chronologically. Explain collection, generation, extraction, observation, recruitment, measurement, coding, or document handling in evidence-path order.
5. Explain analysis path. Name how information was prepared and analyzed, what patterns or interpretations approach can address, and what it cannot establish.
6. Give proportionate rationale. Show why design, materials, procedure, and analysis fit problem. A task list or bibliography is not rationale.
7. State limitations and ethics honestly. Address access, sampling, privacy, consent, risk, permissions, approval requirements, and limits on claims as relevant.
8. Separate method from results and reverse-check. Keep findings and interpretation for Results or Discussion; check every procedure, source, analysis claim, citation, and ethics statement against actual project.

Fictional learning example

This fictional learning example is invented for practice; it is not real research, participant pool, source record, permission, ethics approval, analysis, finding, or template to submit. Fictional study used semi-structured interviews with first-year students to explore how they described adapting weekly planning routines around paid work. Fictional interviews were transcribed and analyzed thematically. Qualitative design was selected because fictional question concerned accounts of routine adjustment rather than association size. Example describes procedure and limited rationale; it does not report themes or interpret findings.

Keep the section boundaries clear

• Do not turn Methods into a literature review unless a methodological source is necessary to justify the choice.
• Do not report findings, themes, or interpretations before Results or Discussion when your discipline separates those functions.
• Do not describe a procedure as replicable unless you provide the transparency and detail your field expects.
• Do not claim causation, representation, or generalisability unless the design and sampling support that claim.

Use a discipline-aware definition

[USC Libraries](https://libguides.usc.edu/writingguide/methodology) explains that a methods section describes research actions and the rationale for procedures used to obtain and analyze information. Its guide distinguishes methods as technical steps from methodology as underlying reasoning for why particular methods were chosen. Requirements differ across empirical, qualitative, humanities, proposal, and thesis writing, so the course guide, journal, or supervisor remains controlling.