In Scrum, the standard format of a user story is easy to understand: “As a [role] I want [something] so that I can [benefit].” However, there is more difficulties inside the project team to agree on what constitute the content of a user story. In this blog post, Steve Johnson explores this issue.
You have problems when the user stories suggest already a solution or are bug fixes for poor design. Steve Johnson suggests the following solution: “Ideally, a customer expert should tell stories about users, a usability expert will convert these into user stories, and the product team can break those into tasks and deliverables. And this process is best done in a team setting so everyone benefits from the discussion.”
Read the complete blog post on http://under10consulting.com/2013/02/28/stories-about-users-and-user-stories/