Image

To-do list before you publish a Word doc

Without a moment’s hesitation, I can name the most stressful phase of documentation development. It’s pre-publishing. The tension grows when you realize the importance of the release. You try to do your best, but very often the stress plays a trick with you. You neglect misprints, broken links, and messed up page numbering. And these minor mistakes can make a huge trouble for you.

To be sure that your document is of the superb quality, follow the pre-publishing checklist. It covers every troublesome aspect of document pre-publishing and will help you not to miss a thing.

Continue reading

Metrics: useful resources

Sooner or later, each seasoned Information Developer starts wondering whether the quality of content produced can be measured. And so do Information Development Managers. However, in addition to content quality metrics, managers care about one more aspect—measuring the productivity of their department in order to improve and streamline their team efforts.

Thus, when thinking of developing and introducing metrics in your organization, you should think of at least two metrics to assess:

  • Content quality
  • Work productivity

Continue reading

Documentation Audit: Why and How?

Once you have lots of projects behind your Office’s back and a bunch of them in progress or yet to come, you start analyzing if anything could have been done better, quicker, and more efficiently.

Each documentation project is unique in its own way, but when you look closer, you can find that most of them follow processes, rules, and collaboration patterns that do not differ that much.

Therefore, we’ve built the documentation assessment process that proved its efficiency and improved the overall quality of our projects, not only at their final stage, but right from the start.

Continue reading

User behavior types vs. Hogwarts houses (Ravenclaw)

In documentation for software that covers a wide market, we – Technical Communicators – often make it our point to target an ‘average user’. You know, the one who is neither too sloth nor too attentive, interested in both the big picture and a specific check box, and honestly, this list is endless.

But the majority of users does tend to lean one way or the other and follow a different ‘content beacon’.

Being a Potterhead, I could not help associating different user behavior types with Hogwarts houses.
And guess what – they match like the Weasley twins.

Sort your users and learn how to create documentation that ticks for them!


Related articles

https://informaze.wordpress.com/2016/03/02/user-behavior-types-vs-hogwarts-houses-part-1/

https://informaze.wordpress.com/2016/03/16/user-behavior-types-vs-hogwarts-houses-part-2/

https://informaze.wordpress.com/?p=1178&preview=true

 

 

 


Continue reading

User behavior types vs. Hogwarts houses (Hufflepuff)

In documentation for software that covers a wide market, we – Technical Communicators – often make it our point to target an ‘average user’. You know, the one who is neither too sloth nor too attentive, interested in both the big picture and a specific check box, and honestly, this list is endless.

But the majority of users does tend to lean one way or the other and follow a different ‘content beacon’.

Being a Potterhead, I could not help associating different user behavior types with Hogwarts houses.
And guess what – they match like the Weasley twins.

Sort your users and learn how to create documentation that ticks for them!


Related articles

https://informaze.wordpress.com/2016/03/02/user-behavior-types-vs-hogwarts-houses-part-1/

https://informaze.wordpress.com/2016/03/16/user-behavior-types-vs-hogwarts-houses-part-2/

https://informaze.wordpress.com/2016/04/06/user-behavior-types-vs-hogwarts-houses-ravenclaw/

 

 

 


Continue reading

Slytherin

User behavior types vs. Hogwarts houses (Slytherin)

In documentation for software that covers a wide market, we – Technical Communicators – often make it our point to target an ‘average user’. You know, the one who is neither too sloth nor too attentive, interested in both the big picture and a specific check box, and honestly, this list is endless.

But the majority of users does tend to lean one way or the other and follow a different ‘content beacon’.

Being a Potterhead, I could not help associating different user behavior types with Hogwarts houses.
And guess what – they match like the Weasley twins.

Sort your users and learn how to create documentation that ticks for them!


Related articles

https://informaze.wordpress.com/2016/03/02/user-behavior-types-vs-hogwarts-houses-part-1/

https://informaze.wordpress.com/?p=1178&preview=true

https://informaze.wordpress.com/2016/04/06/user-behavior-types-vs-hogwarts-houses-ravenclaw/

 

 

 

 

 


Continue reading

Gryffindor wallpaper

User behavior types vs. Hogwarts houses (Gryffindor)

In documentation for applications that cover a wide market, we – Technical Communicators – often make it our point to target an ‘average user’. You know, the one who is neither too sloth nor too attentive, interested in both big picture and specific check box, and honestly, this list is endless.

But the majority of users does tend to lean one way or the other, follow a different ‘content beacon’.

Being a Potterhead, I could not help associating different user behavior types with Hogwarts houses.
And guess what – they match like the Weasley twins.

Sort your users and learn how to create a documentation that ticks for them!


Related articles

https://informaze.wordpress.com/2016/03/16/user-behavior-types-vs-hogwarts-houses-part-2/

https://informaze.wordpress.com/?p=1178&preview=true

https://informaze.wordpress.com/2016/04/06/user-behavior-types-vs-hogwarts-houses-ravenclaw/

 


 

 


Continue reading