Guides and templates for writing up your research.
An introduction has two parts. The opening tells the whole story of your study in plain language. The rest steps back and builds the theoretical case, narrowing from the broad research area down to your research questions.
Each section below sits beside an excerpt from an example introduction on the reactivity of metacognitive ratings. Read the excerpts in order to see how the pieces fit together.
Part 1
Three short paragraphs that give the reader the whole study before any theory.
Situate the reader and set the context of the problem you are trying to solve.
When psychologists want to know how well people judge their own thinking, they usually just ask them. How confident are you in that answer? How likely are you to remember this later? These ratings appear in hundreds of studies of learning, memory and decision-making.
Specify the problem, and explain why it is a problem.
But asking the question may change the answer. A growing body of work suggests that making these ratings can change how people learn and perform. If so, the measure is altering the very thing it is meant to measure.
Explain how you are going to solve the problem in this study.
In this study, we compared people who rated their confidence with people who did not, to test whether rating changes performance on [task].
Part 2
Step back, then narrow down. Each section is a little more specific than the one before, until the reader arrives at your research questions.
Now step back and start with very general background. How far you step back depends on the length of the piece, but it is usually the research area.
Metacognition refers to the ability to monitor and control one’s own cognitive processes (Flavell, 1979).
Narrow to your research topic within that area.
Metacognition is most often measured with self-reported ratings, such as judgements of learning or confidence ratings, collected during or after a task.
Introduce the specific research problem your study addresses.
These measures rest on an assumption that is rarely tested: that asking for a rating does not change the processes being measured. When it does, the measure is said to be reactive.
Review what we already know about the research problem.
Organise this by idea, not by paper. Group studies around a finding or argument rather than giving each paper its own paragraph (“Smith (2019) found… Jones (2020) found…”).
Judgements of learning are now known to be reactive. Making them improves memory for related word pairs, but has little effect on unrelated pairs (Double et al., 2018; Soderstrom et al., 2015). Confidence ratings can also change performance on reasoning tasks (Double & Birney, 2017).
Set out what we don’t yet know about the research problem, and what we might expect to find.
Make the gap concrete. “No one has studied this” is not enough on its own. Say why it matters that we don’t know, and what the possible results would tell us.
However, it is unclear whether ratings are reactive in [context]. This matters because [why it matters]. If reactivity reflects a change in how people approach the task, we would expect [prediction].
Summarise the current study and your approach: how it will answer what we don’t yet know.
In the current study, participants completed [task] either with or without confidence ratings. This allowed us to test whether [gap].
Finish with your research questions, your hypotheses, or both.
We asked whether making confidence ratings changes [outcome], and whether any effect depends on [moderator].
The method should give another researcher everything they need to run your study again. Use these subheadings.
Claude or ChatGPT can write a good first draft of the method, especially if you ask in the same chat you used to build the task. It already knows the design, the trials and the exclusions. Check every detail against the experiment itself.
The results report what you found, without interpreting it. Save what it means for the discussion.
The same applies here. In the chat where you analysed the data, Claude or ChatGPT already has every number and can draft a solid results section. Check each number against your own R output before you use it.
The discussion mirrors the introduction. The introduction narrows from the broad research area down to your questions. The discussion starts with your answers and widens back out to what they mean for the field.
Once you have a full draft, use Claude or ChatGPT to review it with the prompts below. If you write in Word, the easiest way is the Claude plugin for Microsoft Word, which runs the prompts on your document and can leave its feedback as comments or make edits directly. Run the prompts one at a time, in this order. Doing them separately, rather than in one giant “check everything” prompt, gets you sharper, less generic feedback.
Read this draft as a critical reviewer focused only on the argument, not the writing style. For each claim I make, check whether it is actually supported by the evidence or reasoning I provide. Identify:
- Any claims that are unsupported, overstated, or not backed by what I've cited
- Gaps in the logical chain (where a conclusion doesn't follow from the premises)
- Circular reasoning or unstated assumptions I'm relying on
- Places where I've ignored an obvious counterargument or alternative explanation
- Any internal contradictions between different parts of the draft
For each issue, quote the specific sentence and explain the problem in one or two sentences. Do not comment on grammar, style, or formatting.Read this draft as someone unfamiliar with the topic. Assess:
- Whether the overall structure makes sense (does each section build logically on the last?)
- Whether the purpose of each paragraph is clear within the first sentence or two
- Any paragraphs that try to do too much or wander off topic
- Sentences that are unclear, ambiguous, or require rereading to understand
- Whether transitions between sections/paragraphs actually connect the ideas, or just sit there
Give me a short list of the 5-8 highest-impact issues, ordered by how much they hurt readability. For each, quote the passage and suggest a fix. Do not comment on grammar or formatting.Check this draft for internal consistency only. Look for:
- Terminology used inconsistently (e.g. switching between two terms for the same concept)
- Numbers, statistics, or facts stated differently in different places
- Claims made early in the draft that are contradicted or quietly abandoned later
- Inconsistent tense, voice, or level of formality across sections
- Inconsistent citation style or referencing format
List each inconsistency with both locations quoted side by side.Copy edit this draft at the sentence level. Fix:
- Grammar, punctuation, and spelling errors
- Awkward or clunky phrasing
- Unnecessary wordiness or redundancy
- Passive voice where active would be stronger
Do not change my arguments, structure, or content. Give me the edits as a list of "original -> revised" pairs, not a full rewritten draft, so I can see exactly what changed and decide whether I agree.Check this draft for minor formatting issues only:
- Inconsistent heading levels or heading style
- Inconsistent spacing, bullet/numbering style, or indentation
- Citation and reference list formatting errors (missing details, inconsistent style, references not matching in-text citations)
- Figure/table numbering or caption issues
- Any obvious layout problems (e.g. orphaned headings, inconsistent font/size cues if described in the text)
List each issue with its location. Do not comment on content, argument, or wording.