I recently came across Linear’s zero bugs policy.
I love Linear — as a product and as a business — that I have taken a ton of inspiration from in recent years
They turned project management tooling from “I want to bang my head against the wall” to “I feel inspired to build better things”. No one has ever said this about Jira.
Linear is not just a swish and fancy and fast interface. It’s a reliable interface and product.
So coming across the concept of a “zero bugs” policy on their site doesn’t exactly startle me. But even as good as Linear is, it is an extremely rare and surprising goal for any software team to have, let alone one in B2B software.
As a user of a tool, the idea of having no bugs is of course very attractive. Who wouldn’t want that?
But as a team, and as a business, it’s an incredibly noble goal to have and a very difficult one to maintain.
Fixing bugs isn’t sexy. New features are sexy. Ensuring you don’t lose out to competitors through lack of functionality is the priority… usually.
Focusing on eradicating all bugs is as sure as anything a sign that you deeply care about and listen to your users and customers.
I’d wager that you also could never dream of setting this goal unless you frequently use your own product. So many bugs are not reported by users, they are only evident through user testing and using it yourself.
The benefits of a zero bugs policy are evident from Linear’s own post — fixing things and fixing them fast delights customers. Keeping on top of bugs ensures your backlog doesn’t overflow into a horrible swamp of pain.
I’m proud that we’ve always cared about bugs and moved mountains to fix issues quickly at both GoSquared and EcoSend. We’ve seen first-hand how that can delight customers.
But we have some work to do before we get to “inbox zero” on bugs. That, of course, is evident as Linear is telling me so right now.
I’m curious, are you aware of any tools or teams that have their own zero bugs policy or similar?



