Imagine there is a change in corporate design at your company. Maybe the change is only a general attempt to optimize existing layouts. Maybe it entails a completely new corporate identity with a new logo and different colors. Or maybe your company has a new division that makes new products. Any change, no matter what kind, will have a direct impact on your technical documentation. The cover page needs to be redesigned, and the way headers and footers look will change – as will headlines, safety notices and warnings. It is practical when technical writers can make these layout changes themselves, without any programming skills or troublesome extra work.
If you ask Google about good reasons for starting a company blog, you will receive over 307,000,000 results: “5 good reasons for writing a company blog,” “10 good reasons,” “Why companies should have a corporate blog,” etc. According to them, a blog promotes customer proximity and makes those interested more aware of your company. It might even generate some enthusiasm on the part of highly qualified potential employees.
So every company with a healthy sense of self-esteem urgently needs a blog? Perhaps. But we are concerned with one thing above all. At our company, we work with a lot of experts that have a great deal of specialist knowledge about their respective fields: IT experts, technical writers, consultants, marketing experts, support staff, a number of partners from the higher education and private sectors, and – last but not least – our users. All of them have a lot of important expertise that we want to make available to everyone on our new blog. Our motto: No empty blah blah blah, just content with real added value.
Our goal: No background noise, just informative content
Melanie Kunas, DOCUFY GmbH
We see a blog as the ideal medium for exchanging specific information. And for us it is also explicitly about exchanging information between experts on the user side and experts on the DOCUFY side. There is no imminent danger of “content shock” (many channels, a lot of drivel about nothing). We’re not interested in background noise. What we want to do is take our stores of knowledge out of the basement and make them available to our users and anybody else who is interested – quite in line with the concept of Multi-Level documentation.