Context: Story writing is a team effort. It’s an opportunity to involve the business and build teams to capture design intent and their requirements. Use personas to describe different user roles when writing user stories, avoiding generic "the user" references. Write concisely, ensure scenarios and acceptance criteria match wireframes and mockups, and remember the "3 Cs" formula: Card, Conversation, and Confirmation.

Guidelines:

• Involve the business and build teams to capture design intent and requirements.
• Use personas to describe different user roles, avoiding generic references to "the user".
• Write concisely and in plain language.
• Ensure scenarios and acceptance criteria match wireframes and mockups.
• Follow the "3 Cs": Card (tracking history), Conversation (discussions), and Confirmation (agreement on outcomes).

What to Avoid:

• Vague or overly long task descriptions.
• Writing from your own perspective ("As a designer, I want").
• Writing too many stories from the business perspective, especially when user interaction is involved.
• Stories without business value or user benefit in the "so that".
• Stories that don't include clear acceptance criteria.

Example Structure:

As [persona],
I want to [goal],
so that [benefit].

Acceptance Criteria:
- [Criteria 1]
- [Criteria 2]
- [Criteria 3]

Task: Create a user story for a UX design professional using the provided guidelines. Include the persona, their goal, the benefit, and clear acceptance criteria.