Confidence determines Speed vs. Quality

A product-development heuristic that relates investment in speed and quality to evidence about both the importance of a problem and the suitability of a solution. Weak evidence favors quick, limited learning; strong evidence about both can justify durable implementation. Confidence in the problem and confidence in the solution are separate judgments.

Brandon Chu’s framework asks two separate questions: how well do you know that the problem matters, and how well do you know that the proposed solution works? When both answers have strong support, durable implementation becomes a worthwhile investment. When the need itself is uncertain, a small, quick inquiry can prevent months of polishing something nobody needs.

Treat speed as the time to useful learning and quality as fitness for the current purpose. A quick prototype can still have clear wording, accessible controls, and responsible handling of information. Conversely, a polished interface can be a poor experiment if it cannot distinguish whether the underlying idea is useful. Your confidence should change with evidence, and your investment should change with it.

When to use it

When deciding how much effort to put into a prototype, a tested feature, a course, a recurring service, or another activity whose continued usefulness is uncertain.

How it can help

Use it to decide whether the next effort should investigate a need, compare solutions, or improve a solution that already has support. It helps make disagreements about polish and urgency more specific.