# User stories

> Learn how to base your user stories on user goals and keep the product user focused.

Source: https://uxspot.io/user-stories

<section id="user-stories">
<div id="understand">
<h2>Understand user stories</h2>
<img src="/images/user-story.webp" width="2400" height="1330" alt="User story template — As a (type of user), I want (action), so that (benefit)" title="User story template">
<p class="blockquote">A user story is a fictional one-sentence story told from the point of view of a persona to inspire and inform design decisions.</p>
<p>It introduces the user, describes an obstacle, and states their goal. Don't be confused if you notice some designers refer to these <strong class="highlight">as scenarios or user cases,</strong> they mean the same thing. Now let's look at the goal, structure, and benefits of user stories. <strong class="highlight">The user story extends the persona and deepens the understanding of a user group.</strong> Here are some nice things a user story can do for you.</p>
<p><strong>User stories prioritize design goals.</strong> If you've a lot of user needs to address, user stories can help you determine which needs need to be solved most urgently.</p>
<p><strong>User stories unite the team around a clear goal.</strong> A good user story can also inspire insightful design decisions by making our approach user-centered, also known as user-centric</p>
<p><strong>User stories personalize pitches for stakeholders.</strong> You're not just pitching your ideas for design updates. You're showcasing how it will help specific groups of people. User stories have a hero with an ultimate goal and a conflict that keeps him from achieving that goal.</p>
<p class="blockquote"><strong class="highlight">As a type of user,</strong> I want to <strong class="highlight">action,</strong> so that <strong class="highlight">benefit.</strong></p>
<p>Now we just need to fill in the missing pieces. The <strong>type of user</strong> describes who we're developing the product for. <strong>Action</strong> is what the user hopes will happen. And finally, <strong>benefit</strong> is why the user wants the action to happen. This formula keeps the problem user-centric, actionable, and clear.</p>
</div>
<ul>
<span>keywords</span>
<li>#UserStory</li>
<li>#User</li>
<li>#Obstacle</li>
<li>#Goal</li>
</ul>
<div id="consider">
<h2>Consider edge cases</h2>
<p>An edge case is a situation within a product that the product team thinks is unlikely or outside of the typical product flow. When you are trying to figure out what the edge cases are for your product, you really need to sit down with users and see what their real lives are like with your product.</p>
<p>With user stories, as with any story, <strong class="highlight">there's always a chance that things will not go exactly the way you want them to, but you can always change the user experience.</strong></p>
<p class="blockquote">As a UX designer, when developing a new or improved product, the designer's goal is to keep all users on a good path.</p>
<p>Often, what you think will happen when a user holds your app in their hands is not what actually happens. Identifying these cases is key to creating a harmonious experience when things do not go as you planned.</p>
<p>Here are a few tips on how to avoid them:</p>
<p><strong>Create personas and user stories.</strong> If UX designers make sure their personas and user stories take into account a variety of users and issues, they can keep even the most vulnerable users on a good path.</p>
<p><strong>Thoroughly review the project before launching.</strong> In the rush to launch a product, UX designers may focus only on the <strong class="highlight">"happy path."</strong> A final review of the project from the user's perspective helps designers identify problem cases.</p>
<p><strong>Always use wireframes.</strong> They will help you visualize the whole project, that way, you will be able identify edge cases and improve them.</p>
<p class="blockquote">Good design is all about attention to detail. It's that commitment to designing for each scenario that sets great experiences apart from average ones.</p>
<p>As a designer, make it your mission to plan for those edge cases. They will occur whether you design for them or not.</p>
</div>
<ul>
<span>keywords</span>
<li>#EdgeCases</li>
<li>#ProjectReview</li>
<li>#Wireframing</li>
</ul>
</section>