Nobody catches a structural mistake alone
A mistake in the structure can be caught in three places: in the sketch, by someone who could have built it; in the build, by me; or in a client's hands after it ships. For years only the last two
unfalsifiable reading
Meaning
An untestable interpretation of an outcome or design prevents any conclusive disproof of its underlying assumptions. The unfalsifiable reading, in this context, describes a situation where an assessment of a system, a process, or a product’s behavior cannot be empirically challenged or contradicted through observation or experiment. Such a reading arises when the conditions necessary for testing are absent, inaccessible, or were not established during the development phase.
It defines the boundary where claims about functionality or performance are accepted without verifiable evidence, often because the means to gather that evidence were never built into the process.
Testability Horizon
A critical point in any development cycle marks the testability horizon, beyond which the capacity to validate or invalidate core design choices diminishes significantly. Before this horizon, a founder can test structural assumptions with minimal cost and effort, often through sketches or early prototypes. An unfalsifiable reading emerges when this horizon passes without a rigorous examination of foundational premises.
This delay shifts the burden of discovery to later stages, where any identified flaw has already propagated through the build. The further the work progresses past the point of viable testing, the greater the cost associated with reversing or redesigning components based on a newfound understanding.
Founder’s Cost
The operational cost of an unfalsifiable reading often surfaces as significant financial drain or a loss of attention. When a structural mistake remains hidden due to an untested assumption, its correction later demands substantial resources. A founder might face rework, material waste, or client dissatisfaction, all directly attributable to the inability to falsify an early design choice.
This cost extends beyond direct expenditure to include lost capacity, as effort is diverted from new development to remedial action. The energy required to rebuild or re-architect a component that should have been validated earlier represents a direct tax on future growth.
Design Validation
A robust design validation process aims to render all critical assumptions falsifiable, ensuring that potential errors are exposed at the earliest possible stage. The presence of an unfalsifiable reading indicates a failure in this process, where certain aspects of the design are accepted without a pathway for verification or rejection. Effective validation requires deliberately constructing opportunities for disproof, through explicit test cases, measurable performance criteria, or independent review by those capable of spotting structural flaws.
When such mechanisms are absent, the design proceeds on faith, and any inherent weaknesses remain latent until they become apparent under real-world conditions. This lack of initial validation then dictates a reactive posture, where fixes become mandatory rather than preemptive improvements.