Diagram templates

A C4 system context diagram, a "who uses it and what it depends on" slide, or an integration overview: one system, one to four actors that use it, and one to five external systems it calls or that call it, each link saying what it does.

Event flows through one broker, bus, or topic hub with one to five producers and one to five consumers, such as Kafka topics, Google Pub/Sub, SNS fanning out to SQS queues, EventBridge rules, or a webhook gateway delivering to several handlers; built for fan-in and fan-out.

Capabilities around a core offer, skills around a team's purpose, services around a platform or workstreams around a programme goal, where which parts sit next to each other matters.

Offer design with demand and delivery; Programme inputs and outcomes; Partnership contribution and support.

For one supplied choice among three or four considered options with a single statement about the selected one: a target audience and its positioning, a pilot region and why it goes first, a shortlisted vendor and the deciding reason, or a chosen scenario and its premise.

For one shared basis adapted per branch: an offer tailored to audiences with their channels, a platform packaged into tiers with their prices, a policy applied per region with its owner, or a curriculum adapted per cohort with its format.

One center with three to eight parts that each tie directly to it, such as platform modules, strategy pillars, supporting teams, marketing channels, or product benefits.

For shared service offerings, campaign programs or community support.

For a core platform, team or offer and the four to eight parts that each depend on it directly, such as the services on a shared data platform, the departments around a customer team, the channels fed by one campaign, or the partners around a core product.

Successive enclosing contexts around one core, such as core, actual and augmented product benefits or named application layers.

One center and three to ten named ecosystem members, grouped into one or two supplied rings.

Two departments sharing a capability, partner ecosystems sharing a provider, or two regional networks sharing a facility.

One product, platform, team or idea and two to eight directly related capabilities, stakeholders or parts.

Office support, regional coordination and service coverage between two to five catalogued cities in the fixed 40°E equatorial orthographic hemisphere.

Dimensions, capabilities, values, or pillars around a shared subject: a wellbeing wheel, leadership competencies, service capabilities, or brand values.