Validation frameworks, prior art credit, and design by committee

Executive overview

Startup founders repeatedly make avoidable mistakes because they ignore what came before them — both the ideas and the failures. Crediting prior art and learning from it are distinct obligations: one is ethical, the other is strategic.

Three topics are covered: why the startup world fails at prior art, a staged validation framework for early-stage founders, and why design by committee produces mediocre output.

The fastest path to bad decisions is ignoring what's already been tried.

Prior art: crediting and learning

• Presenting someone else's named framework without attribution is plagiarism, even without explicit claims of authorship.
• Readers assume the speaker originated any uncredited idea — silence reads as a claim.
• "Do things that don't scale" (Paul Graham), the hard work/luck/skill framework (Rob Walling), and many others have clear, documented origins.
• This is widespread in the creator/info-marketing space and is largely intentional.
• Giving credit costs nothing and does not diminish the speaker.
• The separate failure: not learning from prior art — attempting things already proven catastrophic without studying why they failed.
• Example: Bolt's employee stock loan programme repeated a 1990s disaster, with the same outcome. Founders who "go back to first principles" without knowing what those principles replaced are just uninformed.
• Reading Paul Graham, Joel Spolsky, Patrick McKenzie, and similar sources lets founders stand on giants rather than restart from zero each cycle.

The 2/20/200 validation framework

• A staged approach to product validation with three levels of time investment: 2 hours, 20 hours, 200 hours.
• Designed to build confidence incrementally before committing significant resources.

Stage 1 — 2 hours:

• Apply the 5pm idea validation framework (covered separately on the podcast and in Rob's upcoming book).
• Useful for evaluating multiple ideas in parallel: five ideas × 2 hours = 10 hours to shortlist.
• Moves confidence from ~0% to roughly 10–20%.

Stage 2 — 20 hours:

• Landing page validation and/or one-on-one customer conversations.
• Match the approach to the business model: landing page + traffic for low-touch products; direct outreach for high-touch sales.
• Gathers both qualitative and quantitative signal.
• Narrows the field to one or two ideas before proceeding.
• Moves confidence to roughly 30–40%.

Stage 3 — 200 hours:

• Build an MVP: no-code, human-automation (à la Start Small Stay Small), or full coded version.

• Goal is to get something into users' hands and test resonance.

• Moves confidence to roughly 50–70% if the idea holds.

• The framework is not a rigid playbook but a compass — it makes "validate" concrete rather than an amorphous obligation.

Design by committee

• More decision-makers typically produce worse output, not better — especially in early creative or product work.
• The instinct to gather more opinions often reflects uncertainty rather than a genuine need for input.
• Metallica's St. Anger is the case study: forcing all four members to contribute lyrics simultaneously produced incoherent, widely criticised writing compared to the prior two-person model.
• Two people with a shared vision outperform larger groups on cohesion and speed.
• At three to five people, vision fragmentation often outweighs any benefit.

How to get external input without losing coherence:

• Start with internal brainstorming; let ideas go cold before evaluating.
• Bring three or four options (not fifty) to a small trusted inner circle with taste and domain knowledge.
• Expand to a slightly broader community (e.g. a Slack group) only after internal filtering.
• Use broader polls (e.g. Twitter) only to confirm a near-final choice between two near-equivalent options.
• Never start a design process with a large group; refine first, then widen.