Conclusion

so far, this playbook has shown technical writing the way it should be, in a company that knows how to appreciate what we bring to the table things are not always rosy, though, and this guide would not be complete without the dark side oftentimes, documentation is an afterthought and the technical writer is seen as "less than", just an editor, someone who can be overlooked sometimes processes are chaotic and the technical writer is never notified of changes less technical technical writers can be looked down upon by engineers but when you're in a good place with good people ? technical writing is fun you get to learn new things every day you get paid to care about grammar and style you get to contribute a different point of view, maybe even find scenarios that no one thought of you get to be the link between the teams, gathering information from every source and bringing it together you get to support users achieve their goals without frustration even more satisfying when the user is internal and you can get that instant feedback! so if you think you fit the bill and this would be a job you'd enjoy, why not give it a try? written by ioana stanescu technical documentation manager