Daily UX Writing Challenge
The challenge
The Daily UX Writing Challenge was created in 2018 by Ryan Farrell – a content strategist, UX writer, and advisor of the UX Content Collective. Since then, more than 12000 UX writers worldwide have taken the challenge. In his own words:
1 of 14 short exercises will be delivered to your inbox every day for 14 days. Including: a scenario, a challenge and how many words you have to work with.
[The scenarios are] actual prompts from the largest product organizations in the world. [Each time,] write and edit your solution as fast as you can.
Try to do it in ten minutes. Most UX writing and content challenges are timed exercises. If you can do it even faster, that's even better.
My approach
Let's start by admitting that yes, I cheated. I didn't come up with each solution in just 10 minutes.
Or, better: I did write and edit in 10 minutes – but I took an extra 15 to set the stage right before writing anything.
To work as fast and efficiently as possible, I used The Microcopy Canvas by Jane Ruffino on Miro as a framework for each challenge. I also quickly researched online the common terminology of the target users, especially for contexts I am not familiar with (like soccer or truck driving).
As an additional exercise, I explained my rationale and process in English – something I have to do all the time while writing, editing, or localizing Italian (micro)copy in an international setting.
My role: Content strategist, UX writer
Duration: 30 minutes per day, for two weeks
Tools: Google Workspace, Miro, and Figma
You can read the scenario, challenge, and solution by clicking on each image, or just below the gallery.
Day One
Scenario
A traveler is in an airport waiting for the last leg of a flight home when their flight gets abruptly canceled 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
Solution
The goal here is to get all our tired, potentially angry customers to process the news without blaming the company for the cancellation and quickly provide them with a solution – so they can go to have a nap or a meal instead of besieging our staff at the airport and causing further delays. To do so:
-
I tried to strike a balance between personal and impersonal, to achieve a human tone that could sound reassuring and caring rather than apologetic. I started with an impersonal form (the flight was canceled), and I immediately moved to the reason for the cancellation, the bad weather. The company and the passenger appear just afterward, linked by an expression with a positive connotation: the bad weather doesn't allow us to guarantee you a safe trip.
-
Not knowing the specific policy and liability of the airline, I chose to focus on giving the passenger two quick options, to avoid escalation and reduce the workload on customer support and ground crew. I also made sure to dispel two potential fears of passengers: they will be refunded in full or change the reservation at no additional cost.
Alternative copy for feedback/testing
Body:
A. Il maltempo non ci permette di garantirti un viaggio sicuro. Ti offriamo il rimborso completo o l'imbarco prioritario sul prossimo volo, senza costi aggiuntivi.
B. Il maltempo non ci permette di garantire un viaggio sicuro a te e agli altri passeggeri. Ti offriamo il rimborso completo o un posto sul prossimo volo, senza costi aggiuntivi.
Day Two
Scenario
A user is a working parent, and a big sports fan, in the midst of their favorite 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
Solution
At first, I went along with the assignment and played around with FOMO and a few football jargons – but then I decided to shift the focus.
Watching a match live might be a great experience, but you're bound to miss some actions: if it's on TV, it might be interrupted by ads, while if you're at the stadium, you might not always have a perfect view of the field. So, instead of focusing on not missing out, I hinted at how the app could guarantee you to keep up-to-date with every single action, hence giving you a fuller live experience – like watching a game from the sidelines.
I then used some keywords that users might be actively scanning for: results, reminders, and replays. Also, since users might be wary of receiving (too many) unwanted push messages, I signaled they are in control of choosing a team and turning on notifications.
Alternative copy for feedback/testing
Headline:
Marca stretto la tua squadra
Day Three
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
Solution
A short assignment that hides one of the most difficult challenges out of all – at least in Italian, a language that doesn't usually get along with tight character constraints.
Despite what it states, the purpose of this message was not only to tell users to enter the right email, but to:
1) Identify clearly the error (as to say, notify them the email address they entered is wrong)
2) Ask them to check it/try again
3) Give them the option of recovering the email address linked to their account
To keep within the character limit, I relied on words commonly used in Italian for error messages, and the web convention that underlined text hides a hyperlink. The hyperlink allows users to recover their email, and the button label clearly states what happens next. I also chose neutral words that don't blame/patronize users for an error (like wrong/incorrect): the email is simply not found.
I could have cheated (ehm, again) and split the message in two, isolating the recovery option as a button on the left and adding a symbol on the top right of the lightbox as a way out. But since it's a challenge, I gave it a go and packed everything in 40 characters. Of course, if this were a real-life scenario, I would test it with users first – I am particularly concerned by the potentially confusing combination of the word for recover + the clitic pronoun for [the email].
Alternative copy for feedback/testing
Indirizzo non riconosciuto. Vuoi recuperarlo?
Email non registrata. Riprova o recuperala. [43 characters]
Day Four
Scenario
A user is in their favorite 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
Solution
This was a tricky one. It sounded like odd behavior to check the supermarket's app for deals while inside the supermarket. And what about the app itself? Is it used mainly for this purpose or to shop online? Does it locate the user inside the supermarket? Do people pay for the subscription service through the app or at the cashier if they shop IRL?
Since I don't know the answer to these questions, I went for a solution that might work both if the customer is shopping online and on-site, mentioning they can try the subscription with today's groceries shopping (I promise that in Italian it sounds better). I also addressed the potential fear of being tied down to a subscription: you can cancel at any time.
Day Five
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
Solution
The least inspiring challenge out of all 14. It was not clear if the app was itself a designer's tool (to give feedback, like TrackDuck) or just the temporary object of a design critique. I decided to go with the first option but give a generic solution, trying to avoid humor (or the now overused "Ooops!" messages) and keeping the tone as professional as possible – while still sounding human.
Day Six
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
Solution
Word order was essential for this challenge. We want to catch the users' attention while driving, make them understand the danger at a glance, and keep reading until the last word.
The first word they'll see in the headline is fire, followed by the location in km (a data that should be easy to pull out) and from you to make it more personal and sharpen the driver's hazard perception. I also tried to add the fire emoji, but this will need to be tested to ensure it's not perceived as inappropriate or childish.
For the body, I took up the suggestion given with the assignment to use click-bait tactics as a force for good. The first words are road closures: we don't actually know if there are or there will be road closures on their itinerary, but we want users to be aware of the danger, stop for a moment, and look for more information.
Alternative copy for feedback/testing
Headline:
Incendio a [nome città/località]
Body:
Controlla i blocchi stradali sul percorso.
Day Five
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
Day Seven
Scenario
A sports fan is at a wedding while their favorite 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
Solution
I'm far from being the target user of this app, but oddly enough, this might have been the easiest challenge of all 14. This time, the character constraint was not daunting at all since I could rely on a consolidated "code" that football fans could easily decipher. I added a football emoji so users can immediately place the notification in context if they are distracted by something else and tested the message with four friends – not a broad sample, but everyone immediately understood all elements.
Day Six
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
Day Eight
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 favorite 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
Solution
This challenge looks pretty straightforward but hides two key issues:
1) Should we directly mention that users' listening behavior is why we show them this specific live event? Should we say that the band is one of their favorites, one they have often been listening to?
2) Why is a music player app promoting a live event? What's exactly our business goal for this message?
We are not our users, but I followed my gut and replied no to the first question. In this case, we might not even notice how/why the app is tracking our behavior or find it harmless; still, it's always creepy the feeling of being observed.
Therefore, I wrote just the artist's name – in the body instead of the headline so we limit space issues that might arise for longer names. I repeated twice (but in different forms) that the event is live to avoid confusion and hinted at the specific set of emotions brought by a live concert.
I labeled the button referring to an exclusive promotion/presale to get users engaged and have them find out more.
Alternative copy for feedback/testing
Headline:
Patti Smith dal vivo a Verona
Body:
A giugno prova l'emozione della musica live.
Button:
Partecipa all'evento
Day Nine
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
Solution
Here, I used the heading to state the issue clearly (the card is expired), and the body to identify the action required (use another card).
I went a bit further and added two buttons marked as alternative options by or (Change card or Pay on pickup). We need to give users a way to complete booking a car without paying by card, should they not have another one available; otherwise, they might drop off altogether and go for another rental service (or another way of transportation).
I also mentioned the "online discount" applied when paying by card – this way:
-
users are encouraged to proceed with online payment, and we reduce drop-off or payments on pickup
-
users are reminded that the price they are about to pay is not the same as the price they would pay on pickup
-
we add a positive element (a discount) to a message that appears in a situation that is frustrating and potentially stressful for users
Day Ten
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
Solution
For this challenge, I used the frame of a search tool that could be used to find cars on sale in a specific area. I've added the keyword deals in the body and the button and used hints as placeholder text to avoid confusion on the name (just the first name, or first name + surname?) and the ZIP code.
Should I have a product manager to speak with, I would have probably Slacked them: why are we asking their first name?
Alternative copy for feedback/testing
Button:
Trova offerte
Day Eleven
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.
Headline: 60 characters max
Meta Description: 160 characters max
Solution
Another pretty straightforward challenge. I researched the keywords that users google when buying contact lenses and packed them in a meta description that would be SEO(and user)-friendly. I also quantified how much customers could save, to help them visualize the benefit of a subscription.
Day Twelve
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
Solution
For this challenge, I provided a copy similar to day three's. Instead of declaring the name invalid, I ask users if their name is correct. The question helps get users' attention and gives two options:
1) rewriting the name (if misspelled)
2) jumping to a screen or lightbox where they could confirm it
I left the field border and the copy in black, but it might help to have them in another color to show that further action is required.
Day Thirteen
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
Solution
The goal here is to alert the driver that they might need to change their schedule, not act as if we know better and have already decided for them. I phrased the headline as a question, and in the body, I recapped the number of deliveries left before stopping for fuel (without mentioning they might be too many to complete in one go). The label text of the main CTA button mirrors the headline question, and there's a second button that allows users to ignore the notification.
Day Fourteen
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
Solution
Here, I played with an expression generally used before commercials: we'll be right back. Not to be misleading (and to make the tech team happy), instead of right back I chose a more generic shortly. I mentioned a technical issue and repeated we'll be back with the price the user is looking for, to keep them engaged. I also offered to be notified when the app is working again, giving the option of receiving a push notification.
Some final notes
Thinking outside the box, yet not too far
For each exercise, I tried my best to shy away from overused microcopy (Scopri di più, Entra nel club etc.) without offering overly creative solutions that might puzzle or alienate users.
We are so used to clichés and collocations that we easily forget that there might be better ways to express a concept – words more precise, concrete, or suggestive.
Still, we don't have (always) to reinvent the wheel or force humor or cleverness into our copy. Users might scan a screen for specific words: we can reduce their cognitive load and frustration by meeting their expectations and using plain, clear language.
Conciseness – Italians don't do it better
This challenge was initially mounted on English-speaking writers. When it comes to conciseness, English has a considerable advantage over Italian: its love for compounds. In Italian, adding a preposition between two nouns is often necessary to clarify their logical relation, and adding an article to sound human. This makes it harder to work within tight constraints and pack meaning in few characters.
Sometimes the questions are more relevant than the answer
Having just a few minutes to develop a solution doesn't necessarily translate into excellent copy. Still, the words are not the (only) focus here: this is why I run for each challenge a quick research session. Writing is the fun part, but it is equally important to practice what comes before and after – understanding the product, its business goals, the users, and their journey.
Big thanks to Nathan Guo, who provided a free Figma file with the UI templates.