← Full mapCurated public summary
Index
Entry 06PUBLIC HANDBOOK

Solution Discovery explained for humans

Problem, Capability Matrix, SaaS, OSS, components, licensing, security, reproducible shortlist, Golden Flows, GAP/TCO/risk, ADR, and ADOPT/CONFIGURE/INTEGRATE/EXTEND/BUILD.

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 06 — Solution Discovery explained for humans
Related normative sources
  • NORMATIVE SOURCEStandard · Development Methodology
  • NORMATIVE SOURCEStandard · Solution Discovery Gate
  • NORMATIVE SOURCEStandard · Existing Solution Assessment
Authority
Public explanation — NON-NORMATIVE
Summary

Problem, Capability Matrix, SaaS, OSS, components, licensing, security, reproducible shortlist, Golden Flows, GAP/TCO/risk, ADR, and ADOPT/CONFIGURE/INTEGRATE/EXTEND/BUILD.

Solution Discovery prevents reflexive building. Before custom development, DCP Flow requires investigating what exists, testing material candidates, and measuring GAP across functional and technical criteria.

The discovery journey

Start with the problem and a Capability Matrix, review SaaS as benchmark, full OSS products and components, then validate licensing, security, compliance, maintainability, and dependency risk. Test the shortlist through reproducible Golden Flows.

Key points
  • SaaS benchmark.
  • Full OSS Product Discovery.
  • Engines and components.
  • Reproducible shortlist and Golden Flows.

ADOPT, CONFIGURE, INTEGRATE, EXTEND, or BUILD

Record the final decision in an ADR. ADOPT uses an existing solution with minimal changes; CONFIGURE uses supported configuration; INTEGRATE connects existing capabilities; EXTEND adds capabilities through supported extension mechanisms; BUILD creates custom implementation when the previous alternatives do not reasonably satisfy the outcome or there is explicit material justification.

Key points
  • Functional and technical GAP.
  • TCO and complexity.
  • Security, compliance, and lock-in.
  • Maintainability and dependency risk.

Discovery is an evidence path, not a list of links

The Gate starts with Problem Definition and a Capability Matrix, uses SaaS as a benchmark, searches for complete OSS products, and then evaluates engines or components. Licensing, security, and compliance filter material candidates. When behavior matters, the shortlist is deployed reproducibly and Golden Flows are executed before GAP, TCO, and risk are assessed.

flowchart TB
A[Problem] --> B[Capability Matrix]
B --> C[SaaS benchmark]
C --> D[Full OSS]
D --> E[Components]
E --> F[License / Security / Compliance]
F --> G[Reproducible shortlist]
G --> H[Golden Flows]
H --> I[GAP / TCO / Risk]
I --> J{Decision}
J --> K[ADOPT]
J --> L[CONFIGURE]
J --> M[INTEGRATE]
J --> N[EXTEND]
J --> O[BUILD]
Diagram source
flowchart TB
A[Problem] --> B[Capability Matrix]
B --> C[SaaS benchmark]
C --> D[Full OSS]
D --> E[Components]
E --> F[License / Security / Compliance]
F --> G[Reproducible shortlist]
G --> H[Golden Flows]
H --> I[GAP / TCO / Risk]
I --> J{Decision}
J --> K[ADOPT]
J --> L[CONFIGURE]
J --> M[INTEGRATE]
J --> N[EXTEND]
J --> O[BUILD]
Key points
  • 1 Problem → 2 Capabilities.
  • 3 SaaS → 4 Full OSS → 5 Components.
  • 6 License/Security → 7 Reproducible shortlist.
  • 8 Golden Flows → 9 GAP/TCO/Risk → 10 ADR.

Five current decisions, evaluated proportionally

DCP Flow evaluates ADOPT → CONFIGURE → INTEGRATE → EXTEND → BUILD as a preference, not a mechanical ladder. ADOPT uses an existing solution with minimal changes; CONFIGURE uses supported configuration; INTEGRATE connects existing capabilities; EXTEND covers gaps through supported mechanisms; BUILD creates a custom implementation only when earlier alternatives do not reasonably solve the outcome or an explicit material justification exists.

Key points
  • ADOPT: minimal changes.
  • CONFIGURE: supported configuration.
  • INTEGRATE: connect existing capabilities.
  • Prefer EXTEND before BUILD when fit, risk, TCO, upgrades, lock-in, architecture, and operating capacity justify it.

Executing candidates and documenting the decision prevents decorative discovery

Finding a repository or reading a README does not validate a solution. A POC records version, runtime, installation, non-sensitive configuration, errors, and limits; Golden Flows may be PASS, PARTIAL, FAIL, BLOCKED, or NOT RUN. The ADR preserves candidates, evidence, trade-offs, and consequences so the decision survives the conversation that created it.

Key points
  • Repository found ≠ candidate validated.
  • Use a reproducible shortlist when runtime behavior matters.
  • NOT RUN is never PASS.
  • ADR turns research into decision memory.

Proportional Discovery and verifiable comparison

Start with the problem and capability matrix. Compare SaaS, complete OSS products, and components using licensing, security, GAP, TCO, and risk. Record ADOPT, CONFIGURE, INTEGRATE, EXTEND, or BUILD with an ADR and a Golden Flow.

INTERACTIVE LAB · 01

Discover before you build

Try four scenarios or shape your own. Changing a condition recalculates candidate paths, trade-offs and missing evidence.

Shape the scenario

FIRST PATH TO INVESTIGATECONFIGURE

Scenario factors

    Compare alternatives

      Risks and dependencies

        Evidence still needed

          Educational simulation: the relative index is not a probability, TCO or normative verdict. The Solution Discovery Gate governs decision modes; validate actual products, licensing, costs, Golden Flow and ADR before the Human Gate.

          Contextual glossary+
          Solution Discovery

          Process of investigating real alternatives and proportionally evaluating ADOPT → CONFIGURE → INTEGRATE → EXTEND → BUILD before a material decision.

          ADOPT

          Use an existing solution with minimal changes when it reasonably covers the outcome.

          CONFIGURE

          Solve the outcome through supported configuration of an existing solution.

          INTEGRATE

          Connect existing capabilities or systems when the governed combination solves the outcome.

          EXTEND

          Expand a platform through supported extension mechanisms to cover real gaps.

          BUILD

          Create a custom implementation when ADOPT, CONFIGURE, INTEGRATE, and EXTEND do not reasonably solve the outcome or an explicit material justification exists.

          IMPLEMENT

          Historical terminology: former umbrella term for implementing an existing solution; superseded by ADOPT / CONFIGURE / INTEGRATE / EXTEND / BUILD.

          GAP

          Difference between required capabilities and those available in an evaluated alternative.

          TCO

          Total cost of ownership including operation, maintenance, dependency, and evolution.