This article is my response to the following user experience writing challenge:
|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.|
|Body: 45 characters max|
Body: 15 characters max
I drafted two versions of a response to the challenge. I considered what sort of messaging I would like to receive for a request to provide my name and location. Then, I referred back to the challenge as it pertained to tone.
|DRAFTS||VERSION A||VERSION B|
|Body||Please provide your name and ZIP code to find your car.||We need your name and ZIP code to find your dream car.|
|Button||Enter Info, Skip||OK, Cancel|
Body Approach: The challenge uses the word ‘ask’ for the prompt. I decided to write imperative sentences that as opposed to interrogative sentences. Both versions provide the incentive of finding a vehicle for the user. It lessens the chances of users thinking the message is an arbitrary data request.
Button Approach: The two affirmative responses to submit personal information are ‘Enter Info’ and ‘OK.’ ‘Enter Info’ provides a direct call-to-action, while ‘OK’ is just an acceptance of the request. The rejection buttons ‘Skip’ and ‘Cancel’ are common words on the web. ‘Skip’ implies moving on to the next step, while ‘Cancel’ halts the process.
FINAL DRAFT: My biggest consideration was tone for the challenge. After considering the pros and cons of both drafts, I decided to incorporate elements from versions to produce the following:
|Body||Please provide your name and ZIP code to find your car.|
|Button||Enter Info, Cancel|