AI Writing & Creator Studio
How to write a how-to guide from a collection of sources — a step-by-step guide for academic researchers, PhD candidates, and graduate students who want to convert a methodology literature review into a reproducible, cited instructional guide for teaching or dissemination.
Academic researchers know how to execute methods that most of the people who could benefit from them cannot access. A PhD candidate who has learned Thematic Analysis (TA) through reading Braun and Clarke's methodological literature has assembled knowledge scattered across 6+ papers published between 2006 and 2022. A researcher who has learned systematic literature review methodology has synthesized guidance across the Cochrane Handbook, the PRISMA guidelines, and multiple implementation papers.
The problem is that this knowledge doesn't exist anywhere in a form accessible to a newcomer. The methodological literature describes procedures with the precision necessary for peer review, not with the clarity necessary for a first-time practitioner. Every graduate student who comes after faces the same synthesis challenge as the one before them — reading the same distributed literature, making the same mistakes, arriving at the same synthesis.
A how-to guide from your collection of sources converts that synthesis work into something shareable: a step-by-step instructional guide, grounded in the methodological literature, written for the specific audience that needs to use the method. It serves your lab group, your course participants, your conference workshop attendees, or — if published as a preprint or methods note — the broader community of researchers who need the method without the 6-month literature review.
An academic how-to guide is not a methods section. Methods sections are written for peer reviewers who need to assess whether your implementation was appropriate; how-to guides are written for newcomers who need to know what to do. The distinction produces completely different documents.
| Methods section | How-to guide |
|---|---|
| Describes what the researcher did (past tense) | Instructs the reader what to do (imperative voice) |
| Assumes reader knows the method | Assumes reader is learning the method |
| Organized for completeness and replication verification | Organized for learning — pedagogical step order |
| Passive voice and formal register | Active, second-person voice |
| Omits obvious steps (known to reviewers) | Makes every step explicit (needed by newcomers) |
| Citation style: inline academic | Citation style: adapted for pedagogical context |
Similarly, a how-to guide is not a literature review. A literature review synthesizes what the sources say about a topic; a how-to guide synthesizes what the sources say about a procedure and converts it into steps a newcomer can follow.
Audience 1: Lab group members The internal research team SOP (standard operating procedure) — a how-to guide for members of your lab who need to apply a method you've mastered. This is the most common and lowest-barrier use case. The guide doesn't need to be published; it just needs to be clear enough that a new lab member can follow it without asking you to walk through the method in person every time.
Audience 2: Teaching contexts A tutorial, workshop handout, or course supplement for students learning the method. This guide needs more explanation than an internal SOP — it assumes the least prior knowledge, defines all jargon, and includes more examples and common mistakes.
Audience 3: Research community dissemination A preprint, methods note, or tutorial paper published for the research community. This requires the most formal citation structure and the most explicit grounding in the published methodological literature. If you're adapting or extending the method beyond what the literature describes, you must clearly label those extensions.
Choose your audience before writing — it determines the level of jargon, the amount of background explanation, and the citation density the guide requires.
Before sequencing steps, survey your source collection for where the methodological literature agrees and where it doesn't:
METHODS SOURCE AUDIT
Sources in my collection on this method:
1. [Author, Title, Year, Journal/Publisher, Citation type: foundational / application / critique]
2. [Author, Title, Year, ...]
[...]
For each step or decision point in the method, note:
Step/Decision: [Specific step or choice point in the method]
Sources that describe this: [List]
Do they agree? [Y/N]
If yes: What's the consensus guidance? [Summary]
If no: What's the disagreement? [Describe the positions]
Can I resolve it? [Yes — explain why I prefer one / No — present both and give my judgment]
Foundational sources (the method originators or most-cited guides):
[List — these carry the most authority for describing the procedure]
Application/case study sources (practitioners who've applied the method):
[List — these provide grounding about what the method looks like in practice]
Critique/commentary sources (scholars who have critiqued the method):
[List — these inform the "limitations and caveats" section]
Most research methods have a small number of foundational sources — the original papers where the method was described, or the most-cited authoritative guides — and a larger number of application sources that describe the method as it was implemented in specific studies.
These two source types serve different purposes in a how-to guide:
Foundational sources → Define the steps and their rationale; establish the criteria for what constitutes correct application; describe the method's principles
Application sources → Demonstrate how the steps were executed in practice; show what decisions practitioners face; provide examples of what the method produces
Illustrative case (Thematic Analysis):
When conflicting guidance exists between foundational sources: the more recent foundational source typically takes precedence. When Braun & Clarke updated their guidance in 2019-2022 (shifting from "phases" to "process" and emphasizing reflexive TA), their updated guidance superseded the 2006 framing. Note the version distinction when citing.
The methodological literature almost never describes procedures in the order a newcomer should learn them. It describes procedures in the order they make logical sense — which is different.
Three ordering principles for pedagogical step sequences:
Principle 1: Execution order, not conceptual importance The most conceptually important element of Thematic Analysis is the analyst's active role in meaning-making. But you don't teach that first — you teach it after the student understands the phases, because "active role in meaning-making" only makes sense once they understand what they're making meaning from.
Principle 2: Prerequisites first A newcomer can't code data before they have data. A how-to guide that starts with "Step 1: Code your data" without establishing what they need before starting is structurally incomplete.
Principle 3: Decision tree before action Many research methods involve choice points — decision tree moments where the next step depends on an answer. A good how-to guide addresses decision points explicitly: "If your data collection is complete, proceed to Step 2. If you're conducting interviews, see the data sufficiency note before continuing."
The most common how-to guide failure mode for methods guides is describing what to do without specifying what a correctly completed step produces. A newcomer who runs the procedure without knowing what it should produce can't evaluate whether they've done it correctly.
For each step, the guide must answer: "How do I know I've done this correctly?"
VERIFICATION CRITERION FOR STEP [N]
What to do (action): [The step in imperative voice]
What correct completion looks like: [Specific, observable outcome]
What incorrect completion looks like: [What mistakes produce / what the wrong version looks like]
Source: [Which methodological source establishes this criterion]
Example from Thematic Analysis Step 3 (initial coding):
What to do: "Code the entire data set by assigning a label to every extract that is relevant to your research question. Do not pre-select extracts — code comprehensively."
What correct completion looks like: "You have a long list of codes attached to specific data extracts. The codes capture meaning rather than just describing content — not 'participant mentions time' but 'time scarcity as limiting factor.' The code list is more numerous than your eventual themes will be." (Braun & Clarke, 2021)
What incorrect looks like: "You have a small number of codes derived from your initial hunches about what the data should show. You have not coded the data that 'doesn't fit' — you've skipped extracts that seemed irrelevant. This is what Braun & Clarke call 'theme-centric' rather than 'data-centric' coding, and it produces themes that reflect the analyst's prior assumptions rather than the data."
Academic how-to guides require full citations, not paraphrase without attribution. Every non-obvious step and every criterion should be traced to its methodological source.
I'm writing a how-to guide on [specific method] for [audience: lab group / students / community].
Purpose: [Internal SOP / Teaching supplement / Published methods note]
Sources in my collection (organized by type):
Foundational:
[Author(s), Year, Title, Journal/Press, How it contributes to this guide]
Application:
[Author(s), Year, Study, What it shows about how the method works in practice]
Critique:
[Author(s), Year, What limitation or caveat it surfaces]
Steps I've identified (execution order):
Step 1: [Verb phrase + what correct completion looks like + which source establishes this]
Step 2: [Same structure]
[...]
Conflicts in the literature:
[Step or decision where sources disagree + how I'm resolving it]
Draft a how-to guide:
- Title: "How to [Method]: A [beginner's / practitioner's / step-by-step] guide"
- Intro: What the method is; what output it produces; what NOT to confuse it with; audience
- Prerequisites: what the reader needs before starting
- Steps in execution order with:
- Imperative voice actions
- "What correct completion looks like" for each step
- Inline citations for non-obvious steps: "[Author, Year, p. N or section]"
- Common mistake for each step with source if available
- Decision tree where the procedure branches
- Limitations section (from critique sources)
- Full references at the end (academic citation format)
Citation style: [APA / MLA / Chicago / discipline standard]
Context: A second-year PhD candidate in organizational psychology has read the primary methodological literature on Thematic Analysis for her dissertation. She's asked to run a half-day workshop for incoming first-year PhD students who need to understand qualitative methods for their own dissertations.
Her source collection:
Step list from her synthesis (execution order):
Before (from the foundational paper — written for researchers):
"The six phases of thematic analysis [from Braun & Clarke, 2006]:
- Familiarizing yourself with your data
- Generating initial codes
- Searching for themes
- Reviewing themes
- Defining and naming themes
- Producing the report"
Accurate, but written for researchers who already understand qualitative methods. No guidance on what each step looks like, what correct completion looks like, or what mistakes to avoid.
After (how-to guide for PhD students):
How to Do Thematic Analysis: A Step-by-Step Guide for Qualitative Researchers
What you'll be able to do after this guide: conduct a Thematic Analysis of a qualitative data set — typically interview transcripts, focus group transcripts, or open-ended survey responses — producing a set of themes supported by data extracts and a written-up analysis.
What this guide covers: Reflexive Thematic Analysis as described by Braun & Clarke (2006; updated 2021). This is the most widely used qualitative analysis method in psychology and social sciences.
What this guide does NOT cover: other forms of thematic analysis (framework analysis, IPA, grounded theory); data collection; interview methodology; how to write up findings for a specific journal format.
Prerequisites: a completed (or substantially complete) qualitative data set; a research question that your analysis addresses; familiarity with the constructivist epistemological position that Reflexive TA assumes.
Phase 1: Familiarize yourself with the data.
Read all of your data before coding anything. If you have interview transcripts, read them in full. Take notes as you read — initial impressions, patterns you notice, things that surprise you. Do not begin coding.
Why before coding: "Thorough familiarity with the dataset is a prerequisite of quality thematic analysis." — Braun & Clarke (2006, p. 87). The temptation to begin coding immediately leads to shallow engagement with data you haven't absorbed as a whole.
What correct Phase 1 looks like: You've read all transcripts at least once. You have a page of rough impressions — patterns you noticed, things you didn't expect, initial hunches. You have NOT organized these impressions into themes yet.
Common mistake: Starting to code immediately after the first interview transcript, before you've read all data. This produces a coding scheme shaped by the first few transcripts rather than by the full data set.
Phase 2: Generate initial codes.
Read through your data again and assign codes to every extract that is relevant to your research question. A code is a label — typically 2-5 words — that captures what is meaningful about a data extract. Code comprehensively: do not pre-select which parts to code.
Critical distinction: Initial codes are data-level labels, not theme-level labels. "Time constraints mentioned" is a code. "Work-life imbalance as barrier to [health behavior]" is a theme. Phase 2 codes should describe data, not interpret it.
What correct Phase 2 looks like: "You will end up with a long list of codes, probably more than 100 for a full data set, many of which may seem repetitive or minor. This is expected — you are mapping the terrain of the data, not summarizing it." (Maguire & Delahunt, 2017, Section 4)
Common mistake: "Theme-centric coding" — approaching the data looking for evidence of themes you already have in mind, rather than generating codes from the data. Braun & Clarke (2021) identify this as the most common error in student TA work.
[Continues for Phases 3-6]
References: Braun, V. & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. Braun, V. & Clarke, V. (2021). Thematic Analysis: A Practical Guide. SAGE. Maguire, M. & Delahunt, B. (2017). Doing thematic analysis: A practical, step-by-step guide. Echt: The All-Ireland Journal of Teaching and Learning in Higher Education, 8(3), 3351-33514.
Foundational citations for each step; "what correct looks like" for each phase; common mistakes from the application literature; accessible for newcomers without losing methodological accuracy.
A how-to guide from your collection of sources converts the synthesis work of a literature review into an instructional artifact that outlasts any single research project. Researchers who have mastered a method through extensive reading hold knowledge that newcomers to their field need — and that is currently forcing each newcomer to repeat the same synthesis from scratch. The how-to guide format distributes that knowledge efficiently: grounded in the foundational literature, illustrated by application sources, honest about conflicts, and written in the pedagogical step order that actually enables practice rather than the logical order that makes sense to an expert. The result is reproducible knowledge that can be verified against its sources and improved as the methodological literature develops.
More WebSnips articles that pair well with this topic.
How to write a how-to guide from competitor research — a step-by-step guide for founders and solo operators who want to convert competitive intelligence into instructional content that teaches their audience how to succeed at the task their product helps with.
How to write a how-to guide from your bookmarks — a step-by-step guide for knowledge workers and consultants who want to convert an accumulated reading list into a single, comprehensive methodology reference that consolidates the best guidance from across their practice area reading.
How to write a how-to guide from your clipped articles — a step-by-step guide for marketers and SEOs who want to turn a swipe file of clipped industry articles into a comprehensive, cited instructional guide that outperforms any single source they've read.
How to write a how-to guide from your highlights — a step-by-step guide for students and lifelong learners who want to convert book and paper highlights into a practical, cited instructional guide that teaches a method they've been studying.
How to write a how-to guide from your reading notes — a step-by-step guide for students and lifelong learners who want to convert personal study notes into a practical, cited instructional guide that teaches what they've learned through application.
How to write a product description from a collection of sources — a step-by-step guide for academic researchers and PhD candidates who need to translate diverse evidence sets (papers, datasets, reports) into commercial product copy that converts.