When the project is over, you can then spend some time to turn the terms list into a full-fledged style guide. Or integrate the list into the company style guide if it already exists.
Tip 8: Be a bridge builder
UX writers often work on multiple workstreams and develop unique cross-project insights. Why not share learnings and boost your visibility companywide? Lead the way with docs and meetings that bridge teams and help solve common problems together.
For example, are there multiple teams at your company that contribute menu items to your product’s context (right-click) menu? You can be the person who tracks these items in a single doc to make sure they are consistent and follow your company’s style guide.
Doing this shows your ability to not only craft words, but craft content strategy.
I’m kind of a geek for apps, so this is definitely my favorite tip of the bunch!
Whatever tools your team uses to track work—whether it be Git, Jira, Trello, Figma, Dropbox Paper, or something else, learn them. And ask team members to tag you in them when they have UX writing questions.
Others will see you being tagged and will learn to tag you, too. This raises your visibility.
And if you really want to go deep on this one, learn how to implement strings in code. (It’s one of the most fun things I’ve ever done.) After getting set up by a few awesome engineers, I can now reply to their tags right in the code, as well as update actual strings!
This allows you more freedom and flexibility in making UX writing decisions.