Who owns what: organization, team, service
Organization, team and service as frames inside each other, every one with its own items and the outer two with a note at the side. The description reads the scopes from the outermost to the innermost. With a phone variant. Illustrative organization.
Who owns what: organization, team, service
examples/scope-nesting.json{
"schemaVersion": 1,
"type": "layers",
"title": "Who owns what: organization, team, service",
"width": 820,
"height": 540,
"mobile": {
"width": 360,
"height": 640
},
"layers": {
"display": "nested",
"layers": [
{
"id": "organization",
"label": "Organization",
"items": [
"Security policy",
"Shared tooling"
],
"note": "Sets the rules every team works under."
},
{
"id": "team",
"label": "Payments team",
"items": [
"On-call rota",
"Roadmap"
],
"note": "Owns its services from design to operation."
},
{
"id": "service",
"label": "Billing service",
"items": [
"Invoices",
"Reminders",
"Tax rules"
],
"role": "critical"
}
]
}
}Focus
Show chart data
| Level | Scope | Items | Notes | Role |
|---|---|---|---|---|
| 1 | Organization | Security policy, Shared tooling | Sets the rules every team works under. | |
| 2 | Payments team | On-call rota, Roadmap | Owns its services from design to operation. | |
| 3 | Billing service | Invoices, Reminders, Tax rules | critical |