Skip to content

Minimum Sufficient Solution

Implement the smallest solution that satisfies the core requirement without unnecessary features, scope, or complexity.

The Diagnostic Story

Symptom: The scope keeps expanding before the core requirement is stable. Features, process steps, controls, and variants are added because they might be needed, because a stakeholder asked, or because they seem like good ideas. Delivery slips, the solution becomes harder to maintain, and the additional complexity makes it harder to see whether the essential requirement is actually met.

Pivot: State the core requirement explicitly. Identify the invariants that must be protected — safety, legality, accessibility, operational usability — and filter out everything that does not serve those constraints or the core requirement itself. Validate that the remainder is sufficient, and define the explicit trigger that would justify adding scope back.

Resolution: Delivery is faster and the result is easier to maintain because it reflects only what the requirement actually needed. The sufficiency boundary is legible, so the team can make principled decisions about what to add next rather than accumulating features by default. The expansion path is preserved, but expansion requires evidence rather than speculation.

Reach for this when you hear…

[startup product] “We spent three months building the admin dashboard before we had a single paying customer — turns out none of them cared about the dashboard.”

[emergency response] “In the field you need a protocol that gets you to the right answer with what you have, not the optimal protocol for ideal conditions.”

[regulatory drafting] “Every exception we add to make the rule more precise creates a new loophole — sometimes the best rule is the shortest one that covers the core case.”

Mechanisms / Implementations

  • MVP-like Scoping: Is a common implementation mechanism, especially in product and service contexts.
  • Minimum Viable Process: A minimum viable process is the smallest recurring workflow that performs its function.
  • Lean Policy Design: Creates the simplest rule or governance structure that can achieve the policy purpose.
  • Essential Feature Set: An essential feature set is an artifact that lists the capabilities required for the solution to work.
  • Minimum Viable Documentation: Gives users and operators enough information to act correctly, maintain the solution, hand it off, or escalate problems.
  • Simple Intervention Package: A simple intervention package bundles the few elements needed to produce a target effect.
  • Pilotable Solution: A pilotable solution makes the minimum testable in a bounded context.
  • Must/Should/Could Filter and Scope-Cut Review: Must/Should/Could filters and scope-cut reviews are practical sorting mechanisms.
  • Must/Should/Could Filter
  • Scope-Cut Review

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 8 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Minimum Viable Process · implementation variant · recognized

Use the smallest process that reliably performs the required coordination, control, or governance function.

Essential Feature Set · subtype · recognized

Define the smallest set of features or capabilities that lets the solution satisfy the core user or system need.

Minimum Viable Documentation · implementation variant · recognized

Create the smallest documentation package that lets the intended users operate, maintain, audit, or hand off the solution safely.

Simple Intervention Package · implementation variant · candidate

Bundle the few intervention elements required to produce the target effect while leaving optional supports out until needed.