Jonatan Lundin's blog
In pursuit of the ultimate techCom information architecture
Are you a technical communicator who are uncertain about what to write in a manual? Do you fear the subject-matter expert will question your competence as a professional communicator, as they might claim that users want something other than what you suggest? This guide helps you get started developing an information architecture, to become more comfortable asking a subject-matter expert for input. This will hopefully help you produce better technical documentation. Read more…
Watch how to create one (1) mobile-friendly web knowledge base from existing technical documentation books. This, without requiring any manual work to rewrite or re-structure the book content.
A “topic” can be defined in several different ways— a fact which often leads to inefficiencies in content management. This post is a presentation of what a topic means within the context of three different content delivery scenarios.
Practitioners find it difficult to see how the knowledge academics produce can be used to address real, practitioner-related problems. Why?
It goes deeper than academics failing to communicate with practitioners. The reason has to do with the fact that much of the academic research itself is weakly linked to the practical problems practitioners face. This fact is what makes practitioners uninterested in talking to academics— hence the gap.
Read more to find out how the gap could be bridged.
Are you struggling with information architecture itself: What type of information should be organized, and in which manual? In the summer 2015 edition of ISTC Communicator, I present an approach to help you settle the struggle. Based on a viewpoint that users search for answers, I offer tips on how to design for findability.