A sales manager at Cloud Kicks recently learned about Salesforce Macros and believes service agents could benefit from the feature. The sales manager created the following user story: "As a service agent, I want Salesforce Macros to complete repetitive tasks faster."
What should the business analyst change to improve the user story?
The user story should focus on the goal rather than a specific feature. By replacing the specific feature with a goal, the story remains solution-agnostic and emphasizes the desired outcome. This approach also aligns better with best practices for writing user stories, which generally follow the format: As a [user persona], I want [goal], so that [reason].
User stories are often written from the perspective of the User Client and more often than not the client wont know the specific SF feature so doesn't make great sense to include it in the user story, also user stories don't need to include quantifiable data as a reason for what they need So in this example, the more accurate way to write this could be - 'As a service agent, I want the ability to complete repetitive tasks quicker, to save time on customer service etc etc' Writing it like this also fills in the Who, What, Why criteria for SF user stories https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user-stories
Answer is C not B as the user story should not contain a specific feature like it does with macro's.