Core principles
Six commitments that shape what we publish and how we describe it.
Structural analysis over product marketing
We study how systems behave inside organizations, not how they are positioned in marketing material. Vendor narratives are treated as one input among several, not as ground truth.
Operational behavior over feature comparison
Feature parity tells us little about long-term dependency. We focus on how software is actually operated, integrated, and relied upon over months and years.
Long-term dependency over short-term efficiency
Most software decisions are evaluated on quarter-scale efficiency. We are interested in the 24–60 month consequences: what becomes load-bearing, what becomes difficult to remove.
Reversibility as a measurable property
A system that cannot be exited without operational damage is structurally different from one that can. We treat reversibility as a first-class property worth describing carefully.
Evidence over certainty
We prefer narrow, defensible observations to broad claims. When evidence is partial, we say so. Confidence is calibrated to what the material actually supports.
Revision in the open
Publications are living documents. Where our understanding changes, we revise the text and log the change. Methodology itself is expected to evolve.
What System Drift analyzes
The structural surfaces we read across organizations and platforms.
Operational concentration
The degree to which a single platform mediates a meaningful share of an organization's day-to-day workflow surface.
Workflow capture
How everyday operational habits, tooling, and internal language become shaped by the systems used to perform them.
Dependency accumulation
The gradual addition of integrations, automations, and data flows that quietly increase the structural cost of change.
Identity centralization
The convergence of authentication, authorization, and access governance into a small number of control planes.
Infrastructure drift
Slow movement of operational state, configuration, and institutional knowledge into the systems that run it.
Reversibility
The realistic technical, contractual, and organizational cost of discontinuing a system without degrading operations.
Platform governance surfaces
The points at which a platform's policy decisions effectively become an organization's policy decisions.
How research is produced
We work from public material, careful reading, and modest field input. We do not maintain proprietary datasets at scale.
- Document reviewPublic documentation, technical references, terms of service, status histories, and security disclosures.
- Architectural analysisReading systems as architectures: where state lives, where authority sits, what is reversible and what is not.
- Public disclosuresRegulatory filings, standards body publications, post-incident write-ups, and vendor transparency reports.
- Procurement patternsPublicly available contracts, RFPs, and budget disclosures that signal how systems are adopted at scale.
- Incident reportsPublished outage reports and structured reconstructions, including downstream effects on dependent organizations.
- Structured observationLongitudinal tracking of product changes, pricing changes, and contractual changes across defined windows.
- Non-attributed operational interviewsWhere appropriate, conversations with operators inside affected organizations, used to inform structural analysis rather than to source quotes.
Limitations
What this work is not, and where its visibility ends.
- System Drift does not perform formal audits.
- Findings are interpretive and structural, not certifications.
- Some operational claims rely on partial visibility.
- Not all dependencies are measurable; some are inferred.
- Organizational context materially shapes how a pattern manifests.
- Absence of evidence is not evidence of absence.
Stating limitations openly is part of the method. Readers should treat System Drift material as careful structural interpretation, not as certification or audit.
Scoring & frameworks
How concepts are evaluated. Framed as structured analytical estimation, not numerical precision.
- ConcentrationHow much of a workflow surface is mediated by a single platform.
- ReversibilityHow costly it would be to discontinue use without degrading operations.
- Workflow surfaceThe breadth of daily operational activity that touches the system.
- Dependency tierWhether the system is peripheral, supporting, or load-bearing.
- Operational exposureThe blast radius of a meaningful failure, change, or policy shift.
These dimensions are descriptive scales used to organize observation. They are not algorithmic outputs, indexes, or audit scores. Where a dimension is referenced in a publication, the reasoning is shown in line.
Revision policy
Revised in the open.
Publications may be revised as understanding develops or new material becomes available.
Factual corrections are logged with the date and a short note describing what changed.
Language may be clarified where readers reasonably misread an earlier formulation.
Methodology itself evolves; this page is the current statement, not a permanent one.
What System Drift does not do
Stated plainly, so there is no ambiguity about commercial posture.
- —No affiliate rankings.
- —No sponsored reviews.
- —No paid placement.
- —No vendor certification.
- —No “best software” recommendations.
- —No investment advice.
“We publish what we can defend. System Drift is designed to observe structural patterns patiently, rather than react to every market movement or vendor announcement.”
— System Drift, editorial position
For editorial procedures, sourcing standards, and correction handling, see our editorial standards.
Editorial standards →