Pod Insights The Agile Daily Standup - AgileDad Stop Using User Stories.. I Think Not About this episode Stop Using User Stories.. I Think NotSomeone Asked me to review an article about user stories... Lets just say it is a mixed review. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 Someone recently sent in an article, I thought this was kind of funny. The article is called "Stop Using User Stories." And at first, I have to admit, I had a cringe moment. I'm like, oof, is it gonna be another one of those? And it starts out, "As product managers, we prioritize our backlog items based on user stories. Let's stop." That's typically not how I prioritize my backlog. But we'll keep going and see where he takes this. "But I have seen a very fundamental problem with the way we approach writing each user story. Traditional user stories, despite their popularity, often fail to clearly define what we're building and why." Okay, that I can get on board with. I think that the way traditional user stories are typically structured, there's not enough detail.
1:00 Speaker 00 "So user stories are simple descriptions of features from the perspective of a end user. They help the team focus on delivering value rather than implementing features." Right, right. "A traditional user story says, 'As a user type, I want to do this action so that I can receive this benefit.'" Or as a "who," "I would like to do what so that why." That's the way I like to put it. "As you can see, every user story tries to capture who needs the feature, what they want to do, and why it matters to them. It's very simple to understand, but this simplicity can create problems." Hmm, let's see where this problem is. "The main challenge with traditional user stories is that they don't distinguish between system-oriented needs and customer-oriented needs.
1:43 Speaker 00 When a story says, 'As a user, I want to view my transaction history so that I can track my spending,' it doesn't specify these four things clearly. What is the time period we should display? Should we also display all the pending transactions? How should we go about categorizing the transactions? What filtering options should we give our customers?" Let's pause there. I get where this is going, but I think that if we put more granularity, it actually may be bad for some people because then people have another decision to make. One of the hardest things about agile right now is all the decisions that need to be made. And I just sense that people would feel very uneasy making even more and more decisions. And this is just adding another decision to their plate.
2:26 Speaker 00 He says, that's why we need to split stories before it can be usable. And as a result, we lose time. I've seen my team spending entire sprint planning sessions just to break down these vague stories into implementable chunks using the invest format. So he's proposing two different types of stories. System stories that focus on the internal work, bug fixes, and performance improvements that don't directly involve end users. And that story we written action verbs, subjects, so that what our goal is achieved. Implement a caching system so that page load times are reduced by 50%.
3:00 Speaker 00 This format works well for technical debt, infrastructure improvements, and system enhancements. It doesn't force technical work into the user-centric framework. And then outcome stories focus on specific user needs in a very particular situation. And that would be when this opportunity happens, I want this action or activity so that I can achieve this outcome. Okay, let's just stop there. There's a lot more to the story, but I am gonna stop there. Here's what I know. In my world, or in the world of what I call simple agile, or easy agile, what you end up doing is everything is a story of some type. Now hear me out. We might have feature-driven stories, we may have enhancement stories, enabler stories, defect stories, they're all different types of stories.
3:43 Speaker 00 The intent of using the story designation is so that each story can be allotted story points, can be broken down, can be allocated across teams, can be rolled up to a larger item. We just want to keep it simple by calling all things story. Now that we got that out of the way. I'm not opposed to changing the description to reflect what type of story it is. So one of the things I think people miss out on is that all stories aren't just one type. All stories aren't user stories. So what I'm saying is, while I agree with what you're saying, I think it's causing a little bit of confusion. If everything's a story and then you say, what type of story?
4:26 Speaker 00 And then based on what type of story it is, you edit the description to match what you're trying to say, then I'm fully on board with what you're saying. But if you're saying that we need to now designate or create different types of stories and dictate that inside of our tool and separate it, break it out and have teams break it down further in sprint planning, I don't think all that's necessary. I think keeping it simple is the best option. Allowing the team to define with product owner how that description should be formatted and then figuring out ways to guide each other so that that format is maximized and works best for everybody. That's going to bring you the best results. Don't strain so hard. I would rather see you strain so hard in keeping things small in size than in trying to designate all the different types that you've been talking about. So for me, just remember, everything is going to be a story.
5:12 Speaker 00 Everything is going to be based somewhat on outcome. And depending on a story type, your description can change. So this way, everything's a story. Everything is story points. Everything's good to go. The team knows exactly what they need to do with it. And they're not spinning their wheels trying to, you know, formulate a description that doesn't fit into the type of story. They're just leveraging everything in such a way that it makes life a lot easier. So that's going to do it. I hope you enjoyed this. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye now.
Previous The Coaching Question That Makes People See Their Impact Next How To Improve Your Teams Motivation Page updated November 7, 2026 · transcript and summary are machine-generated