{"id":1240,"date":"2019-08-26T17:42:18","date_gmt":"2019-08-26T17:42:18","guid":{"rendered":"https:\/\/uxwritinghub.com\/?p=1240"},"modified":"2021-05-10T10:59:01","modified_gmt":"2021-05-10T10:59:01","slug":"ux-writing-internship","status":"publish","type":"post","link":"https:\/\/uxwritinghub.com\/ux-writing-internship\/","title":{"rendered":"Six takeaways from my six-month UX writing internship"},"content":{"rendered":"

When I was straight out of college, I was going about trying to figure out what I could do next, just like most people who graduated with me. However, there was one thing I was clear about – I wanted to write. Towards the end of my three-year undergraduate program in economics, mathematics, and statistics, I realized that I enjoyed working with words over anything, especially over working with numbers.\u00a0<\/span><\/p>\n

So, that summer, I started scouting for opportunities that would allow me to foray into writing. That\u2019s when I chanced upon this – \u201c<\/span>Freshworks<\/span><\/a> is looking for a UX writing intern for Freshdesk\u201d. Although I had heard about the company, I wasn\u2019t familiar with the words \u2018UX writer\u2019. Nor did I have prior work experience in writing. So, I was convinced that I stood no chance of getting the internship. I decided to test my luck anyway.\u00a0<\/span><\/p>\n

\"freshwork<\/p>\n

Freshdesk office, picture by Glassdoor<\/em><\/a><\/p>\n

A few weeks after applying, I heard from an HR at Freshdesk, soon after which I had to go through the tests and the interviews. By then, I had a fair understanding of what a UX writer does (it seemed both interesting and intimidating). Much to my surprise, I was offered the internship!\u00a0<\/span><\/p>\n

Fast forward six months: I realized that applying for the internship was the best decision I\u2019ve ever made. I met a bunch of awesome people who I learned a lot from \u2014 about product development, design, collaboration, and of course, UX writing. While I\u2019d like to talk about it all in detail, I\u2019m going to discuss the most important things I learned. In this article, I\u2019ve charted out six takeaways from my six-month UX writing internship.<\/span><\/p>\n

1. Write copy when the feature is still in design.<\/b><\/h2>\n

Since I was the first UX writer in the company, we were yet to perfect the process of writing copy. For instance, in the initial few months of my internship, I would review the strings committed in the en.json and en.yml files. After which, I worked with the developers to change the copy and the changes were pushed in the next development cycle. The downside of this process was the time-lag between passing feedback on copy and the changes being reflected in the live environment (as the developers had other things on their plates).<\/span><\/p>\n

Gradually, we realized that the best time to write copy is during design. It was easier to change the copy in design than it was in development. Plus, working on copy ahead of development gave us room to design content and the interface together, which improved the UX. So going forward, we made sure that the mocks for all the features that were being designed reached us well on time. This way, we had ample time to pass UX feedback and craft copy that fits perfectly in the interface.<\/span><\/p>\n

Although the mocks changed based on successive iterations, some parts of the UI remained unchanged. For the bits that were changed, we revisited the copy and altered it accordingly. This process worked great for the designers, developers and the product managers too as it reduced back and forth between teams.<\/span><\/p>\n

\"\"<\/h3>\n

2. Review your copy with a product manager<\/b><\/h2>\n

If you\u2019re working along with a team of UX writers, there\u2019s always someone around to give you feedback and help you craft better copy. But what do you do when you\u2019re the sole UX writer for the entire product?<\/span><\/p>\n

Turn to your product managers for help.<\/span><\/p>\n

Product managers care a great deal about the product and the feature they\u2019re building. So they\u2019d be happy to review your copy. It\u2019s a good practice to get your copy reviewed by the product manager involved because if there\u2019s anyone who knows the product and the user really well, it\u2019s them. So the input they offer is very valuable and can help you polish the copy you\u2019ve written.<\/span><\/p>\n

My mentor, <\/span>Shankar Ganesh<\/span><\/a>, was a product manager who is known as \u201cthe guardian of good UX\u201d. He reviewed the copy I wrote and helped me tweak it. It\u2019s from those sessions that I learned most of what I know today about UX design and UX writing (a huge thanks to him).<\/span><\/p>\n

3. Test the feature while it\u2019s being developed<\/b><\/h2>\n

Even though copy is written in design, sometimes the sentences tend to break in the live environment. Or, sometimes, an error message that might have not been covered in design, might end up with a jarring copy.<\/span><\/p>\n

The best way to make sure that nothing is out of place in the live environment is to constantly test the feature. You need to begin testing right from the time the feature is being developed. Play around with the feature and test for all possible scenarios. You\u2019re likely to encounter a few error and success messages that might have been missed earlier. When I went about this, I would even document the bugs in the feature, along with instances of broken copy, if any. Once the feature is out, you need to go through the same process again.<\/span><\/p>\n

4. Collaborate with a support agent<\/b><\/h2>\n

When I started out, my mentor encouraged me to read support tickets. That\u2019s where customers raise their issues and some of them are very concerning from a UX point of view. However, going through each and every ticket is a time-consuming process and I could only browse through tickets during my free time. Luckily for me, about a month or two into my internship, I got to work with our community manager who had just moved into the product team from customer support. I have written in detail about <\/span>UX writers collaborating with support agents<\/span><\/a> to improve copy. Here\u2019s a gist of how this collaboration can help you:<\/span><\/p>\n

–\u00a0 Understand the user better.<\/span><\/p>\n

– Get familiar with user pain-points.<\/span><\/p>\n

– Know the language that your customers use.<\/span><\/p>\n

– Revisit old features wherein the copy needs to be changed.<\/span><\/p>\n

– Design better interfaces.<\/span><\/p>\n

5. Build a style guide for in-product copy<\/b><\/h2>\n

One of the last few things that I did as an intern was creating a style guide for the in-app product copy. But I didn\u2019t do it overnight.<\/span><\/p>\n

Building a style guide for in-product copy is a gradual process. In the first few months of my internship, whenever I encountered instances wherein we\u2019d go with a certain spelling or stick to sentence case, I made a note of them. Over a few months, I had enough clarity about how we framed and placed the copy. So, I documented my learnings and observations and built the style guide. Here\u2019s how you can go about it:<\/span><\/p>\n