FrameworkF-001Foundation

Dependency Concentration

The foundation framework. Every other concept in the library is measured against it.

Core questionHow much organizational activity depends on a small number of platforms, suppliers, or control points?

Category
Foundation framework
Reading time
~9 minutes
Last updated
June 2026
Status
Active framework
Related concepts
  • Reversibility
  • ·
  • Governance Surface
  • ·
  • Operational Capture
  • ·
  • Exit Complexity
§ 02

Why concentration is the foundation

Almost every other concept System Drift studies — reversibility, governance surface, operational capture, exit complexity — assumes a prior step: that an organization has settled, in practice, around a small number of platforms. Concentration is that prior step. It is the ground the rest of the library stands on.

Organizations rarely choose to concentrate. They make ten reasonable decisions years apart and find, later, that the ten decisions point to three vendors. The framework is concerned less with the choices themselves than with the cumulative shape they form, and with how clearly that shape is seen from inside.

Concentration is not, in itself, a failure. It is often the by-product of efficiency. But concentration changes the meaning of every subsequent vendor decision: it narrows the field of what is reversible, and it lengthens the consequences of every outage, repricing, and roadmap shift.

“Concentration is what every other dependency framework is measuring against.”

§ 03 · Framework view

The five dimensions

Concentration is not a single measurement. System Drift examines it across five surfaces, each carrying a distinct kind of weight.

  1. D·01

    Supplier Concentration

    How few suppliers carry the operation.

    • How many vendors actually matter?
    • How many could disappear without serious disruption?
    • How many are genuinely replaceable?
    Example

    AWS, Microsoft, Salesforce. Three suppliers supporting most operations.

  2. D·02

    Workflow Concentration

    How much of the working day flows through a single platform.

    • How many business processes flow through the platform?
    • What percentage of daily work depends on it?
    • Could employees work effectively without it?
    Example

    An organization with hundreds of workflows embedded inside Salesforce.

  3. D·03

    Governance Concentration

    Where authority, permission, and policy actually live.

    • Where do approvals happen?
    • Where are permissions managed?
    • Where are policies enforced?
    Example

    Everything governed through Okta.

  4. D·04

    Knowledge Concentration

    How much of the configuration lives inside a small number of people.

    • Who understands the configuration?
    • Who understands the integrations?
    • What happens if those people leave?
    Example

    One administrator understands the entire environment.

  5. D·05The System Drift question

    Disappearance Impact

    The System Drift question.

    Not outage. Not degradation. Disappearance. The dependency is gone tomorrow and is not coming back.

    • Can operations continue?
    • For how long?
    • What becomes invisible?
    • What becomes uncontrollable?
§ 04

What concentration is not

Concentration is frequently confused with adjacent ideas. The distinctions are worth drawing carefully, because each describes something different about the relationship between an organization and its suppliers.

  • Concentrationvs.Scale
    A vendor can be large in the market without being concentrated inside any one organization. Scale describes the vendor; concentration describes the buyer's posture toward it.
  • Concentrationvs.Standardization
    Standardizing on one tool is a deliberate choice. Concentration is the cumulative result of many such choices, often made independently, that compound over time.
  • Concentrationvs.Lock-in
    Lock-in describes the difficulty of leaving. Concentration describes how much of the operation is exposed. The two are related, but they are not the same measurement.
§ 05

How System Drift uses this framework

Dependency Concentration is the first lens System Drift applies to any subject of research. It precedes — and informs — every other framework in the library.

  • ResearchLong-form publications begin by establishing the concentration profile of a category before examining its behavior over time.
  • ProfilesDependency Profiles describe the surface a single vendor occupies inside the wider concentration picture.
  • ObservatoryConcentration indices track the share of operational surface held by the largest providers in each category.

The framework is intentionally diagnostic rather than prescriptive. It does not argue that concentration is wrong. It argues that concentration is a fact worth naming, before any further analysis can stand on it.

§ 06

Related research

System Drift begins every study with concentration because concentration is the quietest fact about a modern organization. It is rarely chosen, frequently unmeasured, and almost always visible only in reverse.