Writing a Book When You’re Trained to Write Journal Articles
On unlearning journal habits to build a book-length argument
If you’re a social scientist working on a book—whether it’s a dissertation-to-book revision or a new project—you may find yourself bumping up against an unexpected challenge. The writing conventions that served you well in journal articles don’t translate directly to the book genre. In fact, they can actively work against you.
This is something I see frequently with coaching clients from sociology, political science, communication, and other social science fields. They know how to write a strong journal article. But when they sit down to write a book, they default to the same structures—and then wonder why the manuscript feels disjointed or why readers struggle to follow the argument.
The good news is that this is a solvable problem. But it requires understanding that you’re working in a different genre, one that draws more heavily on humanistic writing traditions.
If you’ve published in the social sciences, you’re likely very familiar with the IMRAD format—Introduction, Methods, Results, and Discussion—which dominates empirical journal articles.
Each section has a clear job: the introduction frames the problem and literature, the methods explain how the study was conducted, the results present findings without interpretation, and the discussion makes sense of those findings and situates them in the field.
This structure works well for journals: it’s standardized, signals rigor, and helps readers and reviewers know exactly where to look. But books, especially those meant to reach beyond a narrow subfield, don’t work this way. Academic monographs already speak to broader audiences, and if you’re aiming for a crossover book, moving beyond IMRAD conventions becomes even more important.
Books—including academic monographs—draw on a different tradition.
Rather than separating evidence from interpretation, book chapters integrate them. Rather than cordoning off your literature review into its own section, you weave engagement with other scholars throughout your argument. Rather than saving your analysis for a discussion section at the end, you’re analyzing as you go, giving readers context and making sense of your findings the moment you present them.
Let me give you a concrete example.
In an IMRAD-style article, you might write something like this:
Results: Participants reported high levels of uncertainty about their employment status. Seventy-three percent indicated they did not know whether their position would exist in six months.
And then, pages later in the discussion section:
Discussion: The high levels of employment uncertainty reported by participants reflect broader patterns of labor precarity identified by Smith (2011) and Jones (2018). These findings suggest that gig economy workers experience chronic instability that affects not only their material conditions but also their sense of identity and future planning.
In a book, you wouldn’t separate these. Instead, you’d write something like:
The workers I interviewed lived in a state of perpetual uncertainty. Nearly three-quarters didn’t know whether their jobs would exist in six months—a pattern that reflects what scholars have called the “precariat,” a class defined not by what they do but by the instability of their relationship to work itself (Smith 2011; Jones, 2018). This uncertainty wasn’t just a practical problem to be solved; it shaped how workers understood themselves, making long-term planning feel almost absurd.
Do you see the difference? The book version presents the finding and interprets it in the same breath. It brings in relevant scholarship not as a separate literature review but as a way of making sense of what you’re showing the reader. The evidence and the analysis are interwoven.
When I work with social scientists who are new to book writing, I often notice them trying to preserve the IMRAD structure in disguised forms.
They want a standalone literature review chapter that surveys everything scholars have said about their topic.
They want a theory chapter that explains their theoretical framework before they’ve shown readers why it matters.
They want a methods chapter that describes their data collection in exhaustive detail.
And they want to save their analysis for later chapters, presenting “findings” first and interpretation second.
This instinct makes sense—it’s what you’ve been trained to do. But it makes for a less engaging book, one that asks readers to wade through extensive setup before they get to the payoff.
Books need to earn the reader’s attention continuously, not just in the introduction. Your book audience often isn’t just specialists in your subfield—it’s often students at various levels, scholars in adjacent fields, and perhaps even broader publics interested in your topic. They need to be pulled through by an argument, not handed a series of disconnected sections to assemble themselves.
In a book, the introduction does far more heavy lifting.
It’s where you establish the argument, introduce key concepts, and provide enough theoretical and methodological grounding to orient readers without tracing the full genealogy of every framework you use. Rather than separating theory and methods into standalone sections, you weave them into the setup of your intervention.
For example, instead of explaining Foucault’s governmentality in a discrete theory section, you introduce it as part of showing what your book argues and why that concept clarifies your topic. Methods are similarly condensed, sometimes supplemented by a brief appendix, offering just enough detail for readers to trust your evidence and follow your analysis.
There are exceptions—especially when developing or extending theory—but even then, a theory chapter should advance the book’s argument, not just summarize existing scholarship.
The shift I’m describing is fundamentally about integration.
In humanistic writing traditions—and in the book genre more broadly—you don’t separate your “results” from your analysis. You give context and make sense of what a finding means when you first present it. You bring in other scholars not to demonstrate that you’ve read them but because their ideas help illuminate what you’re showing the reader.
This means every chapter is doing multiple things at once: presenting evidence, analyzing that evidence, engaging with relevant scholarship, and advancing your overall argument. It’s more demanding to write this way, but it’s also more engaging to read.
If you find yourself writing a chapter that’s purely “here’s what I found” with no interpretation, or a chapter that’s purely “here’s what other scholars have said” with no connection to your evidence, that’s a sign you may be defaulting to IMRAD habits.
I want to be clear: writing in a more humanistic, integrated style isn’t less rigorous than the IMRAD format. It’s differently rigorous.
You still need to be systematic. You still need to ground your claims in evidence. You still need to engage seriously with existing scholarship.
But the rigor shows up differently. It shows up in the quality of your analysis, in the precision of your prose, and in your ability to weave together evidence and interpretation into a compelling whole. It shows up in an argument that builds and develops across chapters rather than findings that sit in one section waiting to be discussed in another.
If you’re a social scientist writing a book, you don’t have to abandon everything you know. But you do have to expand your repertoire, drawing on humanistic writing conventions to create something that works as a book, which is a sustained argument that pulls readers through from beginning to end.
Your task now is to adapt your familiar writing genre to a different genre—one with its own conventions, challenges, pleasures, and possibilities.