Skip to content

Commit

Permalink
Work on article
Browse files Browse the repository at this point in the history
  • Loading branch information
basham committed Aug 21, 2024
1 parent 650a285 commit 6f0d168
Show file tree
Hide file tree
Showing 2 changed files with 92 additions and 108 deletions.
92 changes: 92 additions & 0 deletions src/content/writings/2024-08-20-useful.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,92 @@
---
title: Writing should be useful
pubDate: 2024-08-20
description: ""
draft: true
---

import Aside from '@components/Aside.astro';
import Figure from '@components/Figure.astro';

This is the start of a series about UX writing, based on my workshop [*Writing for Product Teams*](https://github.com/basham/swit-workshop-writing). Over the series, I explain three tenets: The writing we use in digital products should be useful, usable, and kind.

<Aside>
**UX writing series:**
1. Writing should be useful
2. [Writing should be usable](/2024-08-21/usable)
3. [Writing should be kind](/2024-08-22/kind)
</Aside>

## Useful writing is purposeful

The purpose of writing in digital systems is to solve problems, and the practice of UX writing gives us the means to do this. You don't have to be a "designer" or a "writer" to practice UX writing. Any product team member who has influence over the words that are used or how they are used shares the responsibility. As the book [*Strategic Writing for UX* (2019)](https://www.oreilly.com/library/view/strategic-writing-for/9781492049388/) explains:

> We need words is not the problem that we solve as UX writers. We communicate. We invite action. We inspire loyalty. Our teams need to know that UX writing can be used to solve problems.
Many problems can't be solved alone. Individuals may have to work together to meet their respective or shared goals. Working together minimally requires a meaningful exchange of information or resources.

Between people, this exchange happens through verbal or written conversation.

<Figure>
Person ⇄ (Conversation) ⇄ Person
</Figure>

Between a person and a digital system, this exchange happens through a user interface, such as an app or website.

<Figure>
Person ⇄ (Interface) ⇄ System
</Figure>

We can use our daily experience conversing with other people as a guide for the writing we use in user interfaces.

The more you know about another person, the more effective your conversation. You should identify who they are to you, learn more about them, and speak to them in a relatable way. In terms of a user interface:

1. **Identify your audience:** Don't write for a "general audience." If your website is meant for college students, think about where they are in their journey. Are they prospective students, enrolled, or alumni? Are they first-generation college students? Get specific enough while not excluding anyone within your intended audience.
2. **Research your audience:** Ask questions to learn about your audience's knowledge, expertise, interests, concerns, needs, tasks, and goals.
3. **Write for your audience:** Write in a way to help your audience find the content they need, understand that content, and then use that content to meet their goals. Speak to the user as a member of your audience.

## Mutual benefits

Because you know your audience, you can make the conversation easy for them. Be cooperative. Reduce the required effort or upfront knowledge they need to engage in the exchange. The conversation should be mutually beneficial. Each side should be satisfied with what they invested in it and what resulted from it.

In this example at a restaurant, the waiter states upfront the options available to the customer. The customer can provide a simple response by selecting one of those options.

> **Waiter:** Would you like wheat bread or gluten-free bread?
>
> **Customer:** Wheat, please.
>
> **Waiter:** Great!
In contrast, an uncooperative salesperson could be curt and not offer next steps. This could frustrate a customer and cost them extra time and effort.

> **Customer:** Can you call me when this furniture is back in stock?
>
> **Salesperson:** No.
>
> **Customer:** Then what should I do?
>
> **Salesperson:** Check back later.
In this third example, a customer and a home improvement store both benefit from their exchange:

1. A home owner wants to hang drywall for the first time. This requires knowledge, materials, and tools.
2. They discover Home Depot has an [online guide](https://www.homedepot.com/c/ah/how-to-hang-drywall/9ba683603be9fa5395fab90cbb4826d) to walk through this project with videos and written instructions suitable for do-it-yourself home owners.
3. They gained knowledge, but the page also lists the materials and tools that they may need and a means to find the them in the customer's local store.

The store aims to gain a loyal customer (and their money) by making it easy for the home owner to learn about and complete their projects.

## Activities for useful writing

These activities explore ways individuals can meet their goals through a conversation. The conversation can be summarized as a user journey (steps toward meeting a goal). This user journey and the language used in the conversation can be the basis for designing a user interface.

### Instructions

1. Participants vote on sample situations and select one for all groups to use.
2. Participants split into groups of two people and each determine a role to play based on the selected situation.
3. Use a speech-to-text tool (such as [Microsoft Translator](https://translator.microsoft.com), the [Microsoft Word dictate feature](https://support.microsoft.com/en-us/office/dictate-your-documents-in-word-3876e05f-3fcc-418f-b8ab-db7ce0d11d3c), or the [Google Docs voice typing feature](https://support.google.com/docs/answer/4492226)) to record a conversation between the participants based on the selected situation and roles.
3. Write a user journey based on the recorded text.
4. Repeat as time allows, with participants rotating roles. Add variation by changing:
- Time, place, environment
- Mental or physical impairments of individuals
- Outcome of the conversation
5. Afterwards, each group should share what they did and learned.
108 changes: 0 additions & 108 deletions src/content/writings/2024-08-20-writing.mdx

This file was deleted.

0 comments on commit 6f0d168

Please sign in to comment.