Technical authors are faced with limited time and resources, so they often are faced with the dilemma as to what to include and what to leave out of their user documentation. You may ask, if 80% read only 20% of the content, is there any value in documenting the rest?<\/p>\n

Technical Authors are often great advocates of\u00a0doing away with what\u00a0doesn’t add value in documentation. However, in an article “How normal is normal?<\/a>“, John Casti explains why extreme events like a killer hurricane\u00a0occur far more often than we think.<\/p>\n

So does this mean\u00a0that your rare and unusual topics in documents do need to described, after all?<\/p>\n

Casti\u00a0discovered there was greater likelihood to extreme values than we\u2019d expect from\u00a0bell-shaped, normal distributions:<\/p>\n

“Just as with the meltdown of the global financial system, the normal distribution dramatically underestimates the likelihood of unlikely events. Such events follow a different type of probability curve informally termed a \u201cfat-tailed\u201d distribution.”<\/em><\/p>\n

Indeed, he states Pareto’s (80-20) principle\u00a0is closely related to fat-tailed distributions:<\/p>\n

“In a normal bookshop, there might be around 100,000 titles on the shelves of which 80 per cent don\u2019t sell a single copy during the course of a month. Here the 80-20 Rule prevails. Now consider amazon.com, which has nearly four million titles available, or perhaps an online music site like iTunes, and ask how many of the titles they have available sell at least one copy in a month\u2019s time. The answer is not 20 per cent or 50 per cent or even 80 per cent. It\u2019s a staggering 98 per cent! Nearly every single title gets some action nearly every single month.”<\/em><\/p>\n

There are also implications regarding information architecture and site navigation in Casti’s article:<\/p>\n

“What\u2019s needed, (Chris Anderson) he says, is for there to be a functioning way to drive demand for those niche products out near the end of tail. First you need a \u2018head\u2019, consisting of a relatively small number of hits. Then comes a tail of many niche volumes, the kind only the author, his mother and a small band of fanatics and connoisseurs could ever love. So there must be not only a huge inventory of products, but also a way to direct prospective customers from the head to the tail by means of suggestions, background profiles from past purchases and all the other things a place like amazon.com does to match readers with the books they really want.”<\/em><\/p>\n

So does this mean that users navigate to the “niche” topics via the popular “head”\u00a0topics? Do\u00a0you need a “head topic” to bring the users in, with a filtering\u00a0and suggested topics mechanism to direct them to niche topics, to service any customer\u2019s wishes?<\/p>\n

I’m not aware of any user assistance-related usability studies that have looked into this.\u00a0Perhaps\u00a0there is, as Casti claims, “a lot more going on out on the \u2018fringe\u2019 than we ever imagined”. As more content is published online, and more Web analytics-derived statistics becomes available to Publications Managers, then perhaps we’ll find out.<\/p>\n","protected":false},"excerpt":{"rendered":"

Technical authors are faced with limited time and resources, so they often are faced with the dilemma as to what to include and what to leave out of their user documentation. You may ask, if 80% read only 20% of the content, is there any value in documenting the rest? Technical Authors are often great… Read more »<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[162,157,194,236,176,230,229,191,154],"tags":[276,294,258,262,295,264],"class_list":["post-471","post","type-post","status-publish","format-standard","hentry","category-documentation","category-survey","category-technical-communication","category-technical-documentation","category-technical-writing","category-usability","category-user-assistance","category-user-manuals","category-writing","tag-documentation","tag-research","tag-technical-author","tag-technical-communication","tag-usability","tag-user-assistance"],"acf":[],"yoast_head":"\n