Being a Loud Technical Writer

To produce good documentation, we sometimes need to advocate for ourselves, our colleagues, our users, and our craft. This is easier said than done! Let’s explore how to be “loud” as technical writers. Being loud doesn’t mean being aggressive; it means making sure documentation work is recognized, valued, and aligned with broader business goals. We’ll share success stories, challenges, and ideas for next steps.

We'll use Zoom for this meetup. Register to receive the Zoom link here in the event description on the morning of the event. Then, when you log in to Zoom for the event, be sure that your Zoom name matches the name you used in your registration.

Want to get notifications about our events? Follow the instructions in the “About” section of the meetup home page (tip: you might need to select "Read more" to see the full text!).

Discussion topics:

• What does “loud” mean to you, and when have you been loud?
• Do you highlight your own accomplishments? The accomplishments of your colleagues? Both?
• What types of accomplishments have you highlighted? How did you choose these accomplishments instead of others?
• What are the benefits of talking about the things you’re proud of? Potential drawbacks?
• What are some of the results you’ve seen?
• Can company culture influence how loud you are?
• Are there times when being loud is not a good idea, or times when you must be loud?
• How do you communicate the impact and value of your work to colleagues who aren't tech writers?
• Some people find it’s difficult to show off their good work. What are a few comfortable ways to ease into the practice?
• What can we do to support our quieter colleagues so they can get their voices heard?
• Another way to be loud: How often do you speak up when something outside your area of control needs to be improved?