UX writing

B E F O R E

This messaging for those with no listings currently in Sale status only made sense to first time sellers. It was confusing to everyone else with Removed and Sold items, which they obviously had already listed (and could review on a different screen).
During a site audit while revising the style guide, I identified the semicolon here to be too formal.

A F T E R

I changed the tense, which implies "currently" while maintaining brevity. I also eliminated "yet" and specified item status instead.
The new color here (which matches the updated branding style guide) combined with the change to two sentences better highlights the CTA.

One of the many ways Meta aims to reduce fraudulent sellers advertising on their platforms is to gather feedback directly from buyers in the form of surveys. Noticing there was a decline in completed surveys via the prompt in the Facebook application, my team was tasked with creating a prompt to take the survey via a notification instead - which was sent to a small group of users to A/B test response & completion rates alongside the existing in-app prompt.

Working on the notifications menu screen was not something with which anyone in my orbit had had experience. So, I had to dig pretty deeply into Meta's content standards & style guides and research current and past approaches. I learned there were many reasons we could not simply use the same copy as the in-app prompt (alongside other challenges):

Notifications cannot be in the form of a question.
Notifications cannot be in the second person - and yet there was an express business need for this message to convey that it was Meta asking about the advertiser, not the advertiser requesting a product review.
Note in my screenshot how certain notifications are from other users, while the one at the bottom is from Facebook. There are separate style guides to use for actions related to users vs. those directly from Meta. Yet, to avoid user fatigue and void the entire experiment, the copy needed to also not overlap or too closely mimic other current or past Meta CTAs.
Given the limited number of characters allowed, there would be no way around the fact that part of the notification would be cut off in some cases (due to some advertiser names being lengthy). This meant the CTA could be buried if the name came first or early in the sentence.

After garnering constructive feedback on my drafts from fellow CDs and other content leaders in design crits, I landed on “Rate your experience with [advertiser name]”.

BEFORE

Header & CTA: The header's action verb is to Agree, while the button's action is Save and Print.
Voice: This paragraph uses both "I", meaning the user, and "We", meaning the company.
Timeline: "I will not expect a...Kit" is problematic, as the change of mind could often be after the Kit is already headed their way.
Technical directions: Saving and printing actually required additional steps found on the next screen, so the technical how-to should be there instead (edited, of course, to apply to more devices).

AFTER

Header & CTA: This alignment not only makes better sense but also draws focus away from the task of printing and back to making the update itself.
Voice: There's better flow now that this is consistent.
Earnings/cost: This valuable information previously only found during the listing creation and buried in the FAQs is now part of the update process itself. Plus, the tip about free materials keeps a conversational tone by assuring there doesn't have to be an out-of-pocket expense for having made this update.

UX Writing samples

short messages, big impact

Facebook app notification

BEFORE

AFTER