How the dependency formed
A longitudinal note. Dependency rarely arrives in a single decision.
Adoption typically begins with mail and document collaboration. Within two to three years Drive holds the working corpus, and the directory federates an expanding set of third-party SaaS.
By the time identity, mail, files, calendar, and meetings all run through the same tenant, the platform is the operational substrate.
The platform read through the five frameworks
Each section applies one of the System Drift frameworks to Google Workspace.
Dependency Concentration
Concentration covers mail, files, calendar, meetings, and identity. Bundled licensing reinforces full-suite adoption, and Drive's real-time collaboration model concentrates document creation rather than distributing it.
Concentration in identity grows quietly as SAML and OIDC integrations accumulate against the directory.
Observed indicators- —Drive is the canonical place documents live and are co-authored.
- —The directory is the federation point for non-Google SaaS.
- —Calendar and Meet absorb scheduling and meeting workflow.
Reversibility
Reversibility is constrained by co-authoring history, sharing-link continuity, and the federation graph. Native exports exist for mail and files; the surrounding context is harder to move.
Reversibility decreases as Workspace-native document formats accumulate in the corpus.
Governance Surface
Governance lives in admin console policies, context-aware access rules, Vault retention, and DLP. Where these are the place policy is authored, Workspace is the governance surface for the productivity layer.
Audit functions increasingly read out of the admin console rather than into it.
Operational Capture
Capture is most visible in Drive and Docs. Decision logs, drafts, and shared workspaces accumulate in ways that no separate inventory describes.
Capture is also present in calendar conventions and meeting structures that have become organizational defaults.
Exit Complexity
Exit complexity is dominated by document fidelity, federation re-implementation, and the retraining of staff who think in Workspace conventions.
Institutional memory lives in shared Drives, where it is rarely re-described elsewhere before migration.
What separation would involve
A description, not a recommendation.
Separation would require migrating the document corpus with attention to fidelity, re-platforming the directory and re-federating downstream SaaS, and replacing collaboration conventions with whichever platform absorbs them. The dominant cost is the corpus and the conventions around it, not mail.
Editorial note
This profile is a dependency study, not a product review. It is not a buyer's guide, a feature comparison, or a recommendation. It does not argue that Google Workspace is good or bad. It documents how the platform shapes organizational behavior, where concentration accumulates, and what separation would involve.
The framework readings are revised on the transparent methodology cadence. The indices are analytical signal, not procurement advice.