I’ve never thought of Shakespeare in the context of technical writing, but in this article Josh Stubbs makes the connection. It’s a great article and definitely worth reading – you’ll probably learn something about Shakespeare you didn’t know and it’ll help you with your documents as well.
There is no doubt that William Shakespeare was an extraordinarily gifted writer but his document control left room for improvement.
This article will show several document control mistakes that Shakespeare made and describe why the issue is still relevant to technical writers 400 years later
#1 KING LEAR – Not Uniquely Identifying Each Document and its Release
Shakespeare produced two different versions of King Lear. Between these two versions there are nearly 300 different lines of dialogue that significantly affect the over all tone of the play.
Scholars have debated which was the Bard’s preferred version. Was one the fully realized tragedy exploring the themes and ideas to their conclusion or was the other a more direct and visceral plot meant to capture the attention of wandering groundlings?
WHY IT IS RELEVANT
Readers will make their own assumptions about the various drafts of your document and use their own method to determine several documents with similar names. A reader will naturally assume that a document is complete if it is labelled “Final Draft” or “Final Draft (2)” and they do not know that there is FINAL Final Draft or a Final Draft (3).