Recently, I commented that "Conclusion" is a really boring heading for an online article's conclusion. Some charming writerly/usability friends suggested that, boring as it may be, if the heading preceded a conclusion, then it's both appropriate and usable.
Of course, I wanted to explore that further. Who wouldn't?
It's true that calling your conclusion "Conclusion" is a great way to indicate to users what they'll get out of that part of the content. But it's also boring. Yes, if your content is an academic piece or a formal document, then by all means, go ahead and let it end with a "Conclusion".
But what of these articles?
- Dye Your Cat for Christmas!
- How to Play the Spoons in Six Simple Steps
- The Banjo and the Buffoon—My Unforgettable Weekend
In these cases, a conclusion heading that reflects and rounds out the content will be more coherent for users than one that reads "Conclusion".
In fact, if that cat-dyeing article is any good, "Conclusion" is likely to be among the more jarring heading options,
viz.:
H1:
Dye Your Cat for Christmas!H2:
Why dye?H2:
What you'll needH2:
Let's get dyeing!H3:
Step 1: Wash the coatH3:
Step 2: Rinse the coatH3:
Step 3: Apply the dyeH3:
Step 4: The second rinseH3:
Step 5: Dry the coatH2:
Have a very meow-y Christmas!Yes, we could have called the conclusion, "Conclusion". But doesn't "Have a very meow-y Christmas!", while extreme (and extremely corny) for the purposes of example, seem more contextually relevant to the content here?
Isn't it likely to speak more directly to—and perhaps further endear our brand/the article's publisher to—the cat-dyeing readership?
True, "Have a merry Christmas" is a festive farewell, and that makes it an especially suitable closing heading—a heading that actually
implies the article's ending, and thus a
conclusion. But headings that imply a conclusion subtley, without stating it outright (and thus boringly), can be found for all content topics.
On the much-lauded social web, writing in context, with the sensibilities of readers in mind, should be seen as a good thing. It doesn't need to undermine the content's usability if it's done well. On the contrary, I think it can be used to
enhance content usability.