---
id: "entity-gv"
type: "entity"
entityType: "organization"
canonicalName: "GV"
aliases: ["Google Ventures", "GV (Alphabet)", "Alphabet's venture arm"]
canonical_url: "https://www.gv.com"
source_timestamps: ["§ What Successful CVCs Do Differently"]
tags: ["case-study", "success-mode"]
related: ["concept-living-organizational-interface"]
sources: ["ecosystem"]
sourceVaultSlug: "hbr-seg-ecosystem"
originDay: 11
articleStem: "hbr-cl-81-corporate-vc-funds"
sourceUrl: "https://hbr.org/2026/03/what-successful-corporate-venture-capital-funds-do-differently"
sourceTitle: "What Successful Corporate Venture Capital Funds Do Differently"
---
# GV (Alphabet)

## Role in the source

GV is the article's **model of successful CVC boundary management** — the positive counterpoint to [[entity-xerox]] and the exemplar of a healthy [[concept-living-organizational-interface]].

## Why GV works

Alphabet's venture arm, launched in **2009**, balances two things most CVCs fail to hold together:

- **Extreme autonomy** — its own fund structure, investment committee, and compensation system.
- **Deliberate bridges back to Alphabet** — shared strategic themes, regular contact with product leaders, and clear rules for connecting portfolio companies to Google.

This balance of independence and embeddedness has let GV **survive multiple market cycles** — exactly the durability the framework ([[framework-cvc-boundary-management]]) aims to produce.

## Enrichment / external corroboration

GV (formerly **Google Ventures**), founded 2009, is widely cited as a successful example of balancing operational autonomy with strategic bridges to the parent (shared themes, regular interaction with product leaders). Canonical site: https://www.gv.com.


## Related across articles
- [[entity-vitex]]
- [[entity-xerox]]