Skip to content

[Anchor Proposal]: Minimum Viable Product (MVP) #424

Description

@cpoepke

Proposed Term

Minimum Viable Product (MVP)

Context (Optional)

The smallest product that allows a team to test a specific hypothesis about user needs with the least effort. Framed here as an inception-phase product risk reduction technique — not general product strategy. The defining output is validated learning, not feature completeness.

Category: System Inception Patterns (see #414)
(Note: MVP sits at the boundary of inception patterns and product strategy; included here for its role in reducing product risk at project start)

Why it qualifies:

  • Precise: defined by Eric Ries in The Lean Startup with clear intent (hypothesis testing, validated learning)
  • Rich: activates concepts around lean startup, build-measure-learn, pivot vs persevere, customer development
  • Consistent: distinct from "minimal product" or "quick release" — specifically hypothesis-driven
  • Attributable: Eric Ries (The Lean Startup, 2011); Steve Blank (customer development, precursor concept)

Distinguishes from:

  • Walking Skeleton — product-demand validation vs technical architecture validation
  • Thin Vertical Slice — product-level hypothesis test vs single feature delivery increment
  • Spike Solution — product question vs technical question; user-facing vs internal experiment

Open question for reviewers: Should MVP be a dual-category entry (System Inception Patterns + Business/Product Strategy)?

References:

Pre-submission Checklist

  • I have searched existing anchors and this term is not already included
  • This term refers to a well-established concept (not something I invented)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions