Tips for your UX writing portfolio when you’re starting out
by Andy Welfle
One of the ways I’ve been trying to make a positive difference during this lost COVID-19 season is to hold office hours for unemployed or emerging UX writers. I hear over and over again from writers in other industries — journalists, marketing copywriters, technical writers, etc. — that they’re pretty interested in UX writing but just don’t know how to break into the field.
I get that. UX is an alluring, inscrutable beast that comes with its own set of jargon, terminology, and process. To an outsider, it’s hard to parse at best, and at worst seems like it’s intentionally built to shift goalposts and to keep outsiders out.
One of these big unknowns is, of course, the UX writing portfolio. This is one of the most commonly asked-about topics I’ve seen in my office hours and in the many coffees I’ve had over the years with newcomers to the field.
Specifically, I get asked some variation of these questions:
- Are they (the portfolios) necessary?
- How should they be structured?
- What should be in them?
- What if I don’t have any relevant clips or all my work is under an NDA?
Those are great questions. I tried to tackle some of them in a Twitter thread a couple of weeks ago, but admittedly, that’s a terrible way to get a big idea out. So let’s approach these questions here!
First of all, who are you and why should I listen to you?
Great question! Maybe you shouldn’t. I don’t have all the answers, but I am a sometimes-hiring manager on a small but crack team of UX writers and content strategists at Adobe! We’re responsible for driving (and sometimes writing) the interface language throughout our biiiig varied portfolio of apps. I’m typically in charge of scouting, recruiting, and hiring my team members myself, so I’ve developed some opinions and practices over the last few years.
So are UX writing portfolios really necessary?
I had a great conversation with some friends about this very topic recently, and the conclusion I’ve come to is that they shouldn’t be, but they are.
Why shouldn’t they be?
- Portfolios are impersonal, and an inaccurate way to really get an in-depth look at a candidate’s work.
- Portfolios reinforce the biases (implicit and explicit) of the recruiter or hiring manager. If you approach your work differently than they might expect, they might skip over yours.
- They also reinforce an unequal power dynamic. Big companies often expect your portfolio to be structured in a very specific way that scales for their applicant review process but doesn’t scale for you, the applicant.
But why is a UX writing portfolio necessary, then?
- This is one of the best ways we (hiring managers) can get the qual data to accompany the quant data of your resume. A resume gives us a checklist — years of experience, a relevant degree, keywords of proficiencies (all in themselves problematic, but that’s a different post), but the portfolio gives us a snapshot of how you work and how you solve problems.
- While UX writing opportunities as a whole are plentiful, they come up only every once in a while for my team. That means I get several dozen applicants, and most of them either aren’t qualified or used some sort of bulk-application method to apply. I need a way to filter out those who are serious about the role.
How should I structure my UX writing portfolio?
I think this is a great opportunity to play with the various media out there. To me, it doesn’t matter if it’s a link to a “My Work” section of your website, a PDF, a Google Slides deck, or what.
Basically, there are two things that I look for:
- The work itself — a screenshot, a link to a live site or app
- The rationale behind it — the problem you’re solving for, an explanation of a few decisions you’ve made, and any frameworks or process documents you worked on, throughout the project.
Let’s look at an example from what I think is an excellent portfolio. This is from Marina Posniak, a UX writer at Spotify. Of course, one big advantage she has is that Spotify is recognizable to most people — she doesn’t need to take the extra step of giving extra context. But she does a really great job of framing the specific, focused problem at hand:
She presents, on the right sidebar, an overview of the problem, the solutions she pursues, and how she contributed. On the left are a few, specific examples of that work in action. It’s very simple, and very focused, but she hits all the right information — this example shows how she reduced the text string from three lines to one, and why.
Here’s another great example — with the launch of Spotify Codes, Marina did something that’s very common for UX writers — she wrote a few different versions to see which one works best. And while she probably didn’t feel comfortable sharing the exact text of the versions that didn’t go live, she did a great job of summarizing what made the versions different.
If it includes these things, the rest is up to you! Andrea Drugay, Group Manager of Copy at Slack, made a good point when I was discussing this on Twitter.
She said, “A good UX writer is a good problem-solver, and a portfolio is, ultimately, a UX problem. How are you solving the problem of ‘How do I present my work?’ If you’re taking creative approaches to problem-solving, that’s a plus.”
That’s a great point. The way you put together your portfolio is a great meta-challenge, and a chance for you to shine at UX writing interviews.
What if I don’t have any relevant examples?
This is pretty common. How can you be expected to show related examples if you don’t yet have experience?
There are certainly a few scrappy ways you can gain some UX experience without being a full-timer in the field:
- Have a friend who’s building a website? Volunteer to work on the nav structure or help them put together guidelines for what information their pages should include.
- I definitely don’t discount spec work. If you use an app or a website that’s not great, and you have opinions on how you could improve it, go for it! Just reminder a couple things:
- Be respectful. You never know the background and experience your portfolios reviewers may have had, so don’t trash talk. Even if it IS a terrible design.
- Spec well-known apps or experiences. Spec work relies on the reviewer understanding that you’re trying to improve a bad experience. If you’re re-imagining small or obscure apps or websites, it’ll take the reviewer longer to build context.
But I think that you can get even scrappier. What kind of writing samples do you have? Magazine articles? Blog posts? Ad copywriting campaigns? We can work with that. It’s all about how you’re framing it.
Remember, writing is designing, and designing is about solving problems for the user. What was the problem, and how are you solving it with words?
You can probably answer those questions with your clips:
- For a magazine article about a new indie band: How did I get across the feeling of their music to an audience who has never heard them? How did I accurately explain their message if I was only able to email a couple questions to the band leader?
- For a marketing copywriter writing about enterprise software: How did I explain the benefits, quickly and succinctly, for the complicated b2b software I was writing about? How did I take my strategy, and change approaches between different mediums?
If the answer to these questions are, “I dunno, I just wrote some words”, then I can’t help you. UX writing (and these other writing industries, too) requires a baseline level of strategy and decision-making, and it’s very important to be able to give rationale. Your words should speak for themselves when they’re being reviewed, but you should always be able to show your approach and decision-making when you’re being reviewed.
This is all open to interpretation
Remember, there are no hard-and-fast rules to designing your UX writing portfolio. And I think you can use that ambiguity to your advantage. It’s a great design challenge in itself, and I really encourage you to experiment with the structure and form. As long as it’s accomplishing the right goals, and including the right information, you can exercise your communication and systems-thinking skills to really tell your story.
Andy Welfle is a Content Strategy Manager and hiring manager at Adobe Design in San Francisco, the centralized product design team at Adobe. Andy is also the co-author of “Writing is Designing: Words and the User Experience”. Follow him at @awelfle on Twitter or on the web at andy.wtf.