UX writing exercise
Picture this: You slept in on a work day because you forgot to set your alarm, so now you're running late to work. You jump in the shower with a razor in one hand and a toothbrush in the other. You almost mix them up, yikes! That was a close call. You don't have time to make anything for breakfast, so you try to place an order on the Dunkin' Donuts app for pickup on your way to work. Now, to make it even worse, you run into problems ordering your favorite morning treat.
This is an error message that displays in the Dunkin' Donuts app when you try to purchase a donut that isn't available... confusing, right? Now, not only are you late to work, but you can't order your favorite donut, and you don't even know why.
This error message was probably written by a programmer. No hate, no shade, but this copy doesn't tell the user what the problem is in a way they can understand.
I rewrote the error message so the user gets a better understanding of what's going on and how to proceed. I used a light and playful tone to ease any frustrations that this inconvenience would cause for a customer that can't order what they want from the menu.
With the proposed solution, you're still upset you can't get your favorite morning treat, but at least you're not experiencing another trigger on what feels like a day where everything is going wrong.
You try something new, and it turns out that you like it better. Yay, new favorite donut!