It’s clear that technical understanding is important for technical writing. However, compared to the developer, a change in perspective is necessary. After all, to the end customers for whom the technical writing team is ultimately producing the content for, it is less important how the product is designed rather than what they can actually do with it. In essence, this means to create successful manuals, technical writers must focus on the functionality, the usage situations, and of course the possible dangers. They therefore bring the customer’s perspective into the development process, ideally ensuring better usability and preventing “over-engineering”.
In their everyday work, this means linguistic expression and didactic skills are even more important for technical writers than their access to the technical basics of the product. This is where certain questions arise, such as: “How can a text be written so that it is easy to translate?”, or: “What does minimalism mean for a user manual and what are the consequences for documentation?”. These are just a couple of examples of the many questions that need to be answered entirely regardless of the technology. This is because much of what is built into a product is never seen by the customer, so it’s irrelevant to them. But what can be done with the product is not necessarily obvious from the components – and neither is the question of how to create the manuals reliably and efficiently.