The Daily UX Writing Challenge was created by GoodRX content strategist, Ryan Farrell. I created the mockups using Adobe XD 🎨
I didn't know how to use XD. But I wanted to put some context to my copy solutions, so I put a fair bit of time into learning how to use the design tool. I really enjoyed doing so, and felt pretty good when I realised I got the hang of it (after a little over a week). Below is the end result.
Day 1
​
Scenario: A traveller is in an airport waiting for the last leg of a flight home when their flight gets abruptly cancelled due to bad weather.
Challenge: Write a message from the airline app notifying them of the cancellation and what they need to do next.
Headline: 45 characters
Body: 175 characters max
Button(s): 25 characters max
Reasoning
​
Taking into consideration the traveller's frustration, disappointment, and possible anger, my aim here was to front-load the message with the cancellation notice, then be as empathetic and helpful as possible.
Day 2
​
Scenario: A user is a working parent and a big sports fan in the midst of their favourite sports season, who can no longer attend games.
Challenge: Write a promotional screen for an app that lets a user choose teams, sends game reminders, real-time score updates, and highlight videos.
Headline: 40 characters max
Body: 175 characters max
Button(s): 25 characters max
Reasoning
​
My aim here was to get the working parent as excited as possible about this app—from the highlighted benefits right down to the whistle noise at the end and the rousing call to action (CTA).
​
If they need time to think about it, the "Maybe later" option will come in handy.
Day 3
​
Scenario: The user entered the wrong email address to sign in to their account.
Challenge: Tell the user to enter the right email.
40 characters max
Reasoning
​
My aim here was to be as polite as possible. The user made a mistake, but that doesn't mean the copy should be blunt or forceful, thus shaming or
disrespecting them.
Day 4
​
Scenario: A user is in their favourite supermarket. They open the supermarket’s app on their phone to see what’s on sale and are greeted by a promotion.
Challenge: Write a promotional home screen for a subscription service that delivers groceries to the user once a month for a flat fee.
Headline: 45 characters max
​
Body: 175 characters max
​
Button(s): 25 characters max
Reasoning
​
My aim here was to highlight the convenience and reasonable cost of this service as well as offer some incentive to sign up.
​
The CTA should create excitement.
If they need time to think about it, the "Maybe later" option will come in handy.
Day 5
​
Scenario: The user works in graphic design. While critiquing a design in a mobile app, their phone abruptly turns off. When they restart the phone, they reopen the app.
Challenge: Write a message that the user will read immediately upon opening the app. What do they need to know? What steps (if any) do they need to take to recover their content? What if they can't recover the content?
Headline: 40 characters max
Body: 140 characters max
Button(s): 20 characters max
Reasoning
​
My aim here was to calm and reassure the user as soon as possible.
Easing them further is the option to resume later, knowing their work will be there when they're ready.
I also couldn't resist the urge to squeeze a pun in there (sorry, not sorry!).
Day 6
​
Scenario: It’s Monday. A user has just gotten into their car to drive to work. They plug their phone into the car and start driving.
Challenge: How would you let the user know there’s a fire happening in a nearby town that is causing road closures? The effect on their commute is unknown, but there is a definite danger if the fire gets closer. How do you communicate this to them? When? Write it.
Headline: 30 characters max
Body: 45 characters max
Reasoning
​
My aim here was to advise the user, in a concise manner, of a situation that could affect them, but without exaggerating it. Exaggerating would cause undue worry and subsequent resentment once the user realises the situation isn't as threatening as suggested.
​
The "x" allows them to dismiss the alert, while the "another route" link will find them a safer route once they tap it.
Day 7
​
Scenario: A sports fan is at a wedding while their favourite team is playing against their arch-rivals. Their team scores.
Challenge: How would you, quickly, let the sports fan know about the latest play, the current score, and the key players? Write it.
Headline: 30 characters max
Body: 45 characters max
Reasoning
​
My aim here was to give the sports fan all the key details, so they can know what's happening at a glance.
I also wrote it in a way that would make the app share the fan's excitement about their favourite team being in a winning position.
Day 8
​
Scenario: The user is a casual music fan and (on occasion) goes to live concerts. They have a music player app on their phone.
Challenge: Tell the user that one of their favourite bands is playing live in their town. How would you compel them to want to go?
Headline: 30 characters max
Body: 45 characters max
Button: 25 characters
Reasoning
​
My aim here was to make them think about how much better the music is once heard live compared to on their device. I made “live” stand out for that reason.
The CTA was also written with the aim of creating excitement for the concert.
​
If they need time to think about it, the "Ask me later" option will come in handy, while the "x" allows them to dismiss it if they're not interested.
Day 9
​
Scenario: The user is trying to rent a car using an application but the credit card on file has expired.
Challenge: Write them an error message so that they can correct the problem.
Headline: 30 characters
Body: 45 characters
Reasoning
​
The user shouldn't be made to feel bad or disrespected as a result of making an honest mistake. My aim here was
to gently alert them to their card's expiry and politely ask them to change it.
I also made it a point of directing them to where they could quickly fix the problem so they could get back to completing their task.
Day 10
​
Scenario: The user is trying to view a website to help them buy a car. But, the content can’t load without the user’s location. They need to enter their ZIP code and first name.
Challenge: Ask them where they live and who they are without sounding like you're unnecessarily mining their data.
Headline: 25 characters
Body: 45 characters
Button: 15 characters
Reasoning
​
My aim here was to place emphasis on the reason why the user's personal information is being requested and the benefit of giving it up.
​
The aim of the CTA was to excite them, so they'd want to start their car search quickly.
​
The "x" gives them a quick and easy opt out, exiting them from the website.
Day 11
​
Scenario: An elderly user is doing a Google search to find an easy way to buy contact lenses online.
Challenge: Write a title and meta description for a website that sells subscription contact lenses delivered to a user every 30 days—convince them to try it.
Title: 60 characters max
Meta Description: 160 characters max
Reasoning
​
My aim here was to show consideration for the elderly user by making it as convenient as possible for them to find contact lenses. A simple search for “contact lenses online” should bring EyeSpy to the fore.
My copy highlights delivery as well as a free first month's supply, which should entice them into trying the lenses.
Day 12
​
Scenario: A user is creating an account. When they come to the step where they are asked to enter their name, they get an error message. A fraud detection software thinks their name is fake—but it’s wrong 5% of the time.
Challenge: Write an error message that prompts them to fix the error without shaming them for having a fake-sounding name.
45 characters max
Reasoning
​
My aim here was to make the user feel special for having a unique name rather than ashamed or even offended. On the other hand, I didn't want to patronise them either.
I provided a “workaround” via a "here" link to ensure they can still sign up. But I had to borrow an additional two (2) characters for my copy, using 47 in total. Small price to pay to get such a sensitive and important message right for the sake of the user.
Day 13
​
Scenario: A short-haul truck driver has a phone app that monitors his route, schedule, fuel & deliveries.
He has 6 more deliveries before stopping for fuel and lunch. Due to unexpected traffic, he’s behind schedule.
He can choose to stay on his planned route for a few more stops, but risk running low on fuel and missing lunch, or he can get fuel and lunch now and finish the deliveries later.
Challenge: Write a push notification alerting him of this dilemma and options.
Headline: 30 characters max
Body: 45 characters max
Button(s): 25 characters max
Reasoning
​
My aim here was to avoid flooding the truck driver with too much information, which would frustrate him more and distract him too much.
​
My copy should make it easy for him to decide what to do.
Day 14
​
Scenario: a user is shopping using a price comparison app that boasts “real-time” pricing on items. As they are checking the price of an item, something goes wrong. The problem is unknown.
Challenge: write a message that informs the user that they cannot access the app right now. You cannot specify "why" the app doesn't work, you also want them to continue using the app.
Headline: 30 characters max
Body: 120 characters max
Button(s): 15 characters max
Reasoning
​
My aim here was to do my best to assure the user that everything will be okay, even though the cause of the problem is unknown.
It may not be the app's fault, but I wanted it to humbly accept
responsibility, which should appease the user, keeping them in the app.
​
My copy should also empower them by politely requesting their help to resolve the issue.
Day 15 (bonus challenge)
​
Scenario: A user needs a ride to the airport. They use their favourite ride-sharing app to schedule the ride. The driver who accepts is hard of hearing.
Challenge: Write a lockscreen notification that tells the user that their driver is hard of hearing. Include all relevant information (including links) in the notification.
110 characters max
Reasoning
​
This situation could cause discomfort, so my aim here was to alleviate that discomfort by opening the way for some communication between the user and their driver.
​
The message is front-loaded with key information, and I've included a helpful link that once tapped would take the user to learn simple sign-language expressions, empowering them ahead of their ride experience.
​
The emojis are a nice touch, reassuring the user in other words: "Don't worry―we've got you, and you've got this."
