Published on <a href="http://ift.tt/2ntcu2K">| Prototyping: From UX to Front End &mdash; Medium</a> Rob McWhirter 
<blockquote>Your library can look good, but if the content is poorly structured, the whole thing will fall down.</blockquote>
<img alt="" src="http://ift.tt/2op7qRI">
A Knowledge Library is a place for people to access the information they need to do their job.
People<a href="http://ift.tt/2nvZqdN"> are not looking for miracles; they just want to find stuff quickly</a> — but too often information is out of date, impossible to find or just plain inaccurate. It takes careful planning and management to get it right: in this post I’ll outline the four steps that you need to take to produce an excellent content library.
<h3>1. Taking stock of what you have</h3>
Thou shalt not blindly copy articles from thy old system.
<a href="http://ift.tt/1F1WLMH">Twine</a> (the product I work with) doesn’t have an auto import feature — that’s because moving to a new platform is an opportunity to review your content and clean it up. Over the years, content will have become out of date, inaccurate or irrelevant and if this persists on the new Knowledge Library, it will loose credibility as a reliable source of information. Now is the perfect time to rectify this.
Review your existing content by performing a full audit, sifting through your content, working out what you have, what you need and what you don’t. You can use as little as a pen, some post-it notes and a spreadsheet to do this; your aim is to sift out what’s valuable and fix or delete the rest. Be ruthless.
It’s not exciting, it is time intensive and it takes careful planning to get right. But — it is well worth it. <a href="http://ift.tt/11GVuWl">How to Conduct A Content Audit</a> is a good, free introduction to the content audit process and Kristina Halvorson’s excellent book, <a href="http://ift.tt/2nYTaP6">Content Strategy for the Web</a>, is the one if you really want to swat up on the art of content design.
<img alt="" src="http://ift.tt/2owyjQZ">
<h3>2. Structuring categories</h3>
After you’ve revised what you have, you want to consider how you are going to organise your squeaky clean content. Your users need to find the content they need as quickly as possible, and it’s your job to make sure they can. To get this right, you’ll need to plan a category structure that is easy to navigate and flexible enough to expand on in the future. We call this structure the information architecture.
Your content audit should have given you a good idea of what content you have, so now it’s time to categorise it. The Neilson Norman Group has produced a <a href="http://ift.tt/2h3gMfn">great report </a>covering failures and successes when it comes to Knowledge Library IA. Some of NNG’s advice is:
<ul>
<li>Use clear labels and avoid broad terms and jargon. “Unclear naming is one of the biggest and most important projects to tackle when it comes to the IA”</li>
<li>Organise the categories by task or topic (rather than department). “Task-based structures often better withstood organisational change”</li>
<li>Limit number of categories. “<a href="http://ift.tt/180hl0T">Too many categories can make it difficult for users to choose a site area</a>”</li>
</ul>
<img alt="" src="http://ift.tt/2oppYBc">
<h3>3. Creating articles</h3>
Now you’ve got the skeleton in place, it’s time to put some meat on it. This means acting on what you’ve learnt in the content audit to produce new content where information is missing, updating old content to be accurate and making sure that all articles have a consistent style and layout.
Some words of wisdom:
Avoid PDFs where possible — their contents will not show up in search and can be difficult to download if using a mobile device. Of course, they can be useful for things like printable forms. However, if the content in the PDF can be consumed just as easily on a web page, get it out of there. See <a href="http://ift.tt/1xgmvOd">PDFs V HTML</a> for more info. And at the very minimum, put in a short introduction to what the files are about (this helps with search).
Consider using video rather than words — this can work really well with things like instructional guides. It can be as simple as recording your screen, talking into a £20 microphone and guiding people through how to use a piece of software or process. It can be a much more personal way to teach, rather than having people read an instruction manual — it’s an underused medium in internal comms.
Make sure your style is consistent and coherent — Get your guidelines right (style, tone and voice) — it gets all your writers on the same page, writing in a consistent style. A style guide can come in really useful here, as can tools like <a href="http://ift.tt/HcGzh5">GatherContent</a> if you have a team of people working on the content at once. If you don’t have the time or resource to make your own style guide, have your team use <a href="http://ift.tt/1BUzSuP">GOV.UK’s </a>and you’ll be sure to produce concise and coherent articles.
Use consistent tags and keywords — Good, consistent tagging is vital if your articles are going to show up in searches. Search will use a combination of category names, article names, content and keywords/tags to produce results. To make sure that the right articles are being shown, you’ll need to tag articles thoroughly.
<img alt="" src="http://ift.tt/2owC3BP">
<h3>4. Keeping it all in order</h3>
Now you’ve got your content in order, it’s time to devise a plan about how you’re going to keep it that way. The number one complaint from companies that come to us is that their Knowledge Library is impossible to navigate; this is not because of the interface design, but because the content on it is out of date, irrelevant or duplicated.
You need to get three things right:
<ul>
<li>Keep articles up to date — put alerts on content that will go out of date. Twine has a little reminder tool in the edit page of each article that can help with this.</li>
<li>Listen to users — Gather feedback from users and review it regularly. Twine’s ‘Was this article helpful?’ feature (below) can flag up problem articles so you can investigate.</li>
<li>Look at the data — Link up Google Analytics and look at it often. This can show you popular pages and how users are flowing around the system.</li>
</ul>
UX Mag have some more <a href="http://ift.tt/LqUxaS">good advice</a> on this, and I’ve written about this topic in the post, <a href="http://ift.tt/2nYW2LP">The Case For Maintenance</a>. Both worth taking the time to read.
<img alt="" src="http://ift.tt/2opb8eb">
<h3>Above all, be ready for change</h3>
Organisations change, and with it so does their content. That’s why it’s important to leave yourself some room for new categories and articles when structuring your Knowledge Library.
Proactively planning ahead for this, and putting systems in place to monitor your content, will help make sure that your Knowledge Library remains a place where people can access the information they need to get their work done.
<iframe src="http://ift.tt/2kZ4o5P" width="800" height="400" frameborder="0"><a href="http://ift.tt/2lIYHWK">http://ift.tt/2lIYHWK</a></iframe><img src="http://ift.tt/2owB1WH" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="http://ift.tt/2op1NTq">Building a Knowledge Library — Step by Step</a> was originally published in <a href="http://ift.tt/2cAqCpx">Prototyping: From UX to Front End</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Building a Knowledge Library — Step by Step

Top Stories