Skip to content
UPG is in early alpha. The specification is still evolving and may change between versions.

Use Cases

UPG at scale, worked all the way through

The spec defines what the graph is. A use case shows what it does when a real organisation leans on it. Each one takes a single shape of product work at scale, runs it end to end against a concrete example, and hands off to the reference. The portfolio and competitive cases share one company (Stripe), so they compose into a single picture; the rest stand on their own.

01The Cases

Each covers one region of the lifecycle or a cross-cutting capability, with more added as the pattern earns them. Every one is self-contained, so start anywhere.

Portfolio OrchestrationMulti-product

Two product axes, a shared registry that catches drift, and an OKR cascade that stays legible at the top.

Strategy & OutcomesStrategy

Vision down to a measurable key result, every objective and feature naming the outcome it serves.

Competitive IntelligenceMarket

Competitors as watched graphs, their moves as dated signals, feature parity as a traversal.

Users & NeedsDiscovery

One typed persona the whole product links to, with the jobs it pursues and the needs they surface.

Roadmap & DeliveryDelivery

From the need a feature addresses down to the task an engineer picks up, scope and priority as traversals.

Business & GTMBusiness

Business model, growth engine, and marketing as one region anchored on the value proposition.

Experience & DesignDesign

The journey mapped to the persona, a design system of linked components, and the surfaces they compete to occupy.

Modelling the InterfaceDesign

The place a feature claims, the rule that settles who wins it, and the configuration that decides which interface renders at all.

Analytics & MeasurementAnalytics

Data source to dashboard, a north-star metric decomposed into the inputs that move it.

Metric TreesMeasurement

A metric at every level: formula, decomposition tree, the outcomes it measures, and its provenance.

Engineering & PlatformEngineering

Service, API contract, schema, and deployment hung off one node that traces to the user need.

Operations & QualityOperations

An incident typed to its SLO breach, postmortem, and root cause, so break-learn-prevent is queryable.

Standards & FoundationsFoundations

A spec registered once as a canonical entity every product links to instead of redefining.

Agents That CompoundAI

One shared graph every agent reads and writes over MCP, so AI output accumulates instead of re-deriving.

Adopt Existing WorkAdoption

Markdown, Notion, Linear, and GitHub imported as typed nodes with a confidence a human reviews.

Frameworks as ProjectionsMethod

Entities held once, projected through OST, Business Model Canvas, or RICE with nothing to sync.

Research SynthesisDiscovery

Every rung typed from a verbatim quote up to an opportunity, so decisions trace to their evidence.