Lean Validation & Startup Signal Theater

Abstractions about testing and faking demand signals in early-stage ventures — cheap validation instruments (smoke test, landing-page test, problem-solution fit) versus theater that mimics validation without real stakes (customer-discovery theater, milestone theater, founder blind spot, golden hammer).

8 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Customer-Discovery Theater — Diagnose fake product discovery by the single structural test of whether the inquiry is permitted to change the plan — the tell being a long track record of discovery that has never killed or redirected a roadmap.
• Founder Blind Spot — The venture pattern where a thesis's originator, holding the authority to reroute disconfirming signals, systematically preserves their prior instead of revising it — because revision is uniquely expensive at the authoring seat.
• Golden Hammer Anti-Pattern — Diagnose a team applying its familiar technology to a poorly-fitting problem because the acquisition cost of an alternative is visible while the misfit cost is diffuse and downstream, so fluency reshapes what counts as the right tool before fit is ever asked.
• Landing-Page Test — A lean-startup demand test that publishes a page describing an unbuilt offering as if it existed, then counts costly commitment signals (sign-ups, pre-orders, deposits) from representative traffic against a pre-committed threshold — a necessary-not-sufficient gate that can kill a weak idea but never confirm a strong one.
• Milestone Theater — Read a green milestone as a signal with its own production economics rather than a fact — the multi-clause readiness it was meant to certify can be marked done with clauses deferred, so test it by asking what would look different had it genuinely been met.
• Problem-Solution Fit — The lean-startup gate that demands cheap, need-side evidence — a real, important problem for an identified user, and a solution preferred over their current workaround — before committing to build at scale, guarding against 'build it and they will come.'
• 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.
• Technology Push — The innovation posture in which a technical capability is developed first and a search for problems it can address follows — the inverse of demand pull, fixing the technology and ranging over problem spaces, with the multi-year match step as the load-bearing risk.