It’s a casual post, but I very much enjoyed and happily recommend Mark Tushnet’s post today speculating about why his article on art and the First Amendment didn’t place as he might (reasonably) have expected it to. I especially like this portion of the post:
3. I hate “roadmap” paragraphs, and don’t write them on my own. My particular bête noire is this: “Part VI concludes,” which is to say, “The Conclusion concludes.” [What else do you expect a conclusion to do?] The article as published has one, because I will go along with editors’ requests. But, maybe the editors figured that the judgment reflected in the absence of a roadmap paragraph would translate into recalcitrance during the editing stages, and again, why borrow trouble? (Note to law review editors reading this: It doesn’t; I’m really easy to edit.)
4. The article doesn’t have a strong normative conclusion. It doesn’t say that the Supreme Court has completely messed up in its treatment of art and the First Amendment. And, indeed, it says that the Court may have gotten it basically right, though the reasons are more complicated than people tend to assume. So, the reaction might be, “Why bother to go through all this to say that the law is basically in the right place anyway?” – particularly on a question that nobody seems to have raised anyway. (That is, maybe you can publish an article saying that the Court’s basically right when someone else has written one saying that the Court’s messed things up, but without the predicate article no one’s going to care that you’ve “defended” the Court’s results.)
Nicely written. Although I agree with both paragraphs, I’m moved to comment on the first.
I almost always use roadmap paragraphs. In reflecting on Mark’s post, though, I must say there is an argument to be made that roadmap paragraphs are a fairly nice illustration of some of the most risible aspects of legal scholarship. Clarity in writing, scholarly or otherwise, is of course essential. But a paper that lacks clarity in general isn’t going to find it because of the insertion of a roadmap paragraph. (I wince as I write those words.) That’s like a surgeon trying to fix massive spinal injuries by inserting a safety pin and a wad of chewing gum into the patient.
If legal scholarship was written to aid and persuade judges, perhaps a roadmap paragraph would be a wise strategy. But: 1) every time some judge sneers at legal scholarship for being unhelpful to judges, many legal scholars respond that they’re engaged in scholarship for broader purposes, not simply to serve as advocates or secondhand law clerks; and 2) in any case, if your paper is long and complex enough that it needs a roadmap paragraph, you have probably already failed at the task of aiding or persuading judges, or indeed just about anyone else outside the legal academy.
Which leaves those inside the legal academy. But if the experts in your field need a roadmap paragraph from you, there is already a good chance that 1) your paper needs to be rewritten anyway, or 2) there is something wrong with the experts in your field.
That leaves us with what I suspect most legal scholars would agree is the number one reason why they use roadmap paragraphs: because they think that law review editors need and/or expect them. Except that law review editors now also commonly expect, and regularly publish, abstracts — which summarize the paper! (And which also appear on SSRN, even when they don’t appear in the print version.) So the roadmap paragraph is really quite useless. Unless your article itself is overly long and complex. Which, come to think of it, most legal scholars would probably agree is the number two reason for the prevalence of roadmap paragraphs in legal scholarship.
Posted by Paul Horwitz on April 12, 2012 at 10:38 PM
Comments
The only reason for the roadmap is that many (most?) law reviews abhor the table of contents. In my view, anything with more than 15 pages needs one. Why do law review editors fail to understand that an 80-page article without a TOC is extremely hard to navigate and will therefore not get cited a lot?
Posted by: ForeignPrawfintheUS | Apr 15, 2012 2:45:18 PM
FWIW, as a law review editor, I love the roadmap. After the title, it is usually the first thing I look at, and, in the submission process, helps readers at least identify what the author intended to include in a section. I agree with Paul that a good roadmap won’t make better a bad paper; but that doesn’t mean that a good roadmap also won’t improve a good paper.
Posted by: Brad A. Greenberg | Apr 14, 2012 7:47:42 PM
A little off topic, but I think the Tushnet piece might have been hard to place because of the crazy number of permissions you’d need to get for the art. It’s beautiful, sure, but it might scare me as an editor who hadn’t much experience with reproducing copyrighted material.
Posted by: Matt Bodie | Apr 13, 2012 2:10:12 PM
I agree in advance with whatever Pierre Schlag has to say about it.
Posted by: Jeff Lipshaw | Apr 13, 2012 12:03:31 PM
Or, roadmap to my comment: what James said.
Posted by: Bruce Boyden | Apr 13, 2012 11:23:16 AM
I hate the roadmap paragraph in its standard form. I don’t like writing them — it feels like a sell-out to sloppiness — and I only read them as a poor substitute for a table of contents (if the article needs a concise roadmap paragraph, then what it really needs is a TOC, IMO).
However, there’s nothing wrong with “roadmapping” the article in the introduction — I just think it’s more artfully done *in more than one paragraph*. That is, somewhere towards the end of the introduction I think it’s useful for the author to start laying out how the argument proceeds. It’s the equivalent of the “summary of the argument” section in a brief. A minor annoyance writing the intro that way incurs, however: law review editors will often then request citations for all of the unsupported statements in your summary (the ones that, of course, are explained in full later on), leading to an incomplete duplicate set of the authorities cited later on being provided in the introduction.
Posted by: Bruce Boyden | Apr 13, 2012 11:20:19 AM
DHMCarver’s point that a standard roadmap is “practically an annotated table of contents” is important. This is one reason why I prefer it when law reviews include tables of contents at the start of articles: they provide an immediately accessible map to the contents of the piece. It’s also a baseline of quality; good roadmaps rise above it. Thus, for example, an introduction could set up a problem and announce out the key insight that the paper will use to resolve the problem — and then use the roadmap to fill in the details of how the insight responds to the problem and survives possible objections. (This sort of a roadmap will typically span multiple paragraphs.) Another good kind of roadmap helps makes the taxonomic structure of the legal phenomenon under consideration clear. The key, I guess, is to understand the roadmap as a tool that is adapted to solve a particular kind of problem with a particular kind of structure, and try to attack that problem rather than fixating on the structure.
Posted by: James Grimmelmann | Apr 13, 2012 11:15:00 AM
Hate the roadmaps. The concept is fine — an introduction is supposed to sketch the outlines of the argument. But the “formal” law review roadmap is merely lazy writing, practically an annotated table of contents. I had read hundreds of academic articles in my prior incarnation as an historian, yet it was not until I started reading law review pieces when I entered law school that I found the stilted roadmap style, which to this day reminds me of how one would write an elementary school research essay.
Posted by: DHMCarver | Apr 13, 2012 10:51:39 AM
I hate, hate, HATE “Part IV concludes,” too. And I’m not a big fan of roadmap paragraphs in the introduction, either, though, like Mark, I always include them when editors ask me to. I do think that such paragraphs are more helpful when the structure of a piece is particularly complex or intricate; my pieces tend to have a simpler — perhaps more simplistic and less interesting — structure.
Posted by: Sam Bagenstos | Apr 13, 2012 9:47:33 AM
Six comments in less than twelve hours for a post that went up at 10:30 pm! I’m not surprised. I should say first that I was definitely venting spleen at a late hour and definitely exaggerated my argument. So, for what it’s worth, I agree that roadmap paragraphs are not the root of all evil. That said, I’ll push back a bit.
I sympathize with Dan’s view that legal scholarship often involves formal constraints and, as with jazz, we can find freedom within and sometimes because of those constraints. Up to a point! Or three points, actually. The first, and this was largely the point of my post (if it had one), is the point at which form ceases to follow function. The function of the roadmap paragraph is clarity and summary. But the more abstracts (which are often better written and serve the purpose of introducing and summarizing the paper more clearly and thoroughly) become the norm, the less the roadmap paragraph serves a vital use. Then it becomes a matter of form dictating form, if not function itself. It becomes a third kidney.
The second point, and to some degree this is a response to Orin, is that the functional contribution of roadmap paragraphs is to provide order, structure, clarity, and guidance. But I see plenty of articles (sometimes fairly well-placed ones) that are too long, too complicated, too disparate in focus. (I’ve written a couple of them! I don’t exempt myself from the criticisms of this post.) Hence the surgery metaphor. The real focus should be on a clear and readable piece of scholarship, and insisting on a roadmap paragraph for a piece that doesn’t need one because it’s clear, or needs much more fundamental structural surgery, again seems like a triumph of form over function.
The third point is that–as with jazz–sometimes you have to experiment with form, to break the mold, to try new things. That’s true both for growth as a scholar and because the function of the piece may dictate a different form. Then the insistence on particular conventions becomes a barrier to useful scholarship, not an aid.
That puts me pretty close to James and Adam. The roadmap is neither always nor never necessary or useful. It should depend on the piece, not on observing conventions for their own sake. And clarity should be the rule, not a particular formalized way of achieving (or still not achieving) it. When it is insisted on for its own sake, or to fulfill the real or imagined expectations of law review editors, then it can indeed expose the risible aspects of some of the material and intellectual underpinnings of our scholarly enterprise.
Posted by: Paul Horwitz | Apr 13, 2012 7:33:21 AM
The take home lesson for law review editors is that roadmap paragraphs are neither always required nor always unwarranted. Too often law review editors fall prey to conventions. Much of the point of scholarship is to innovate, and it would be foolish to hamstring authors in their efforts to innovate by unnecessarily limiting the forms in which they are permitted to do so.
I wrote, “I end with a brief conclusion,” in my April Fool’s Day post from earlier this month: http://prawfsblawg.blogs.com/prawfsblawg/2012/04/earning-the-title-of-your-article.html
So that should make clear what I think of those sentences. They are always unwarranted, at least when they are devoid of interesting content, as in my example.
Posted by: Adam Kolber | Apr 13, 2012 6:18:04 AM
I’m a little puzzled by the concern about how to “roadmap” the conclusion. In my experience, you don’t: The conclusion doesn’t add a new developed argument, so you don’t mention it as part of the roadmap. I guess you can add a snarky comment about how the Conclusion concludes, but it’s no more necessary that saying, “And after the conclusion, the next article will begin.”
Posted by: Orin Kerr | Apr 13, 2012 2:35:05 AM
As a reader, I disagree with Orin Kerr. Roadmap paragraphs are invariably canned and end up all looking the same (“Part XXXVI concludes”); much like a roadmap, they don’t really prepare you for following the actual road.
Why not just sketch out the argument in a series of steps?
“My argument has the following structure:
(1) All lawyers are idiots. (Parts II-LXVI) (2) You are a lawyer. (Part LXVII) (3) You sir, are and idiot. (Part LXVIII)
I conclude by demonstrating how (3), when viewed through a proper lens (viz, a Korsgaardian interpretation of Kantian ethics), requires the Supreme Court to banhammer you from life.”
Posted by: Anonsters | Apr 13, 2012 1:32:56 AM
I agree with Paul: the roadmap paragraph is a good example of a characteristic tendency in legal writing. It can be either effective or risible or both: everything depends on execution. I find that the start of a roadmap creates a natural pause in the rhythm of an introduction: it marks the crucial moment when the introduction expands outwards from setting up the issues to connecting them with the rest of the article. A plodding roadmap throws away the dramatic momentum that moment can yield. The best roadmaps recognize that they are a convention of the genre: they can do so sincerely or with a wink, but good legal writing works with those conventions rather than against them.
My current working draft’s roadmap includes the sentence “A brief Conclusion will do exactly what it says on the tin.” We will see whether the editors let me keep that one.
Posted by: James Grimmelmann | Apr 13, 2012 1:31:00 AM
I don’t think I understand the opposition to roadmap paragraphs. Sure, as an author, they’re boring to write. But as a reader, they can be pretty helpful to understand the author’s argument and the structure of the article — and you can easily skip them if you prefer.
Posted by: Orin Kerr | Apr 13, 2012 12:15:35 AM
Disagree. Love the roadmap (and view it as vital as an abstract). Law review articles are like jazz. Accept the perimeters and improvise within some settled forms. Get with the program, people.
FWIW, I fully agree with the heat over the asinine statement “Part VI concludes.” That locution I understand is risible. It’s worst when you draw attention to a conclusion that makes no effort to say anything of interest such as adverting to possible objections and replies…
Posted by: Markel | Apr 12, 2012 11:44:23 PM
Like this:
Like Loading...