This is the published edition of our weekly UX writer and UX writing newsletter, The Dash. Sign up to The Dash to have these updates sent straight to your inbox!
“Learn more” is not enough yet it’s everywhere on the internet. So what makes a CTA actually helpful? This week’s Dash explores just that. Plus our new course is almost here: UX Writing for Technical Writers. It’s time technical audiences got some user experience love. Coming next week. Until then…
“Learn more” is not enough. Are your CTAs serving a specific purpose or are they acting more like fillers? Alice Chen makes the case for why descriptive CTAs are more accessible, SEO-friendly, and contribute to an overall better UX. We refuse to say learn more so we’ll instead say read the latest over on our blog.
Ask the experts… part two recap. In this Q&A webinar, Patrick Stafford covers your burning career Qs — including everything from your role as a UX writer to working cross-functionally with design teams. Watch the replay.
How Figma’s principal UX writer is helping build design software that UX writers love. In this episode of the Writers of Silicon Valley podcast, Chris Baty shares his experience joining Figma, what it’s like working as a team of one, and the work he’s doing to make Figma an exceptional tool for UX writers everywhere. Get it where you get your podcasts.
How Robinhood handled a crisis. Hint: Not well. What can we learn from the stock trading app’s actions (or inactions) during the recent GameStop debacle? Lack of context, explanation, and user empathy only made matters worse. This is a perfect example of why UX matters in a crisis.
How to structure and present your UX portfolio. The infamous interview portfolio presentation. If just thinking about this gives you anxiety, just know you’re not alone. It all boils down to showing that you can articulate your ideas, processes, and concepts. Need inspiration? UXfolio has your back.
Building a copy collaboration workflow. Since launch, the Ditto team has talked with 200+ organizations about their internal copy collab processes. Their key finding? Copy is end-to-end and should be treated as such.