Skip to content

Smoke Test

Probe demand for a product that doesn't exist yet with a cheap false-front — a landing page, pre-order, or fake door — that extracts a commitment-bearing signal, and build only if that signal clears a kill threshold set in advance.

Core Idea

A lean-startup smoke test is a low-cost probe of demand for a product that does not yet exist — a landing page, pre-order form, fake-door ad, or Wizard-of-Oz mock — that collects a commitment-bearing signal (a click, an email, a card pre-authorisation, a deposit) approximating real demand without the expensive build. The structural commitment is cheap-signal-before-expensive-build: engineer the cheapest test whose signal still discriminates real from notional demand, and abandon the candidate if it falls below a preset kill threshold. A negative result is a valid, money-saving kill.

Scope of Application

The smoke test lives within product and demand-validation practice, across every tactic sharing its cheap-signal-before-expensive-build structure with the probe swapped.

  • Landing-page and fake-door tests — an unbuilt product behind a sign-up or "buy" button.
  • Wizard-of-Oz manual back ends — a façade fulfilling requests by hand before automating.
  • Pre-order and letter-of-intent campaigns — deposits or signed intent as high-commitment signals.
  • Software-engineering build-sanity smoke test — the literal sibling; filters function not demand.

Clarity

Calling a probe a smoke test makes legible that its job is signal value relative to test cost, not validation. It reframes "did people like it?" as "did this test, at the cost I paid, discriminate real demand from notional?" It sharpens the commitment gradient — a click, email, card, and deposit are not interchangeable evidence — and makes legible that a negative result is a result: a page with no sign-ups is a successful kill, not a failed experiment.

Manages Complexity

"Will this product succeed?" is an intractably high-dimensional question folding together market size, willingness to pay, competition, and timing, honestly answerable only by building the thing. The smoke test compresses it to a single tractable scalar: the rate at which a cheap probe converts a commitment-bearing action against a preset kill threshold. One measured conversion number stands in for the whole demand question, and the build-or-walk decision reads off that number rather than off a market forecast.

Abstract Reasoning

The smoke test licenses diagnostic reasoning (weighting a demand signal by what the respondent was made to risk, and reading absence of a costly yes as evidence against demand), interventionist reasoning (engineering the cheapest probe that could still make you walk away, escalating commitment until the signal is predictive, and demanding falsifiability), boundary-drawing (separating the pre-build regime from prototype/MVP testing, and bounding when the conversion number is trustworthy), and predictive ordering (the cheap signal precedes and forecasts the expensive outcome).

Knowledge Transfer

Within lean-startup practice the smoke test transfers as mechanism across landing-page, fake-door, Wizard-of-Oz, and pre-order tactics — one practice with the probe artifact swapped — and the software-engineering sense is a near-sibling sharing the cheap-fast-filter structure. Beyond that family the named tactic stays home but its design composition genuinely recurs across policy green papers, MOOC pre-registration, test screenings, and Phase 0 microdosing. The pattern travels because it composes substrate-general parents: signaling, experiment, falsifiability, screening, and option_value — reach for those, not the named concept.

Relationships to Other Abstractions

Local relationship map for Smoke TestParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Smoke TestDOMAINPrime abstraction: Optionality — is a decomposition of, conditionalOptionalityPRIMEPrime abstraction: Screening — is a decomposition ofScreeningPRIMEDomain-specific abstraction: Problem-Solution Fit — is part of, conditionalProblem-SolutionFitDOMAIN

Current abstraction Smoke Test Domain-specific

Parents (2) — more general patterns this builds on

  • Smoke Test is a decomposition of, conditional Optionality Prime

    The probe cost can act as an option premium that caps early downside while preserving the right, without the duty, to make the larger build commitment later.

  • Smoke Test is a decomposition of Screening Prime

    The uninformed product team designs a structured choice that induces people who privately know their willingness to commit to reveal it through their action.

Children (1) — more specific cases that build on this

  • Problem-Solution Fit Domain-specific is part of, conditional Smoke Test

    A fake door, pre-order, or landing-page Smoke Test can be one cheap need-side instrument inside a Problem–Solution Fit gate before the product is built.

Hierarchy paths (4) — routes to 4 parentless roots

Neighborhood in Abstraction Space

Smoke Test sits in a moderately populated region (53rd percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Lean Validation & Startup Signal Theater (8 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12