Pod Insights The Agile Daily Standup - AgileDad If You Want Better Stories, Stop Writing Them All Yourself About this episode If You Want Better Stories, Stop Writing Them All Yourself
I’ve talked to a lot of product owners who are drowning in tickets, trying to “get ahead” by writing every single user story themselves.
I used to be one of them. And every sprint, we’d slip. Morale tanked. The team blamed the process, and I blamed myself.
But after one conversation — and one uncomfortable realization — I found a single thread running through every success story I’ve seen since.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 What if the fastest way to fix your backlog was to stop touching most of it? Hear me out. I'm not talking about quitting your job or abandoning your team to chaos. Although maybe kind of. I've talked to a lot of product owners who are drowning in tickets, trying to get ahead by writing every single user story themselves. I used to be one of them. And every sprint, we'd slip, morale taint, we fell further behind. The team blamed the process, but in all honesty, I blame myself. But after one conversation and one uncomfortable realization, I found a single thread running through every success story I've seen since.
1:00 Speaker 00 That thread, if you want better stories, stop trying to write it all yourself. Stop trying to do it all yourself. Start getting the right people to write them with you. So here are the three things that you need to do in order to make that happen. The first two will kind of get you into a position and the last one is probably the one you're going to focus your attention on. So here we go. Start out by figuring out who knows the most about the work and let them lead the writing. So for example, in my world, if you've ever taken an Abadi class before, I teach a concept called Po Ba Fat, where a product owner, business analyst, functional analyst, and technical analyst all work together towards building a backlog.
1:43 Speaker 00 So this is something that is a new internal component that is going to be used to help ensure security. You want to make sure someone from the security team is present to help formulate and write, even if they may not be technical, it's okay. You want to make sure that person's there to help make certain that you're writing things in the correct vein or in the correct direction, that you're moving towards the North Star goal. If this was customer phasing, you want to make sure you have a business analyst and understands all the consumers wants, needs, wants, desires, etc. So what I'm saying is dependent on who the product or service is for, who your target audience is, become more outcome focused.
2:24 Speaker 00 And this is going to solve the problem. If you ask me, for example, I may not be the best person to find all the details of an API change.
2:35 Speaker 00 But a senior developer could be, right? I just need to know what problem is resolved, so let me write.
2:43 Speaker 00 You know, at first, it felt like I was giving up control. But then I realized that after saving hours of back and forth and making decisions and having people there, having a technical analyst to give me that information made a lot more sense. So when you do this, you want to make sure you have the right people in the room having the right conversation. And for me, that constitutes product owner, business analyst, functional analyst, technical analyst. Let's go to the second one.
3:10 Speaker 00 How do you make it clear that the team's job is to shape the work, not just deliver it? If you can make everyone feel like their input changes the outcome,
3:21 Speaker 00 then you'll never have to sell them, you don't have to sell the team on a feature again. They'll own it from the start because it was partially their idea, and I think that's where we're trying to get with this. I think when teams feel excluded early, they tend to disengage. And when they disengage, quality is the first thing that suffers. Sometimes this means inviting a technical analyst or a couple of lead engineers in. E- even in early design discussions that they can be present to make sure that everything is flowing well. Sometimes it means letting QA write some of the Gherkin acceptance criteria before the devs even see the ticket. The point is, pull the work into the open before it's finished.
4:03 Speaker 00 And then on paper, it's gonna look messy at first, but in reality, you're gonna get more momentum by doing things a little bit upfront that way. This is part of the whole ideation, initiation, discover, before you do deliver and release, right? Four phases.
4:22 Speaker 00 So let's talk about facilitation. Look, chances are you're already doing backlog refinement. Most organizations are. It's only one hour a week per team, so it's not that much heavy lifting. Preempt the bottleneck by changing what happens in that meeting. I used to show up with a stack of polished, ready to assign stories and the team would nod, ask a question or two, and quietly rewrite half of the stories later. Now I show up with just a handful of messy notes, a problem statement, and the right people in the room to solve the problem. The designer sketches, the engineer flags risks. Somebody who's specialist in testing talks about edge cases. Together, we turn that mess into usable stories in real time.
5:06 Speaker 00 It's more than, it's more work for everyone in the moment, I guess. But far less work after the fact because we end up with something that's higher quality. It doesn't need to be reshaped, revamped, and redelivered. So my crazy idea is next time someone asks, "So what's in the backlog this sprint?", don't hand them just a polished list. Invite them to help study it, create it, make it. Include the right people as part of your Ba Fatah. Now, one of the number one questions I get from people sometimes is, "Does that mean you can only have one ba, one fa, one ta for each product owner?" And the answer is, well, you should only have one product owner. And each product owner should have a designated business analyst.
5:50 Speaker 00 Your functional analyst and technical analyst could be multiples. So that has happened. We have multiple technical analysts to help solve a problem. Or multiple functional analysts from the business side who want to make sure strategically we are marching in the right direction and we're doing the right things. It doesn't mean that I'm promoting or condoning a pooled product ownership. I want to be clear. At the end of the day, the product owner is still the single ring of the neck and gets the final decision. But I do feel like product owners that are trying to make every decision and write every card in a bubble.
6:23 Speaker 00 Are going to be the ones who suffer the most when it comes time to do the actual work because they're not taking advantage of the input that's readily available to them. That's going to do it for this episode. I hope that you enjoyed it. 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.
Previous Velocity = The Most Abused Agile Metric Ever Next 10 Mistakes Enterprises Make When Scaling Agile — and How to Avoid Them Page updated November 6, 2026 · transcript and summary are machine-generated