Jonatans blog has moved. You'll find it here: http://www.excosoft.se/index.php/about-us/blog/itemlist/user/46-jonatanl...

The latest post is about important aspects to consider as technical communicator when entering the new communication paradigm. You will write standalone answers to user questions. And provide filters to allow a user find answers. DITA maps used to organize topics in a static hierarchy for end user deliverables are not an option in the new communication paradigm. Such DITA maps belong to the old Gutenberg paradigm. Are you ready for the move?

Read more

Research has revealed that professional knowledge workers spend up to half of their productive time on searching and in many cases they do not find what they need. This is especially true for users of technical documentation, meaning that a lot of productive time is wasted on people searching in vain.

Read more

This blog post lists a number of questions asked by a technical communicator about SeSAM, trends in the technical communication inudstry and problems end users are facing when using technical documentation. Below you will find my answers.

Have you applied the SeSAM principles in documenting? What were your success points and what was the downside. 

Read more

There have been many discussions within OASIS DITA committees about discovering (and removing) the impediments to DITA adoption. It's probably fair to say that the discussions have discovered there are many roadblocks, but so far haven't resulted in clear ways to remove them.

Read more

Lately, there has been an interesting discussion about whether technical communicators shall consider organizational centric tasks and/or product centric tasks when writing end user assistance. The discussions are found here http://idratherbewriting.com/2011/12/26/using-tags-to-increase-findability/#comments and http://everypageispageone.com/2012/01/09/are-docs-a-responsibility-or-a-business-asset/. I will clarify my view in this blog post, but first some words about the process change taking place in our domain.

Read more