{"id":1944,"date":"2020-03-25T11:02:09","date_gmt":"2020-03-25T11:02:09","guid":{"rendered":"https:\/\/uxwritinghub.com\/?p=1944"},"modified":"2021-05-04T13:22:16","modified_gmt":"2021-05-04T13:22:16","slug":"how-to-apply-ux-writing","status":"publish","type":"post","link":"https:\/\/uxwritinghub.com\/how-to-apply-ux-writing\/","title":{"rendered":"When and how to apply UX writing (It’s like riding a bike!)"},"content":{"rendered":"

\u00a0Imagine that you are teaching your little brother Adam<\/strong>, to ride a bike.\u00a0<\/strong><\/span><\/p>\n

\"\"
Original post : @ Alex Warwick Cycles<\/a><\/figcaption><\/figure>\n

You start with the basics<\/strong>, showing Adam how the bicycle works. Then you get the training wheels out, supporting him<\/strong> every step of the way until he stops wobbling. Finally, you let him play with it \u2014 he\u2019ll fall over a few times, but soon enough he\u2019s off on his own like a pro.<\/strong><\/span><\/p>\n

Let\u2019s break down these steps with real UX writing examples!<\/em><\/strong><\/p>\n

Step 1: The basics<\/b><\/h2>\n

You could also call this step \u201cgoing through the theoretical framework\u201d, but Adam doesn\u2019t care what you call it, he just wants to get going.<\/span><\/p>\n

At this stage, the most important thing for you as the product owner is to persuade Adam that your bike is the one he wants to use. And where do you have a great chance to show off your solution?<\/span><\/p>\n

Above the fold section<\/h3>\n

Above the fold is the top part of a website \u2014 essentially what the users see when they land on it the first time. This section needs a clear headline, a paragraph that explains how your product is going to solve the users\u2019 problems, and a call to action.<\/span><\/p>\n

This is the moment when Adam spots what he wants at the store and will throw a tantrum if he doesn\u2019t get this particular bike. So how do you make sure your above the fold section is the one that catches Adam\u2019s attention?<\/span><\/p>\n

One thing is for sure \u2014 it is easier said than done, and like most people, you will probably not master the new bike at the first attempt. Try out different things, test them and move forward. Strong visuals are crucial in this part so be sure to talk to the design team and build a strong message.<\/span><\/p>\n

A great example of a clear and practical above the fold section is the home page of the management tool <\/span>Monday.com<\/span><\/a>.\u00a0<\/span><\/p>\n

\"monday<\/p>\n

I just want to grab their tool and play around with it, do you agree?<\/span><\/p>\n

Onboarding experience<\/h3>\n

Now when your users are in and Adam can\u2019t stop smiling because he has a new bike, we need to explain what he can do with it. In UX writing terms, this is the onboarding experience.<\/span><\/p>\n

There are numerous ways to do this. Some say you should just let the users play around, others think you should give them as much information as possible. It really depends on the user and the product, so there isn\u2019t a single way to go here.<\/span><\/p>\n

You\u2019ll find a good explanation and lots of examples of the onboarding experience at <\/span>material.io\/onboarding<\/span><\/a>.<\/span><\/p>\n

I also recommend following UX designer <\/span>Samuel Hulick<\/span><\/a>, who shares fantastic insights (and even a book!) on user onboarding.<\/span><\/p>\n

\"Example
Example by Duolingo<\/a><\/figcaption><\/figure>\n

Step 2: The support phase<\/b><\/h2>\n

We\u2019ve managed to show Adam what he can do with the bike, and he\u2019s now so keen to get going there\u2019s definitely another tantrum coming on. So let\u2019s do it! We\u2019re going to guide our little bro every step of the way from zero to hero.<\/span><\/p>\n

From complete trial-and-error newbies, your users are going to actually learn how to use the product.<\/span><\/p>\n

Customer support bot<\/h3>\n

Tools such as Intercom or Zendesk can help you to create a customer support bot.\u00a0<\/span><\/p>\n

The technicalities are easy as you just plug the tool to your website. But the interesting (and challenging) part would be to design a conversation for that bot that will answer all the questions the users have without a live agent.<\/span><\/p>\n

I\u2019ve never built this kind of bot myself, I just know that creating one would help you to do the next part which is:<\/span><\/p>\n

Informative FAQ section<\/h3>\n

Writing the technicalities of a product is easy, creating a useful FAQ (frequently asked questions) section is hard. Adam is on the bike; it\u2019s a bit wobbly but he\u2019s getting there. All of a sudden he stops. He\u2019s spotted the bike bell. \u201cWhat\u2019s this? Why is it there? How does it work? What is it made of? Where does it come from?\u201d You get the point \ud83d\ude42\u00a0<\/span><\/p>\n

The smart way to go here is to use existing data and pay attention to what it says.<\/span><\/p>\n

What makes Adam frustrated? When you can explain it to Adam, you have come a long way and should consider making the information available to the rest of the users.<\/span><\/p>\n

In the real world, you would use the data you\u2019ve collected through your chatbot agent or by holding interviews with your customer support department. The important thing is to use existing data. If you don\u2019t have any, carry out benchmark research \u2014 find out what others are doing in your field.<\/span><\/p>\n

Tooltips<\/h3>\n

Tooltips are small pieces of text that make sure your users always know what to do. They are often shown automatically when hovering over a question mark or information icon.<\/span><\/p>\n

\"Example
Example by google docs<\/a><\/figcaption><\/figure>\n

As with the FAQ section, the best way to go here is to use existing data. Identify and focus on the bottleneck of your platform \u2014 what information do people need to make sure they don\u2019t get stuck?<\/span><\/p>\n

If you don\u2019t have any existing data, user research is your best buddy. How did Adam\u2019s mates get on with their bikes?\u00a0<\/span>What helped them to master the bell? <\/span><\/p>\n

Create user surveys, hold interviews, build personas, create assumptions that predict how your tooltips will communicate your product better and test those assumptions.\u00a0<\/span><\/p>\n

Just don\u2019t try too hard here. Make it short and sweet \u2014 there\u2019s no need to overcomplicate things!<\/span><\/p>\n

Step 3: The pro stage<\/b><\/h2>\n

After scraping his knees a few times, Adam is off on his own. Don\u2019t they just grow up so fast? I know. Now it\u2019s time to let them be.\u00a0<\/span><\/p>\n

There are many ways to use a bike. Some turn into power users and ride it every day, while others just use it once in a while. In any case, we want to make sure the bike helps them achieve their goals.\u00a0<\/span><\/p>\n

Error messages<\/h3>\n

If your users are trying to perform an action but fail, the most important thing is to make sure you can solve the issue in the best possible way. When something has gone wrong \u2014 imagine Adam getting a puncture for the first time on the way to his friend Mike\u2019s place \u2014 he has no idea what happened and what to do about it, but he is very scared that he has done something that ruined the bike forever. This is not a good time to be smart or funny. Even if you know that it\u2019s easy to fix a puncture and the bike will be fine, Adam doesn\u2019t know that. And on top of this, he is upset that he can\u2019t play with Mike.<\/span><\/p>\n

It\u2019s a good idea to map all the possible errors a user can come across when using your product. This might include a declined card or the wrong password. Be sure to let the user know exactly what the problem is and help them to find a solution.<\/span><\/p>\n

\"error
Error message done right by Mailchimp<\/a><\/figcaption><\/figure>\n

Even better, try to think of copy that will prevent that error in advance. Do they need to create a password with a particular set of characters? Tell them before they have a chance to enter \u201c1234\u201d in the password field.<\/span><\/p>\n

Transactional emails<\/h3>\n

Many companies do a great job sending emails that inform you how to use their product.\u00a0<\/span><\/p>\n

The meditation app Headspace confirms how much time you\u2019ve spent meditating, for example, and offers you new meditation based on your meditation history.<\/span><\/p>\n

\"Headspace
Headspace<\/a> transactional email<\/figcaption><\/figure>\n

The messaging app\u00a0Slack<\/a> lets you know how many people were active in your chat.<\/span><\/p>\n

\"Slack
Slack<\/a> transactional emails<\/figcaption><\/figure>\n

They use emails to provide product insights and help you become the champ. Write your transactional emails well and you might just make users for life.\u00a0<\/span><\/p>\n

A great idea is to take existing and complex data and present it in a fun and gamified way to encourage people to review the data and aim for better results.<\/span><\/p>\n

You can read more about transactional emails in this Udemy case study<\/a> by our student Jim Gallant.<\/p>\n

Confirmations<\/h3>\n

When we try to complete a task, it\u2019s good to know that we\u2019re on the right track.\u00a0<\/span><\/p>\n

When your users perform an action in your product, be sure to acknowledge that. The right feedback at the right moment will make Adam a better cyclist. Perhaps it will even encourage him to become a cycling pro?<\/span> How awesome would that be! If your users upgrade to your premium version, celebrate it with them. High fives, even!<\/span><\/p>\n

\"Mailchimp
Original post from Invision about the history of Mailchimp\u2019s high five<\/a><\/figcaption><\/figure>\n

If they send you a message, don\u2019t leave them hanging. Let them know you\u2019ve received the message \u2014 if you use automated responses, try to be as specific as possible about when they can expect a response (in the next 24 hours? Within 2 days?). If you tell Adam you will fix his bike \u201cas soon as possible\u201d, he might come back and hassle you about it every five minutes \ud83d\ude42\u00a0<\/span><\/p>\n

Ride out your UX Writing<\/strong><\/h2>\n

If you want to make your product\u2019s experience as easy as riding a bike, communicate it as if you are teaching Adam how to ride a bike.\u00a0 At first, there is a lot of groundwork to do, but once you get the hang of it, your users will be hooked.\u00a0<\/span><\/p>\n

Just remember, UX writing is about helping your users, not trying to manipulate them to take certain actions. In short, avoid dark patterns and don\u2019t be a jerk!<\/span><\/p>\n

\"Avoid
Avoid dark patterns – original post @Velo Theory<\/a><\/figcaption><\/figure>\n

Now it\u2019s your turn. What can you do today to improve your product or service based on what you\u2019ve read?<\/span><\/p>\n

For more fun UX writing lessons:<\/span><\/p>\n