How to write an abstract | My EASY formula with REAL examples
Based on Andy Stapleton's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use a consistent abstract sequence: background (1–2 sentences), a single focused problem statement, one-sentence methods, the top numbered results, and one-sentence implications.
Briefing
A strong abstract follows a predictable sequence: set context, name the exact problem, state the methods, report the key numbered findings, and close with implications that matter beyond the lab. That structure works across thesis abstracts, research reports, and peer-reviewed papers—even though length and formatting vary by field and journal.
The opening should do two jobs at once: establish the topic and pull readers in. The first sentence (or first couple of sentences) functions like an “establishing shot,” offering a broad, zoomed-out statement that still captures the research focus. Examples include framing water-based polymer nanoparticle dispersions as a route to tackling challenges in printing large-area organic photovoltaic devices, or noting that graphene has emerged as a material with a wide range of applications. After that initial scene-setting, a brief snapshot of the current literature—kept to no more than two sentences—signals what others have done and what techniques or approaches already exist.
From there, the abstract pivots to the hook: a single, clearly defined problem statement. The goal is to identify the biggest challenge the work addresses, even if the broader project solves multiple issues. The transcript emphasizes using a direct contrast—often via “however”—to highlight the gap. One example argues that atomic force microscopy has produced inaccurate thickness measurements for single-layer graphene, with a wide spread of reported values. Another example frames the core issue as performance: efficiencies of nanoparticle-based devices lag behind corresponding bulk heterojunction devices, especially when switching from solvent-based to water-based approaches.
Next comes methods, distilled into one sentence that names what was done and how it was analyzed. The methods line can be broad—physical characterization, chemical analysis, or even surveys—so long as it points to the approach that leads to the results. Then the abstract delivers the numbered results: the most important quantitative outcomes, stated plainly with comparisons where relevant, but without burying the reader in technical detail. The focus is impact, not intricacy.
Finally, implications translate findings into what changes next. The closing one sentence should indicate whether the work corrects prior assumptions, suggests further investigation, or affects related areas of research. It should also be carefully scaled—avoiding grandiose claims—and tailored so the real-world significance is clear to the relevant audience.
A key nuance: some technical journals expect a different style. In highly specialized papers, the abstract may skip background and go straight to results in the first sentence, such as reporting that electrodes made from commercially available silver nanowires and single-walled carbon nanotubes achieve specific sheet resistance ranges and optical transparency percentages. Even then, the transcript recommends a practical strategy: create a journal-specific cheat sheet by reviewing the last several published abstracts in that venue (or a handful of top articles from the year) and mirror their structure so the submission matches what editors and readers expect.
Cornell Notes
A reliable abstract formula is built in layers: background (1–2 sentences), a focused problem statement, one-sentence methods, the top numbered results, and a final sentence on implications. The background sets context, the problem statement acts as the hook by naming the central gap or challenge, and the methods line signals how the work was done. Results should be stated directly with the most important quantitative comparisons, not exhaustive detail. The last sentence should explain what the findings mean for the field or further research, without overhyping. Some technical journals deviate by requiring a results-first abstract, so matching that journal’s norms matters.
What should the first sentence(s) of an abstract accomplish, and how specific should it be?
How does a strong problem statement work, and why does it matter?
What level of detail is expected for methods in an abstract?
What makes results effective in an abstract?
How should implications be written to avoid overreach?
What should writers do when a journal’s abstract style differs from the standard formula?
Review Questions
- What is the recommended order of components in a standard abstract, and what does each component do for the reader?
- Give an example of how a problem statement can be structured using contrast (e.g., “however”) and explain why that hook is effective.
- When would an author consider skipping background in an abstract, and what practical method helps match a journal’s expectations?
Key Points
- 1
Use a consistent abstract sequence: background (1–2 sentences), a single focused problem statement, one-sentence methods, the top numbered results, and one-sentence implications.
- 2
Write the first sentence as a broad, topic-setting “establishing shot” that still clearly signals the research focus.
- 3
Keep the problem statement tight and central, even if the broader project addresses multiple issues.
- 4
State methods in one sentence that names what was done and the main type of analysis, without trying to include every technical detail.
- 5
Report results with the most important quantitative outcomes and comparisons, selecting one or two key findings rather than exhaustive data.
- 6
End with implications scaled to reality—indicating what changes next (correction, further study, or field impact) without grand claims.
- 7
For technical journals that deviate from the standard structure, mirror that journal’s norms by reviewing recent published abstracts and building a journal-specific cheat sheet.