bad user stories examples

Avoid "The Worst User Stories: Real-World Examples (& What to Do)

By Nicole Taylor
AD

Imagine you're a product owner or a software developer tasked with turning user needs into well-defined, actionable tasks. Sounds straightforward, right? But what if you're given a user story that's vague, incomplete, or confusing? That's where bad user stories come into play, creating more harm than good. Let's dive into some common examples to understand what makes a user story... well, bad.

To create effective user stories, we'll follow the format: "As a [type of user], I want [some goal] so that [some reason]". This structure, coined by Mike Cohn in "User Stories Applied", helps create clear, concise, and useful user stories. Now, let's examine some anti-patterns, presented in a fictional product context: a simple task management app.

Avoid Vague and Ambiguous User Stories

Vague user stories are like light switches with burnt-out bulbs - they don't provide enough clarity to guide development efforts.

AD
UI UX Design Agency for SaaS, Fintech & AI | Adam Fard UX Studio
UI UX Design Agency for SaaS, Fintech & AI | Adam Fard UX Studio
a notebook with writing on it and an image of user stories written in the top right corner
a notebook with writing on it and an image of user stories written in the top right corner
a man walking down a sidewalk next to a park
a man walking down a sidewalk next to a park

Example: "As a user, I want to be able to do stuff so that it's cool."

Vague Goals

When the goal is not clearly stated, it opens the door to assumptions and misinterpretations. The user's intention could be anything, and the developer is left guessing.

the user story and appliance citeria is shown in this graphic above
the user story and appliance citeria is shown in this graphic above
User Stories Definitive Guide
User Stories Definitive Guide
¿Cómo dividir epics e historias de usuario grandes?
¿Cómo dividir epics e historias de usuario grandes?

Example: "As a user, I want to have a button. ________" (Fill in the blank - what's the purpose of this button?)

Lack of Context

Without a 'so that' clause, we're missing the 'why' - the reason behind the user's goal, which provides crucial context and creates a direct link to the user's needs and satisfaction.

AD

Example: "As a user, I want to be able to delete tasks." - Why? What's the benefit for the user?

how to write an agile user story infographical poster by kravee on devisy
how to write an agile user story infographical poster by kravee on devisy
INVEST in your User Stories – Nimesh Soni
INVEST in your User Stories – Nimesh Soni
User Stories vs Job Stories
User Stories vs Job Stories
User Story Templates
User Story Templates
User Story for Agile Development Projects: Why create user stories? How to Write User Stories?
User Story for Agile Development Projects: Why create user stories? How to Write User Stories?
two different types of user story and user story, each with their own text or image
two different types of user story and user story, each with their own text or image

Large Stories are a Developer's Nightmare

User stories that describe a bunch of features or functionalities can overwhelm developers and make it difficult to estimate effort or prioritize work.

Example: "As a user, I want to be able to add tasks, edit tasks, delete tasks, and to do this, I need to be able to create user accounts, log in, manage my profile, and sync my tasks across devices." - That's more than one user story!

AD

Feature Lists

User stories thatात्मक consist of lists of features are often too broad and lack definition. They make it hard for developers to understand what needs to be done and how to approach it.

the user story writing framework is shown in this screenshote, which shows how to use
the user story writing framework is shown in this screenshote, which shows how to use

Example: "As a user, I want to be able to create, read, update, and delete tasks." - That's a whole lot of CRUD actions, but what does the user really want to achieve?

Epic Stories

Epic stories describe large, multi-step processes or workflows. While they can be helpful for high-level planning, they should be decomposed into smaller, manageable, and clean user stories before work begins.

AD

Example: "As a user, I want to invite my team members to collaborate on tasks, so we can manage our workload together." - That's a complex workflow involving several user interactions and system responses.

dependencies Without Solutions

While it's important to note dependencies, ignoring the 'as a' part, or neglecting to provide a solution for the dependent functionality, can lead to circular references and other nasty side effects.

Example: "The 'add task' feature depends on 'user authentication'." - Yes, but how does the user authenticate? This story is incomplete without a solution for the dependent feature.

Forgetting 'As a'

Omitting 'As a' in a user story forces developers to assume who the user is, which can lead to incorrect assumptions about the user's needs and context.

Example: "The 'edit task' feature depends on 'task selection'." - Who needs to select the task? Why? Understanding the user is key to understanding the story.

Lack of Solution for Dependencies

Ignoring dependencies without proposing a solution leaves developers stuck, unable to proceed or make progress on their own.

Example: "The 'task commenting' feature depends on 'user authentication'." - Sure, but how does the user log in? What happens if they're not authenticated?

Understanding bad user stories helps us create better ones. By following the templates and best practices we've discussed, we can transform those light switch dimmers into bright, focused, and useful user stories, guiding our development efforts towards meaningful and useful outcomes. So, the next time you're crafting a user story, ask yourself: Is this clear? Is this concise? Does this meet a user need? If you can confidently answer 'yes' to these questions, you're well on your way to creating effective user stories.

AD