Quality is a choice

“Our product should be perfect, with zero bugs! Also, our budget is limited.”

The truth is that quality isn't an exact science. Perfection comes at a cost.

What to consider when determining the level of quality:

  1. Industry context: Highly regulated sectors demand rigorous QA. For non-critical products, speed to market can be balanced with zero flaws.
  2. Product maturity: Early-stage products can tolerate some imperfections if they deliver value. As the user base grows, the margin for error shrinks.
  3. Time allocation: Every hour spent on testing is not spent on new features. Choose wisely.
  4. User feedback: Sometimes, launching and iterating based on real-world usage is better than aiming for theoretical perfection.

Quality is a deliberate choice, not a fixed set of measures. A technical leader's job is to balance quality and speed at each stage of the product's lifecycle.