By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres and Petra Wille argue that a giant, messy product backlog is a symptom of unclear filtering rather than a ranking problem. They question whether scoring frameworks like ICE and RICE help when hundreds of items are involved, and suggest instead narrowing the field first. Their tactics include auto-closing stale tickets, archiving items nobody understands, and tagging work by theme, initiative, or user group. They also cover using outcomes and customer needs as strategic filters, securing early wins when inheriting a product, and carving out discovery time even in a feature factory. The episode matters because most PMs spend effort ordering backlogs that should have been pruned first.
01Key takeaways
- Prune stale and unintelligible backlog tickets before attempting any ranking.
- Use auto-closing rules to remove old items without manually reviewing each one.
- Tag backlog items by theme, initiative, or user group to make them easier to filter.
- Filter by desired outcomes and customer needs rather than scoring hundreds of items.
- Secure early wins and a time-boxed onboarding period when taking over a product or team.
- Reserve dedicated discovery time, even in a delivery-heavy feature factory.
02Key sections
- The problem with scoring models
- The hosts question whether ICE, RICE and similar scoring models are useful when a backlog holds hundreds of items. Ranking everything consumes time without solving the underlying clutter.
- Clean up before you prioritize
- Auto-closing old tickets and archiving items no one understands removes noise cheaply. Tagging by themes, initiatives, or user groups makes the remaining work easier to see and navigate.
- Filter with strategy, not scores
- Rather than ranking every item, use outcomes and customer needs as filters to decide what deserves attention. This keeps the focus on impact instead of volume.
- Onboarding and early wins
- When inheriting a product or team, a time-boxed onboarding period and a few early visible wins build trust. These create room to change how work gets managed.
- Hidden work and discovery time
- Stories such as a one-day database project that took a week reveal how much work is invisible in backlogs. The hosts also suggest protecting discovery time even inside a feature factory.
03From the post
“Listen to this episode on: Spotify | Apple Podcasts Drowning in Jira tickets? Wondering how to prioritize when every stakeholder has a “brilliant” idea and your roadmap is already bursting at the seams? In this episode of All Things Product, Teresa Torres and Petra Wille tackle one of the most common”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.