Resources > Articles

Ask the Experts: Who is accountable for product defects?

Author
  • Rich Nutinsky

    Rich Nutinsky is a master instructor at Pragmatic Institute, with more than 20 years of experience in the software industry. He has launched several successful software products using the Pragmatic Institute Framework. Prior to joining Pragmatic Institute, Rich served in various management and product management positions for companies including Arasys Technologies, where he was vice president of product management and development. He has provided consulting services to market leaders such as Microsoft, AT&T, DuPont, NEC, GE and Siemens, working with senior-level executives to improve their product strategy, product management and marketing processes. He may be reached at [email protected].

Pragmatic Institute Logo and 3 verticals

In my experience, “defects” actually fall into two categories. The first group represents things that work exactly as we designed them to work, but that people feel don’t work correctly. In other words, they aren’t broken, they just aren’t very good. These actually aren’t defects at all; they are poorly designed features. They should be captured and added to the list of things we need to do. Whoever owns the “to-do” lists (enhancements, new ideas, product roadmap) should add these improvements to the list. Generally, that’s product management. Those items need to be analyzed, reviewed and prioritized along with everything else on the list.

The second kind of defect is one where the product doesn’t work as designed. In other words, it is broken. If it adds a column of numbers and gets the wrong result, that is a defect. In those cases, these items shouldn’t have to get in line or be analyzed or prioritized. They should be fixed. Development should own these, assess how the defect happened and fix it as soon as possible. Once that’s completed, product management should be involved in deciding when to deliver a fix to the market.

One more comment: If the second type of defect is a common occurrence, it could be a quality issue. Usually, quality is a policy issue, a function of management policy and standards. Some companies have a zero defect policy, resulting in high-cost—and sometimes much slower—development processes. Others choose lower costs or quicker delivery as a policy objective, sometimes resulting in quality issues. Should you start to see a growing number of defects, it may be time to look more closely at your policies.

Author
  • Rich Nutinsky

    Rich Nutinsky is a master instructor at Pragmatic Institute, with more than 20 years of experience in the software industry. He has launched several successful software products using the Pragmatic Institute Framework. Prior to joining Pragmatic Institute, Rich served in various management and product management positions for companies including Arasys Technologies, where he was vice president of product management and development. He has provided consulting services to market leaders such as Microsoft, AT&T, DuPont, NEC, GE and Siemens, working with senior-level executives to improve their product strategy, product management and marketing processes. He may be reached at [email protected].

Author:

Other Resources in this Series

Most Recent

Revenue retention
Article

Net Revenue Retention: A Critical Indicator of Business Health

Net revenue retention is maintaining and increasing income from existing customers over time. So it’s a critical metric that impacts the sustainability and scalability of any business
Article

Four Methodologies for Prioritizing Roadmaps 

In this blog, we'll explore four common approaches to roadmap prioritization and discover the practical tools and frameworks that can propel your product to new heights.
Prism photo: Product management Lessons from Pink Floyd
Article

Product Management Lessons from Pink Floyd: a Lighthearted Look into Their Epic Music and Unlikely Product Expertise

Few people (actually, no one!) spontaneously associate product management with Pink Floyd, but if you look closely, you can find good examples of best product management practices in their journey, as I hope to reveal...
Creating a product roadmap: what should you include
Article

A Guide to Product Roadmaps: How to Build One That Works

A product roadmap is a frequent request from the sales force and others in the company. ‘What’s coming in the next release and the ones after that?’ Long buying cycles common with strategic products often...
Dry erase board with product roadmap drawn on it
Article

How to Build a Brilliant Visual Product Roadmap

Building roadmaps is a crucial part of a product manager’s job. Yet most product managers still use outdated tools for roadmapping—Excel, PowerPoint, wikis, etc. The good news is that there’s a better way. Executives have...

OTHER ArticleS

Revenue retention
Article

Net Revenue Retention: A Critical Indicator of Business Health

Net revenue retention is maintaining and increasing income from existing customers over time. So it’s a critical metric that impacts the sustainability and scalability of any business
Article

Four Methodologies for Prioritizing Roadmaps 

In this blog, we'll explore four common approaches to roadmap prioritization and discover the practical tools and frameworks that can propel your product to new heights.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe