A technical writer has a key role within a company. He works with people with various functions. He’s asking developers for advice and feedback to build the user guide of their product. He’s connected and dealing with every part of the team: developers, testers, managers, product experts, etc. to produce documentation that is as clear as possible for the user, and depending on the product, the user’s life can depend on his work. Most of the time, this interaction is a very rich and fulfilling experience.
But how to find the right place between the different services of a company? Communicating with developers is not always easy: they often don’t have time to spend with a technical writer. Receiving feedback from testers can be troublesome, sometimes you don’t get information unless asking clearly for it. Many uninformed people think that being a technical writer is just writing sentences and that anyone can do it. It happens sometimes that even people in their own team don’t recognize the work and the importance of the technical writer. This article explores the difficulties a technical writer can encounter when working with experts.

Read the full article in PDF: What are the Stakes and Difficulties of Working with Experts?