§ FAnalytical Frameworks

The lenses System Drift uses to read modern software ecosystems.

Each framework is a working definition — refined through field research, published openly, and revised on a transparent log.

F·01

Operational Concentration

What it means

The share of an organization's daily workflows mediated by a single vendor, platform, or contract surface.

Why it matters

When concentration rises, day-to-day operations become structurally bound to a single provider's roadmap, pricing, and policy.

Signals to watch
  • Increasing share of seats or workflows under one license
  • Bundled SKUs replacing category-by-category procurement
  • Cross-product integrations only available within a single estate
Effect on optionality

High concentration narrows the realistic field of alternatives and shortens the timeline in which switching is feasible.

F·02

Reversibility

What it means

The realistic cost, time, and political capital required to exit a platform without degrading mission-critical operations.

Why it matters

Reversibility is the inverse of lock-in. Low reversibility means the organization has surrendered optionality without necessarily intending to.

Signals to watch
  • Data formats with no documented export path
  • Workflows embedded in proprietary automation surfaces
  • Identity and access centralized on a single provider
Effect on optionality

As reversibility falls, every future decision is increasingly shaped by the incumbent platform's constraints.

F·03

Dependency Accumulation

What it means

How integrations, data formats, and trained behaviors compound over time into a structural inability to switch.

Why it matters

Accumulation is rarely the result of a single decision. It is the cumulative residue of dozens of locally rational ones.

Signals to watch
  • Year-over-year growth in vendor-specific custom code
  • Internal trainings centered on one product's UI
  • New hires onboarded directly into the vendor's mental model
Effect on optionality

Accumulated dependency raises the cognitive and political cost of evaluating alternatives, even when they exist.

F·04

Infrastructure Drift

What it means

Gradual changes in vendor architecture, pricing, and policy that quietly reshape an organization's operating model.

Why it matters

Drift is invisible in any single quarter and unmistakable across years. It is how operating models change without explicit decisions.

Signals to watch
  • Repeated minor pricing revisions that compound
  • SKU consolidation that bundles previously optional features
  • Region or residency commitments adjusted under regulatory pressure
Effect on optionality

Drift shifts the cost-benefit of the platform without the organization formally re-deciding to use it.

F·05

Workflow Capture

What it means

The point at which an internal process is no longer separable from the platform it runs on.

Why it matters

Capture marks the moment that a workflow stops being an organizational asset and becomes a platform-defined behavior.

Signals to watch
  • Process documentation indistinguishable from product documentation
  • Internal terminology mirrors a vendor's product vocabulary
  • Removing the platform would also remove the process
Effect on optionality

Captured workflows cannot be migrated; they must be rebuilt. This is the hardest form of dependency to undo.