Determine whether to optimise for speed or quality based on your confidence in the direction
Contents
I send a newsletter every week — free, no spam, unsubscribe anytime.
| Dimension | Best fit |
|---|---|
| Decision type | Resource allocation decisions where execution mode is a choice — how much time, money, and craft to invest in a given initiative. Particularly powerful for product development, market entry, feature prioritisation, and strategic pivots where the team has latitude over how (not just whether) to proceed. |
| Organisational context | Teams that have a cultural default — always fast or always careful — and need a mechanism to override it situationally. The framework is most valuable where it creates friction against the prevailing bias, forcing speed-obsessed teams to slow down on high-confidence work and quality-obsessed teams to ship rough on low-confidence bets. |
| Information environment | Situations where confidence can be meaningfully assessed — where the team has enough context to distinguish between "we know this" and "we're guessing." Falls apart when the team lacks the self-awareness or domain knowledge to rate their own confidence accurately (see Section 4). |
| Stage of initiative | Most powerful at the beginning of an initiative and at each major inflection point. The initial calibration sets the execution tempo; the reassessment loop prevents the team from locking into a mode that no longer matches reality. Less useful mid-stream on a well-defined project where the mode is already set. |
| Failure pattern | What goes wrong | What to use instead |
|---|---|---|
| Overconfidence bias | The framework assumes you can accurately assess your own confidence. Humans are systematically overconfident — particularly founders, particularly about their own ideas. A team that rates confidence as "high" when it's actually medium will invest in quality mode prematurely, building durable infrastructure on an unvalidated foundation. The most dangerous version: the CEO's conviction is mistaken for evidence. | Pre-Mortem to stress-test confidence; Delphi Method for calibrated group estimates |
| Speed mode as permanent state | Some teams use "low confidence" as a perpetual justification for shipping rough work. They never transition to quality mode because they never formally reassess. The result is a product built entirely of experiments — a Frankenstein of MVPs that no one would choose to maintain. Speed mode without a reassessment trigger becomes an excuse for sloppiness. | Build explicit confidence thresholds that trigger mode transitions; Eisenhower Matrix to force prioritisation of quality investments |
| Binary thinking | The framework is a spectrum, but teams often collapse it into a binary: fast or careful. Real projects contain components at different confidence levels simultaneously. The database schema might be high-confidence (quality mode) while the pricing model is low-confidence (speed mode). Applying one mode to the entire initiative wastes resources or creates risk. |
| Reversibility spectrum | Especially useful when the decision sits in the middle of the reversibility spectrum — not obviously one-way-door or two-way-door. These ambiguous cases are where teams most often default to cultural habit rather than deliberate calibration. The framework forces the analysis that Bezos's Type 1/Type 2 distinction leaves implicit. |
| Resource constraints | High-leverage when resources are finite (they always are, but especially at startups and growth-stage companies). The framework's core function is preventing the two most expensive resource misallocations: over-investing in uncertain directions and under-investing in validated ones. |
| Decompose the initiative into components and calibrate each independently |
| Confidence confused with preference | "I'm confident" sometimes means "I want this to be true." Emotional attachment to a direction masquerades as epistemic confidence. The team conflates desire with evidence. This is especially prevalent when the direction was the founder's original vision or when significant sunk costs have already been committed. | Ladder of Inference to surface the reasoning chain; require evidence inventory — what specific data supports each confidence rating? |
| Domains where quality is non-negotiable | In safety-critical systems, regulated industries, or situations with severe downside risk, "move fast" is not an option regardless of confidence level. A medical device startup can't ship a rough prototype to patients. A financial services firm can't test compliance approaches by violating regulations. The framework's speed mode assumes errors are tolerable and correctable. When they're not, the framework doesn't apply. | Reversible vs. Irreversible Decisions to identify non-negotiable quality floors; Regret Minimisation Framework for asymmetric downside scenarios |
| Stakeholder misalignment | The product team calibrates to speed mode. The sales team has already promised a polished product to a marquee customer. The board expects enterprise-grade quality. Confidence calibration done in isolation — without aligning stakeholders on what "speed mode" actually means in terms of output quality — creates expectation gaps that damage trust more than a slower timeline would have. | RACI Matrix to clarify decision authority; explicit communication of execution mode and its implications to all stakeholders |
Reversible vs. Irreversible Decisions applied the First Principles Thinking mental model
Reversible vs. Irreversible Decisions applied the Leverage mental model
Reversible vs. Irreversible Decisions applied the Technical Debt mental model
Reversible vs. Irreversible Decisions applied the OODA Loop mental model
Reversible vs. Irreversible Decisions applied the First-Mover mental model
Reversible vs. Irreversible Decisions applied the Narrative mental model