I think what Michael is saying connects with a lot of us. As a sometimes-hiring manager, I feel like I can do better with being open and transparent about what I'm looking for. In this thread, I'll try to give some guidance for what I think is a universally helpful portfolio https://twitter.com/mjmetts/status/1249771276467568640

First, a disclaimer: This is for portfolios toward roles in UX writing, UX/product content strategy, content design, whatever you want to call it: if you're thinking about the words and language in digital interfaces, with a design approach. Other portfolios may vary.

I also want to acknowledge that ideally, hiring managers should be taking the time to talk to candidates. There's an unbalanced power dynamic at play here.

But portfolios are still the main way companies can get a snapshot of how you work and how you solve problems. Some use skills-assessment take-home tests, but not all do. That's a topic for a different time (I don't like em).

So, like, what's the purpose of a portfolio? I like to think of it as the qual data to a resume's quant — a resume gives you numbers, like years of experience, or if you meet a degree requirement. It checks the boxes a job listing is asking for.

A portfolio can, show that you've made an impact at a place you list on your resume. But more importantly, it should showcase how you think. The output of your writing is important, but even more important is your approach, your decisions, your strategy.

Before/after screenshots of your writing don't do that. I'm left with unanswered questions: Why did you choose this term? Why are you taking this tone? How does this tie into the larger voice strategy of the product/brand?

Some more questions I want a portfolio project to answer:
- Are you using words to help a user accomplish a goal? How?
- How does this language connect to the system at-large? If a user's progression is a journey, how does this contribute to them arriving at their destination?

It's up to you to decide how to do this. Me, I like a few screenshots in a flow that highlight the heavy-lifting your words are doing. That, paired with a few sentences describing why you wrote it, what problem it solves, and what factors you considered.

Example: @marinaposniak, a UX writing/content strategy veteran, does this expertly in her portfolio. Check out how she zooms in on components and string, and then zooms out on the problem it solves. http://www.marinaposniak.com/#/spotify-ux-writing/

She's also really honest about how it's not perfect, which is fantastic. Honesty and transparency are your friends, and any hiring manager should know that these projects are rarely perfect. More on that later.

Q. What do you put in your portfolio?

@mjmetts said it perfectly: A portfolio should show your work, and what you want to do more of. Michael, for example, stresses the importance of a holistic approach to solve a common problem.

Check this page out in his portfolio: http://mjmetts.com/workstories/2019/10/11/xxk979xs3pw7qzioxx3c00rdqsa83i

Here's the approach he took to building a chatbot, and the framework behind it, rather than a screenshot of a chatbot conversation itself. Good chatbots are complicated, and there's a lot to consider.

This shows me he's done the deep thinking. Rather than posting a screenshot of a conversation with the bot while following the happiest path, this shows the triggering logic and the contingencies behind the product.

(BTW to me, a good UX writer portfolio looks _very_ similar to a good UX designer portfolio. That's because, as you may know already, writing _is_ designing. You're all here to solve user problems. Your materials are different, but your strategy is the same.)

A portfolio gives you specific insight into how you work. If you have great, ideal projects you can showcase -- great!
If your projects are less than ideal—if they're under NDA, they never shipped, or there was major compromise, well, then, that's okay.

For lack of practical experience, something to consider: I think spec work is totally OK, though of course the burden of proof weighs more heavily on you to show why your solution is better. Be sure your meta commentary outlines why you've chosen this and how you're improving it.

If your project is under an NDA: check out this article by @jennyshen. I think she has some good advice. https://uxdesign.cc/is-nda-in-the-way-of-your-design-career-5-ways-to-navigate-around-it-215176bea567

In summary:
Portfolios suck but you gotta
Show your work and the rationale behind the work
Show how you think, both at a focus-level and a systems-level
Be honest and transparent

Also, I'd love to hear if any other hiring managers have additional thoughts. Please weigh in if you have more or different thoughts! @andreadrugay @ChelseaLarsson @bizsanford @jcolman, et al!

(Plus, a huge thank you to @mjmetts, @scottkubie (hire him!) and @willfanguy for your insight and feedback into this thread)

(Oh, and @threadreaderapp please unroll)