Every Product Should Be Working Toward a Zero Known Bug Backlog
P4s don't have to languish at the bottom of the backlog anymore. With the right investments, fixing bugs as they arrive can cost about as much as triaging them used to.
I think every software product should be working its way toward a zero known bug backlog if it's not already there, and make a commitment to maintaining that.
We don't have to live in a world where our P4s languish forever at the bottom of the backlog anymore. With the right investments in place it can be just about as much effort to feed them to our bug smashing machine as soon as they come in as it used to be to figure out where they belonged in priority.
Users will notice.
Related insights
3,122 PRs This Year, and Most of Them Are Just Bets
Shipping thousands of changes doesn't create value on its own. Every change is a bet with a cost, so the real leverage is using your tools to make better bets, not just more of them.
Vibe Code to Explore, Engineer to Expand
Vibe coding is perfect when you're still finding out if anyone wants your thing. Once real usage and real money show up, agents make software engineering matter more, not less.
The Golden Age of Prototypes (and The Other 90%)
AI agents get you to 90% of a working product faster than ever - but the real challenge is the other 90%
Get More Like This
Follow along as I build and share what I learn
Found this helpful? Share it with your network!